Mark Cowan

Surely it makes sense for the content-type to depend on the file being served, rather than the URL used to access it? (since we do indeed serve the target file,...

Resolve the path to the file before analysing the extension, possibly using `fs.realpath` https://nodejs.org/docs/latest/api/fs.html#fs_fs_realpath_path_cache_callback

`Why is that better?` Because the format specified in the response is based on the file being served, rather than the path used to access it.

UNIX traditionally used the first two bytes of a file's contents to identify it (which filesystems usually still store a copy of in the directory entry), but filename extensions are...

I recently got this too, when opening files ``` 2 files to edit Vim: Caught deadly signal SEGV Exception KeyError: KeyError(140283346540288,) in ignoredVim: Finished. Segmentation fault (core dumped) ``` I'm...

I have the Greek alphabet mapped on my keyboard so I can type stuff like Ω or μ with 4 keystrokes each. But perhaps having a simple string-replace of `\R`...

Audacity attempts to guess input format and 90% of the time gets it wrong, in addition to having an annoying limit on sample rate, which is how I came across...

I think these are two separate approaches, which probably deserve separate issues: 1. Reading metadata from a separate side-car file. 2. Reading metadata from the raw data file's filename.

If I ever find it, I will! I wrote that several PCs/laptops ago, and a couple of disk-failures ago, so it's buried deep in backups somewhere.

Could possibly have a script hooked to the repo the generates several views of each part and publishes them to a separate repo/site/archive rather than putting them in the source...