Depends on your setup. I’m a btrfs guy, so I’d go with something similar as your other reply. It’s just as easy to remove/replace/add drives. They don’t even have to match in size. Just remember to balance after doing modifications to your array.

Whatever you get, get at least two and do RAID1/5/6. They will break.

Speed shouldn’t be an issue for streaming media.

Don’t you worry about planet express, let me worry about blank.

Inspired by xkcd’s thing explainer I generated a list of how often words appeared in subtitles on opensubtitles for my target language.

I whipped those into a database, added manual translation for the top-1000 and started quizzing myself with a tiny php script.

It was more fun to code than to actually quiz myself. I think I played the top-100 before I got bored.

WebRTC isn’t necessarily a bad specification.

But that history shows how they draft a specification, implement a service around it at a fast pace (in this case even with a takeover), and many years later the draft turns into a än official specification.

Other browsers have no choice but to fall in line behind the draft if they want to stay relevant. And they did.

IE did the same shit with their marquee-tag back in the day. Last I checked it still works on Firefox. (It’s still not in any w3c specification)

https://en.wikipedia.org/wiki/WebRTC#History

I don’t think I could summarise it better than that Wikipedia section.

The Android client seems to have dropped a few player engines in a recent update. Previously there was an option to use libvlc, omxplayer or a third option that I can’t recall. Seems the developer opted to go with the worst option.

The AndroidTV app can use external players such ss VLC. I went with kodi as a client instead.