Old Manifest V2 Chrome extensions will be disabled in 2024

dvdnet89@lemmy.today to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 262 points –
Old Manifest V2 Chrome extensions will be disabled in 2024
9to5google.com
111

You are viewing a single comment
  • I won't bother thinkering with CSS which break with updates
  • Users shouldn't be in charge to fix Mozilla's fuckups. That's how you loose 70M users since 2019
  • The only semi-valid reason people often give to use FF is uBlock Origin. I wonder how many of these FF loyal users would still stay on FF, should uBlock Origin disappear. Would you? At this point, it looks like FF is just an extension for uBO, rather than the opposite.
  • Last but not least, for a lot of reasons, I've grown increasingly pissed off with Mozilla, so I simply refuse to give then more underserved market share (after being a user/supporter/advocate for almost 20 years).

If you wouldn’t care to fix an issue then why complain

Ublock origin is on every browser, who do you think is only on Firefox because of it?

  • I don't complain. I just switched to a different browser.
  • What I mean is that FF is the only major browser which doesn't have an inbuilt adblocker and FF "fans" often brag about uBO working "best" on FF (because of the CNAME support), when there's at least another browser with and in-built adblocker which supports CNAME uncloacking. Without uBO FF usefulness would be exactly 0.