5 ms·
> It's been in place on TalkTalk's network for 2 years now...but it hasn't caused significant issues yet. Of course it hasn't; It's only been 2 years. You won
by dlitz 13y ago
> It's been in place on TalkTalk's network for 2 years now...but it hasn't caused significant issues yet.
Of course it hasn't; It's only been 2 years. You won't notice unless you're trying to build or deploy something innovative that breaks some of the assumptions that the designers of the filters never anticipated.
Layered protocols exist to allow them to evolve over time with a minimum of complexity (and cost). When you break the layering, you make that evolution more expensive. Look at how expensive it is to write a basic app that has peer-to-peer conectivity, thanks to NAT.
How are we supposed to deploy the next WebSockets when there are transparent HTTP proxies everywhere that aren't aware of it?
Economically speaking, widespread deployment of these sorts of filtering technologies are exactly like pollution: they look fine at first, but eventually they end up being very expensive for everyone, even the people who never used them.
- DanBC 13y agoAlso, it may very well have caused a lot of issues, but users are naive and don't know how to troubleshoot these kind of problems.