Got it.

Ah, I see the unclear part. I read this line…

I imagine sitting on coach, searching for show. Then you want to watch some, and then you have to wait half an hour for full episode (or even season?) to download.

As if OP already had a media library, and was outside of their home, sitting on a coach (bus?) and wanting to watch something from their existing library on their phone/laptop/tablet, thinking they’d have to wait for the entire thing to download. This would not be the case. If OP had no content library, and wanted to browse for something new, then yes, you’d need to download the entire thing and add it to your media library first.

1. Getting stuff into your media library require downloading the thing.
2. Watching stuff (even remotely) that already exists in your library does not require downloading the whole thing.

attempts to query 8.8.8.8, regardless of your DNS settings.

Streaming box / stream app makers have been working around local DNS for a long time. Sometimes of course they’re assholes that want to do shitty things and do this to make interdiction harder. But sometimes there are legitimate reasons. Ones I remember… users who don’t really understand what they’re doing can be overly aggressive with blocking and block things that are necessary for a particular service (causing support problems). Sometimes the ISPs DNS servers have shit performance, and using a well known commercial provider like cloudflare or google can improve performance at scale. It’s not always evil.

You can’t watch media before it’s completely downloaded.

This is not true for just about any use case.

If you use *arr, you’ll likely use Plex or Jellyfin for a media server. That server will do progressive streaming. Netflix by contrast does dynamic adaptive progressive streaming.

Progressive streaming means that playback will start once your client has downloaded and buffered enough of the selected content from the server. The amount is typically a fairly small portion of the stream, like 10 seconds or so, though the specifics are left to the server and client configs.

Dynamic adaptive progressive streaming has a multiplicty of streams optimized for different devices, formats, and quality levels. This might be a few hundred copies of the same video asset, but in a few different codecs, a few different color encodings (ie HDR, SDR), and a quality ladder of maybe 10 steps ranging from low quality SD to moderate quality UHD (like maybe 300kbps at the low end, and 40Mbps at the high end. And these will be cached around the world for delivery efficiency. On playback, the client (player) will constantly test your network throughput in the background, and “seamlessly” adjust stream quality during playback to give you the best stream your network and client can support without stopping to rebuffer.

For example, if you’re on a 4K/HDR TV with Atmos sound, and great network throughput, you’ll get the highest quality HDR streams and Atmos audio. Conversely, if you’re on mobile that doesn’t support HDR and only stereo audio, you’ll get much more efficiently coded HD video (or maybe SD) and stereo audio streams that are more suited to playback on that device. It would be impractical (huge cost and minor benefit) to try to replicate dynamic adaptive streaming just for yourself.

In any case, even if you’re just pulling off a NAS, you shouldn’t need to wait for the entire file to download before you can start playback. If your files are properly coded, you should be able to do progressive streaming in just about any use case.

If you haven’t read about the Milgram Experiment, it’s a fascinating, and disheartening journey into notions of authority and compliance. In short… Milgram’s finding was that most people do what they’re told–even when they known it’s wrong–simply because they’re told to do it.

There is no verification that is true.

But there is a nearly continuous stream of occurrences where Meta is caught lying.

It looks like it says iPad in the upper right. iPad never used Silverlight, it had an iOS app from launch, but you’re right in general. PC browsers used WMV for a brief while at the launch of streaming and then switched to Silverlight.

Streaming was very much the term used to describe watch instantly language (like all language in the UI) wasn’t random, it was the result of continual testing and optimization. The entire set of activities was new for a lot of people, and the company tested variants of everything all the time. I can’t remember too much about this specific device/UI combo, but probably watch instantly was chosen because at the time it needed to distinguish “instant watching” from managing your ‘DVD by mail’ queue (which was the only thing you could do on the web before “watch instantly” was a thing. We definitely used streaming to describe the activity though; you’d find it in press, earnings calls, etc… Just not in that particular variant of the UI. (source: worked there at the time).

No. Debian on the server. CachyOS on the laptop OPNsense / FreeBSD on the router-firewall appliance.

I don’t really feel like I need a single OS across everything. The lack of that has never been an issue.

Most Americans don’t understand the distinction between partisanship and politics. The phrase “I’m just not political” usually means either “I don’t want to hear your partisan bullshit right now.” or “I hold objectionable views that I can’t articulately defend.”

It’s the new Ice Barbie.

If he’s that out of the loop on news, the poor bastard probably doesn’t even realize he dies in a fire locked inside it every time he drives.