Jan Wildeboer 😷Apr 23, 2024
What happens when every time your browser sends data to a tracker it makes a beep sound? Well, @bert_hubert did just that. And it sounds like you are listening to an old school modem. Creepy stuff! https://berthub.eu/articles/posts/tracker-beeper/
Tracker Beeper - Bert Hubert's writings

A week ago, I finally got round to implementing an idea I’d been toying with for years: what if your computer made a little bit of noise every time it sent data to Google? From studying logs, I’d long known just how many sites send all your visits and clicks to (at least) Google, but a log that you have to manually create first and then analyze is not very dramatic.

Bert Hubert's writings
Show threadJan Wildeboer 😷Apr 23, 2024
To all the commenters explaining how to make this go away: That's not the point. At all. The majority out there has to deal with this stuff and they don't even know. That's what this experiment is about.
Show threadJan Wildeboer 😷Apr 23, 2024
IMHO (In My Humble Opinion) the real question is: Why do browsers share all of this? (And it's not just Chrome. These are Web Standards, so all browsers share this) Why isn't there a simple option to say "Read-Only, send no data back except for which page I want to see"? The web is not we want it to be, IMHO.
Show threadHaelwenn /элвэн/ 
@jwildeboer You could try to address this on the software side but trying to fix social problems with technical solutions is a red herring.
For example you'd just get even more first-party trackers instead, or everything being done behind the user's back. What this shows is an easily visible part of the iceberg.
Apr 24, 2024 at 3:28pmWeb