Delay between feeds was tolerable when everyone watched the same broadcast, and it stopped being tolerable years ago.
The stream is behind and the noise next door gives it away
You hear the shout through the wall about four seconds before it happens on your screen. Then a phone buzzes. By the time the ball actually crosses the line you already know, and the moment you paid for has been taken from you by physics and by a chain of encoders.
The delay is not one thing. Signal leaves the ground, gets encoded, gets packaged into segments of a few seconds each, gets pushed to a distribution network, gets pulled by your player, which buffers a couple of segments before showing you anything so that a wobble in your connection does not stop the picture. Every stage is defensible on its own. Stacked together they produce a gap of anywhere from ten seconds to nearly a minute against somebody watching a satellite feed, and the gap is not consistent between two people watching the same service in the same city.
That inconsistency is the part I find least acceptable. A uniform delay would be survivable. Everyone lives in the past together, the group chat stays honest, and nobody is spoiled. What we have instead is a room where one person is thirty seconds ahead of another, which ruins the shared experience that was the entire point of watching live.
Providers know how to fix most of it. Shorter segments, low latency protocols, smaller buffers. The reason they do not is that all three make the picture more fragile, and the complaint generated by a stuttering stream is louder and better documented than the complaint generated by being late. A buffering wheel is a support ticket. A four second delay is a vague annoyance nobody reports.
I would take the stutter. I would take a noticeably softer picture too. Given the choice between a stream that is beautiful and thirty seconds late, and one that is mediocre and three seconds late, the second is a better product for live sport and a worse one on every metric the industry actually measures.
What is genuinely unforgivable is a service that runs its own betting or in play statistics ahead of its own video. That happens. It means the operator has decided that data latency matters and picture latency does not, which tells you exactly what they think you are watching for.

