161–170 of 416 posts
Earlier quoted context omitted.
It's probably just a mistake and not actually trying to collect anything.
You think it’s hitting the JavaScript microphone API by mistake? How?
Earlier quoted context omitted.
But you know, we wouldn't stop serving ads until we work it out... no no imagine the loss in revenues.
Let's be adults here. This is SO, and I imagine you've used and enjoyed the use of their services just like the rest of us. Support them by letting passive ads sit on the edges of the page, and appreciate that they are actually trying to solve this issue.
Earlier quoted context omitted.
But you know, we wouldn't stop serving ads until we work it out... no no imagine the loss in revenues.
Let's be adults here. This is SO, and I imagine you've used and enjoyed the use of their services just like the rest of us. Support them by letting passive ads sit on the edges of the page, and appreciate that they are actually trying to solve this issue.
Earlier quoted context omitted.
They realized it was a risk so they built their own browser to have more control. And it worked. Only now, users are wising up and moving to Firefox.
Is firefox less fingerprintable?
I just wanted to chime in from Stack Overflow here and let people know: we are aware of the issue. And we're NOT okay with it. We're trying to sort out how to kill the audio behavior now. It's not very straightforward to find where it's coming from, but we are working on it. We've also reached out to Google for their assistance in tracking it down. If anyone can offer advice, we'll more than happily take it. - Nick C…
If you're serious about this, I've built tools for the publisher side for stopping exactly this.
My email address is in my profile.
Earlier quoted context omitted.
I think the data in aggregate is worth more than people like you would pay for an ad-free service.
This is the actual problem at the heart of it all. And even if it were more profitable to take subscription fees than to serve ads, what's stopping you from "double dipping" and serving ads anyway?
People looking at the source code, like what happened here.
Earlier quoted context omitted.
You think it’s hitting the JavaScript microphone API by mistake? How?
It's Google's fingerprinting for tracking you across the web. It won't actually listen to or play anything, it just opens it up to see if it's there.
Earlier quoted context omitted.
But you know, we wouldn't stop serving ads until we work it out... no no imagine the loss in revenues.
Let's be adults here. This is SO, and I imagine you've used and enjoyed the use of their services just like the rest of us. Support them by letting passive ads sit on the edges of the page, and appreciate that they are actually trying to solve this issue.
And this is why, even with the best intentions of site operators, my browser will continue to use the best ad-block tools I can get, and my networks will be protected by tools like PiHole.
Considering the alternatives, that sounds really appealing for me. I'd also buy it for my less tech-literate parents.