

That second one is apparently sub-ms latency, which is incredibly unnecessary for a TV.
That second one is apparently sub-ms latency, which is incredibly unnecessary for a TV.
Still is 3 hours after you. What are we up to, 27 hours and counting?
Oh man I didn’t even see that in the menu. That is handy.
Secure
is what you’re looking for.
This is second-hand, so take it with a grain of salt, but I’ve seen mention of a bug that sometimes causes the same graphql query to be executed in an infinite loop (presumably they’re async requests, so the browser wouldn’t lock and the user wouldn’t even notice).
So they may essentially be getting DDOS’d by their own users due to a bug on their end.
Edit: better info: https://sfba.social/@sysop408/110639435788921057
My RiF just started doing the same about 10 minutes ago. RIP.
Some math functions have slightly different results depending on architecture and OS, so they fuzz the results a little. Here’s a tor issue discussing the problem: https://gitlab.torproject.org/legacy/trac/-/issues/13018