Firefox 115 can silently remotely disable my extension on any site

8 comments

I was also a little concerned when I saw this in the release notes earlier today. Why not make this opt-in (with a warning explaining the reasoning behind it) rather than opt-out via about:config?!
Seems to be much ado about nothing currently. Even in the release notes it clarified that this feature is not yet included and the quarantine list will be shared once ready (and will at first be mostly test domains). The blog seems to be wildly speculating on its intended use and possible impacts given the knowledge currently available
- Why? This is like some authoritarian clause in a new law being introduced with a reassurance that it will only be used for national security purpose. I feel the author is correct until more explanation is given. Even then it does not look good to me.
Doesn't look all that silent to me?
does using librefox help circumvent this ? also we got too comfortable with corps . do we need to build our own naviagtor now ?
Won't people just see this error, do a quick search and end up disabling this in the about:config?

Seems like a waste of dev time

8 comments