• 0 Posts
  • 198 Comments
Joined 4 years ago
cake
Cake day: June 23rd, 2020

help-circle
  • The fundamental problem is that a web engine is one of the most massively complex pieces of software that we currently use. There are a ridiculous number of standards and behaviors that a modern web browser needs to implement, as well as a whole host of security implications that need constant updating. It’s not like the majority of other software projects, where a determined solo dev or even small group can strike out on their own. It really requires a team of dozens or hundreds of developers putting in consistent effort, which basically means a corporate entity.















  • Because currently the ads are tracking every user personally across as many sites as possible and serving them ads based on that data. It’s preferable to eliminate the personal data and only give them the ad click data.

    Are no ads better? Yes. But this API is better for users than the status quo, and does nothing to reduce the effectiveness of blockers.




  • verdigris@lemmy.mltoLinux@lemmy.mlFirefox enables user tracking
    link
    fedilink
    arrow-up
    3
    arrow-down
    7
    ·
    edit-2
    4 months ago

    … No, it does not. The ads are currently already tracking clicks and conversions, on top of a whole boatload of other personal data. This API instead provides them with just the click and conversion data, divorced from the personal data and then aggregated with all the other site visitors.

    Being against this proposal basically means you trust random websites and ad companies more with your data then you do Mozilla and LetsEncrypt.