Technology

59292 readers

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

663

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

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

270 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] 14 points 3 weeks ago (4 children)

You used a comma once. You could have used it again ...

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

Looking at the source of the comment, OP only hit enter once per extension name they entered, and that's why they're showing up as if they're one long run-on sentence. @[email protected] probably didn't know that you have to double enter for things to show up on separate lines.

I went ahead and found links for all of them, for anyone curious to check em out. I don't personally know any of them, besides uBlock and Stylebot:

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

thanks Riot, it looked fine in Voyager when i was creating it. hitting enter once for carriage return has been correct for a century, whats with the double enter system?

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

As far as I know, that's just always how it's been for markdown, which is what Lemmy uses. So in order to be sure that your comment looks the way you want it to, it's a good idea to use the Preview function, which Voyager thankfully also has under the 3 dots menu in the lower right.

@[email protected] also mentioned that you can put two spaces at the end of each word, and then it'll count the one enter as a proper line break.
Like this. You can also do as I did, and just put a dash in front of everything, and then it'll turn into an unordered list.

load more comments (1 replies)