Technology

59374 readers

7834 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

1018

Google Chrome warns uBlock Origin may soon be disabled (www.bleepingcomputer.com)

submitted 3 months ago by [email protected] to c/[email protected]

448 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 29 points 3 months ago (7 children)

I honestly can't wait to see how this plays out. Only Chrome, chromium and edge in their pure forms have dedicated to doing this. Most of the Chrome forks have said they're going to fork and keep it running. It's certainly going to give Firefox a shot in the arm, but there's no lack of other competition either.

[–] [email protected] 12 points 3 months ago (1 children)

I don't know how long the forks will be able to backport new features to their forked codebase.

I think the only sensible solution is to just switch to Firefox.

[–] [email protected] -5 points 3 months ago (1 children)

Eventually Firefox will switch to V3 anyway so it's kind of just delaying the inevitable.

It sucks that this is the future of the Internet.

[–] [email protected] 9 points 3 months ago (1 children)

Manifest v3 is already supported in Firefox (they must support it to keep the extension ecosystem alive), but they implemented it without the user-hostile restrictions.

[–] [email protected] 6 points 3 months ago* (last edited 3 months ago)

Oh, I wasn't aware of that, I thought the user-hostile restrictions were inherent to Manifest v3 and they were unavoidable.

Okay, maybe just maybe Firefox squeaks by unharmed then.

edit: I literally just had someone else tell me just now that "It’s not something that can be worked around. It’s specifically a design feature of manifest v3 to restrict these types of things."

So which is it? I'm kind of getting mixed signals here.

edit 2: Oh, it sounds like Google has additional arbitrary restrictions on content blocking functionality, beyond what Manifest V3 itself has.

load more comments (5 replies)