this post was submitted on 31 Aug 2026
824 points (99.5% liked)

Technology

87744 readers
3249 users here now

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

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
824
Google Has Removed Manifest V2 Extensions From the Chrome Web Store, Including uBlock Origin (webiterate.dev)
submitted 1 day ago* (last edited 1 day ago) by inari@piefed.zip to c/technology@lemmy.world
164 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] timewarp@lemmy.world -2 points 14 hours ago (1 children)

This is extremely funny that you’re trying to insult me, based on your feelings and not facts.

My only participation in this thread was that UBO Lite creator disagrees with you, which he publicly stated, but you felt… Offended? (No idea) - and decided to insult me rather than to deal with facts.

There is a word for people like you.

Troll.

Citing gorhill’s disclaimer that uBOL isn’t a 1:1 clone of uBO doesn’t prove Chrome is "ad-infested"—it conflates advanced power-user filtering with everyday ad blocking. Many limitation were Firefox-exclusive APIs that Chrome MV2 never supported in the first place.

Under the hood, standard filter lists compile directly into native C++ evaluation via declarativeNetRequest, while cosmetic element hiding and anti-adblock defusers run through the scripting and userScripts APIs. Furthermore, synchronous webRequestBlocking is still built into the Chromium engine for policy installs. Pointing out the architectural reality of how these APIs actually execute isn't trolling; it's addressing technical mechanics rather than hyperbole.

[–] ThirdConsul@lemmy.zip 1 points 8 hours ago

Pointing out the architectural reality of how these APIs actually execute isn’t trolling

Cool. Except that you didn't do that before. You're doing that now, after the fact.