Hacker News new | ask | show | jobs
by DyslexicAtheist 2358 days ago
in 2017 Brave disabled it:

> Back-story: Brave users reported ads getting past our ad-blocking shields in previous Chromium versions, beginning with reports of ads displaying on YouTube.com on October 11, 2016. uBlock Origin users had reported similar bugs. We discovered during testing that disabling QUIC seemed to stop these ads. As a result, we pushed an update to disable QUIC in Brave on January 25, 2017. This update appears to have temporarily abated the incoming bug reports about ads getting past our shields.

...

When we inspected web page traffic via chrome://net-internals, we discovered that QUIC requests were and still are being used for a majority of Google’s ad domains, including domains involved with bidding ...

source: https://brave.com/quic-in-the-wild/
2 comments
Already__Taken 2358 days ago
Google software uses a google protocol to deliver google services. News at 11.

Is this the problem where we've shot ourselves in the foot securing communication to the point we can't block adequately now by tempering with traffic?

link
cptskippy 2358 days ago
> Is this the problem where we've shot ourselves in the foot securing communication

Isn't that the goal? Everyone seems to think Google's innovations are gifts to the world. They are and always have been solutions to problems Google faces. The only reasons they're opensourced or community shared are to benefit Google. Anything beyond that is collateral benefit.

link
zamadatix 2358 days ago
Per the Brave article blocking is perfectly possible and works fine, it was just their blocker implementation not being ready for a different protocol.
link
judge2020 2358 days ago
My question is why does their ad-blocking code work with one protocol and not another? Is their ad blocker running within Chrome's TCP/TLS stack instead of something higher-level like WebRequest (or maybe Chrome makes it impossible to do that)?
link