Jan 1 2019
Partially implemented in the related commit.
Dec 31 2018
Dec 30 2018
Dec 25 2018
Well, my browser for once (Chromium, latest version) won't play any flac or aiff. It just downloads the file but it won't play it
Fair enough. Though there are a bunch of audio file format (aiff, flac...) not supported by the <audio> tag specification, they are still playing within different web browsers.
According to the <audio> tag specification, only audio/mpeg, audio/ogg and audio/wav mime-types are allowed, that doesn't cover .aif/aiff so even if I added support for those files here as a third <source> tag it just wouldn't work. I'll add ogg.
They do, but instaud.io only supports mp3, wav and ogg.
I don't think browsers can play .aiff
I think the most common audio files people will use are .mp3, .wav and .aif (.aiff on macOS)
For now it will report to admins only.
This was the original behavior but iirc somebody requested this to be changed early on. I'll wait for consensus but if nobody else comments here I'll just implement this
Doesn't work if users uploaded anything but an mp3 file
Alright, this seems to have been caused by the server being overloaded at the time the vote happened. The user clicked the vote button multiple times and the server took a couple seconds to process the request, leading to double votes. This can be fixed by "locking" voting from a certain user to a post/comment for a couple seconds (via redis) after the voting endpoint is called. Or maybe outright rate-limiting.
Investigating this right now. It doesn't seem to be the double-voting issues we've had early on with @pembo210's broken mouse
Dec 20 2018
Dec 18 2018
Oct 20 2018
Sep 29 2018
Sep 25 2018
Sep 4 2018
Aug 22 2018
Jul 29 2018
Jul 21 2018
Jul 13 2018
Jul 11 2018
Jul 10 2018
Jul 8 2018
Jul 5 2018
And who would it report to? Mods? Admins?
Jul 4 2018
Typo on the commit description.