

The raw comment is this:
[Digg.com](digg.com) didn't load for me, good start 😅
It’s missing the https:// protocol, so the link is assumed to be relative to the current page you’re on. It should have been formatted as
[Digg.com](https://digg.com/) and then it’ll look like: Digg.com







For broadcast television, especially over the air, there’s no additional load on the provider side for broadcasting to 1 or 1 million people. The TV consumers never have to communicate back to the broadcaster, and this is very efficient from a bandwidth perspective. It’s somewhat similar for cable in most provider situations, the video is broadcast over a wire rather than over the air.
With streaming, each stream has to negotiate with a server to access the stream and the server serves the content to that consumer. This scales as there are more consumers, and the load on the provider increases. Caching layers and CDNs exist to distribute this load, and that is expensive. This is why streaming providers have a “Are you still watching” prompt if they think you’ve stopped watching, since it costs lots to serve the content.