• 0 Posts
  • 6 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2023

help-circle

  • I know how MV3 works, thanks. The point remains that from the moment it was announced people have been claiming, usually with much hyperbole, that Chrome was trying to kill adblockers, and yet here we are with adblockers still blocking ads. In terms of software engineering, I actually find it interesting that they managed to achieve the stated goal of preventing a certain class of malware extensions while letting adblockers still work (though I know it’s not a widely shared sentiment).

    Mind you, I still preferred living in an MV2 world, and I still encourage people to switch to Firefox. It’s better for everyone if the ecosystem is more diverse.




  • I studied at the PR in question and that’s not the conclusion I arrive at. Let me try to explain how this looks to me.

    Also keep in mind, I do think we absolutely need to keep the political pressure on and push back on identity-gating policies with all our collective might. In that light the PR itself does the two things I’d absolutely require here: one, it allows the user to put whatever value they want in that field, including none at all, and two, it disallows all apps from reading that field without the user’s active permission.

    Basically it’s a superficially valid implementation of a bullshit requirement that still leaves all the power in the user’s hands and therefore renders the requirement meaningless. Or in other words, a huge middle finger to the proponents of age-checking.

    Mind you, I feel there’s also value in loud non-compliance and I’m glad some are taking that road – keep it up, folks. But I’m leery of demands that only one single approach be taken. This needs to be fought on every front we can. And to me the PR in question reads like an effective defensive move.