Plus you can rewatch without downloading again. And use sneakernets for sharing with your friends.
I've always disliked how wasteful streaming is in respect bandwidth consumption. However, the "efficiency be damned, just make it fasterer" attitude towards bandwidth is, if not the biggest, then definitely among the biggest, drivers behind the ever increasing internet throughput. Thinking about it, it seems like watching habits could make streaming be more or less "efficient" compared to downloading once and storing…
Huh. I typically watch the same thing over and over repeatedly for like a year or more.
In the article you mention "Cloudflare" a few times, but I think you mean "Cloudfront". For example: "web-assets.strava.com resolves to Cloudflare, see the writeup on my site for details"
I'm assuming this was a typo based on the names sounding so similar and both being CDN's. Is that correct?
Other than telehealth, we also use the bandwidth for remote desktops/apps and lossless high-resolution radiographic images. While one might expect this traffic to occur over local networks, many hospitals have multiple sites and partnerships that are connected over the internet. So, for example, one might operate the hospital's apps while sitting in the library at the affiliated university.
> So, for example, one might operate the hospital's apps while sitting in the library at the affiliated university. Remote Desktop and even PACS are not huge bandwidth consumers in this day and age of 4K streaming. At my large academic institution usually only the radiologists use the PACS client directly on workstations - all the other clinicians are using a “zero footprint” viewer over Citrix like everything else.
That "zero footprint" viewer over Citrix is susprisingly resource-intensive, even at 1080p with lossy compression. If everyone used it (say, if every workstation were a Citrix client), it quickly adds up. During peak hours, it positively chugs. Not sure if networking or compute is the bottleneck here. Perhaps you're right: some institutions have not caught up to this day and age of 4K streaming, and their pre-Netflix infrastructure is buckling under the weight of all these Citrix streams.
> So, for example, one might operate the hospital's apps while sitting in the library at the affiliated university. Remote Desktop and even PACS are not huge bandwidth consumers in this day and age of 4K streaming. At my large academic institution usually only the radiologists use the PACS client directly on workstations - all the other clinicians are using a “zero footprint” viewer over Citrix like everything else.
That "zero footprint" viewer over Citrix is susprisingly resource-intensive, even at 1080p with lossy compression. If everyone used it (say, if every workstation were a Citrix client), it quickly adds up. During peak hours, it positively chugs . Not sure if networking or compute is the bottleneck here. Perhaps you're right: some institutions have not caught up to this day and age of 4K streaming, and their pre-Netfli…
> Placing a device in passthrough mode will remove firewall protection provided by the AT&T gateway Did... did they seriously turn the router into a DMZ*, without your consent? Where every port of your computer is just open to the internet? That's scary. *that's what it was called on my router, the "forward every single port to one device" mode. Not sure if that is the correct term for it.
Yeah. We checked with censys.io, port 3389 and 8080 were open as publicly available service on the router.
Oh yeah, if you leave RDP open to the internet the scanbots will be all over that like white on rice.
If only we would finish the switch to IPv6 we could pull the rug out from under those bots.