Technology

59374 readers

7033 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]

662

Google is Killing uBlock Origin. No Chromium Browser is Safe. (www.quippd.com)

submitted 4 weeks ago by [email protected] to c/[email protected]

274 comments fedilink hide all child comments

We’ve been anticipating it for years, and it’s finally happening. Google is finally killing uBlock Origin – with a note on their web store stating that the extension will soon no longer be available because it “doesn’t follow the best practices for Chrome extensions”.

Now that it is finally happening, many seem to be oddly resigned to the idea that Google is taking away the best and most powerful ad content blocker available on any web browser today, with one article recommending people set up a DNS based content blocker on their network 😒 – instead of more obvious solutions.

I may not have blogged about this but I recently read an article from 1999 about why Gopher lost out to the Web, where Christopher Lee discusses the importance of the then-novel term “mind share” and how it played an important part in dictating why the web won out. In my last post, I touched on the importance of good information to democracies – the same applies to markets (including the browser market) – and it seems to me that we aren’t getting good information about this topic.

This post is me trying to give you that information, to help increase the mind share of an actual alternative. Enjoy!

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

[–] [email protected] 19 points 4 weeks ago (8 children)

.... or use Firefox and migrate their bookmarks.

[–] [email protected] -1 points 4 weeks ago* (last edited 3 weeks ago) (5 children)

I recently switched back to Firefox, and almost immediately ran into an issue where I couldn't log into Dropbox. It took me far longer than I'd like to admit, to realize that ~~Firefox was the problem~~ it wasn't working because Dropbox doesn't properly support Firefox. I popped into edge and logged in immediately no problem.

I'm still gonna stick with Firefox, but it's annoying that it doesn't work all the time.

Edit: what's with the down votes? I like Firefox, I'm using Firefox, but I won't deny that I ran into issues with it 🤷‍♂️

Edit 2: I realize now that the tone of my message sounds like I'm blaming Firefox. That was not my intention. It's a complicated issue and they are getting a rough deal. Not their fault. I've struck out the offending line.

[–] [email protected] 2 points 3 weeks ago (1 children)

This is part of Googles strategy. Ever since the Chromium engine took off enough and everyone else fell behind they began introducing more and more changes that merely benefits them, with less public debate or proper communication (or even adherence to common standards). Last thing I remember, aside of manifest v3, was them killing off JPEG XL as it was a competitor to webp and webm (which they control). JPEG XL was actively worked on and would've probably turned out better before they killed it without any previous notice.

Given Googles dominant market position, their influence and everyone wanting to cut corners wherever possible sometimes Firefox support is just ignored.

tl;dr It's not Firefox' fault. It's Google's sabotage.

[–] [email protected] 2 points 3 weeks ago

Ah I see, it sounds like I'm saying it's Firefox fault. No I definitely agree, chromium is the largest market share, and gets the most support, and doesn't always follow standards, so some websites will have compatibility issues if they don't specifically focus on Firefox support.

It's just a sucky situation.

load more comments (3 replies)

load more comments (5 replies)