News for hackers. Stuff that matters.

A comment on Justin.tv's Live Video Broadcasting Architecture (2010). Parent comment

Re:Justin.tv's Live Video Broadcasting Architecture (2010) by NightlyDev on Thursday July 04, 2019 @12:11AM (#20351449)
"F5 storms" are easy to handle. Intercept all keypress combinations for refresh and do what you want with it client side. (spread it out over time, use a high-performance endpoint to check if live or a combination)

Most people doesn't use the refresh button in the browser, so only a small amount of traffic will be uncontrolled.

[ Parent | on HN ]
Re:Justin.tv's Live Video Broadcasting Architecture (2010) by jrockway on Thursday July 04, 2019 @01:02AM (#20351696)
Do you have any data to support that? I personally don't have an F5 key on my keyboard (it requires pressing a modifier), so I pretty much always click the reload button to fix a stream blip. The impression I get from reading Twitch chat is that most people are using mobile. I doubt they have a keyboard plugged in and press F5 to refresh.

That said, you certainly don't need your video streaming servers to handle those hundred-thousand refresh requests.

[ Parent | on HN ]
Re:Justin.tv's Live Video Broadcasting Architecture (2010) by squeaky-clean on Thursday July 04, 2019 @02:42AM (#20352139)
Yeah anecdotally every non-tech person I know clicks the refresh button.

It also doesn't catch people watching on mobile web who refresh. And I don't believe their mobile app has a refresh button, whenever a stream glitches out for me I force kill and reload the mobile app.

[ Parent | on HN ]
Re:Justin.tv's Live Video Broadcasting Architecture (2010) by cortesoft on Thursday July 04, 2019 @12:23AM (#20351494)
You have any data on most people not using the refresh button in the browser?
[ Parent | on HN ]