upvote
deleted
reply
"Hundreds of GB per month" is, at least, 70KB/s, which should be pretty easy for anyone to observe. So is your Chrome doing it?

My hypothesis is this guy installed so many shady ad blockers and VPNs that were using his rig as a proxy, and the cessation of such traffic, whether permanent or temporary, was purely coincidental.

reply
> 70KB/s, which should be pretty easy for anyone to observe

But also low enough that most of us wouldn't actually notice

reply
Your take is 'probably' correct.

The problem here is without a deep dive you just don't know. Google likes A/Bing the shit out of their software. Google loves setting all kinds of different options that may have to be replicated exactly to get the same behavior.

This isn't like support back in the old days where you just look at your software and find the bug, you have to replicate the environment to see what's up.

reply
OK but the OP provided zero evidence. Chrome has chrome://net-export/ for a reason. Show us logs.
reply
> The problem here is without a deep dive you just don't know.

Without knowing, you don't accuse.

reply
Spotify had a bug where it was writing ten to hundreds of GB to people their SSDs, each day. HN refused to believe it until Spotify acknowledged it. "You must have just injected some shady JavaScript mod".
reply