Yeah this is problematic for open source software. Plenty of better ways to implement a security feature. Seems they will probably end up blocking adblockers eventually with features like this. Why was it approved, surely there is some discussion on the Dev mailing lists?
That’s worrying. I wasn’t surprised that google did it with chrome, but this is surprising. I was thinking surely people would be looking to fork it and take it in a different direction. Maybe it’s finally time to switch to another browser. With just chromium and Mozilla engines, I wonder what the good options would be.
Yeah this is problematic for open source software. Plenty of better ways to implement a security feature. Seems they will probably end up blocking adblockers eventually with features like this. Why was it approved, surely there is some discussion on the Dev mailing lists?
The bug tracker almost has no discussion, just a few comments. I archived it on Wayback Machine personally, nobody did it in 2 days.
That’s worrying. I wasn’t surprised that google did it with chrome, but this is surprising. I was thinking surely people would be looking to fork it and take it in a different direction. Maybe it’s finally time to switch to another browser. With just chromium and Mozilla engines, I wonder what the good options would be.
There does exist override option. Read blog post I linked. user.js still retains all the power we need.