←back to thread

160 points simplesort | 10 comments | | HN request time: 0.848s | source | bottom
Show context
butlike ◴[] No.43625701[source]
All that logging and they cant figure out why people are going to other streaming services
replies(4): >>43625729 #>>43625773 #>>43625797 #>>43625972 #
1. ASalazarMX ◴[] No.43625773[source]
Despite their awful UX, I'm always impressed with how reliable their service is, technically speaking. Video is always good and responsive even on less-than-stellar connections, you can leave a show paused for hours, and resume it almost instantly. Their fast.com speed test is always much faster than your regular internet access, I guess thanks to their Open Connect Appliances.

It must be great to work for them in infrastructure and backends.

replies(5): >>43626160 #>>43626388 #>>43626597 #>>43627654 #>>43627779 #
2. yuters ◴[] No.43626160[source]
I have an old fire tv and never tried to stop automatic updates on it, it has become so slow and unresponsive that I'm barely able to switch inputs to use something else. Netflix is the only app that still works on that tv.
replies(1): >>43627557 #
3. faitswulff ◴[] No.43626388[source]
I can only remember one major outage from them in the past ~10 years (in the 2020s, not the 2012 outage), and if I recall correctly, it was fixed in short order...and they never released a postmortem
4. silisili ◴[] No.43626597[source]
Generally I'd agree, but you must not have seen their attempts at live events :(.
5. ciupicri ◴[] No.43627557[source]
I also have an old TV and guess what? Netflix stopped working last year. The application is not supported anymore. Beats me why.
replies(1): >>43627583 #
6. acdha ◴[] No.43627583{3}[source]
Often it’s CA certificates expiring. My old Toshiba had app rot set in like that, where after about 5 years none of the built in apps worked any more and the errors appeared to be TLS related. I suspect that was due to pinned certs to prevent MITM pirating.
7. toomuchtodo ◴[] No.43627654[source]
They also performed work to ensure it performed well for Starlink customers.

A Global Perspective on the Past, Present, and Future of Video Streaming over Starlink - https://dl.acm.org/doi/10.1145/3700412 | https://doi.org/10.1145/3700412

8. ndriscoll ◴[] No.43627779[source]
Not that this detracts from the wider point, but I'd expect unpause to just work unless you go out of your way to make it not work. Even if you drop the connection at some point, afaik they use ~15 Mb/s as their "premium" bitrate, so e.g. a 30 s buffer takes less than 64 MB. That gives plenty of time to re-establish streaming after an unpause. It's not like the computer forgets what it was doing if you leave it alone.
replies(1): >>43635988 #
9. ASalazarMX ◴[] No.43635988[source]
Counterpoint: Plex and Jellyfin free resources if you leave your video paused too long, and it will take a noticeably amount of time to resume streaming, much more if it needs transcoding.

They're not going out of their way to annoy us, they try to be efficient with the finite resources a home server has. Netflix is going out of their way to make it smooth no matter what you do, even if they have to pool a bit of their own resources for it.

replies(1): >>43659807 #
10. ndriscoll ◴[] No.43659807{3}[source]
Buffering would be on the client though. Assuming it has a couple dozen MB of memory, it should be able to buffer like 30 seconds. I realize their resume has more to do, but e.g. my jellyfin server can initiate playback or seek within maybe 100-250 ms (it's just barely a noticable pause after a random seek). So a 30 s buffer should be more than sufficient for unpausing without any stutter.