Live data from Hacker News

Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

theregister.com

301–310 of 394 posts

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#301

For me (I imagine a lot of others as well), it's simple. If Chrome removes adblock, I'm going back to Firefox. HN ilk don't represent a good target market. Can't really make money off traditionally tracked ads off of us. FWIW, I love Chrome, still do. I've been here since those entirely useless but super viral and catchy speed test ad/vids. It worked on me. I love the debugger as a web developer, more so than Firebug…

Already running a worse version of ublock origin:

https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

Recent Firefox, atleast on Windows 10, is just as fast as Chrome for me. With addons like vertical tabs, adblock it has more features too.

Vivaldi is still the features and UI king but too slow for me.

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#302

Earlier quoted context omitted.

What... Is the appeal of brave ? I hear it has crypto and shit but why not install Firefox with ubo and be done with it? I feel the "cool" factor of brave is silly as they are just fueling chromium. Why don't these chromium forks base on Firefox instead and do some leg work with the benefit of helping the internet as a whole ? I hear someone said on hn a long time ago, building on ff is a pita. Well guess what, Firef…

There are several things. 1) There is an integrated ad blocker. It's very convenient because I don't have to worry about adblocking plugin is bought out and is compromised, I don't have to figure out if my uBlock is supposed to be "origin" or not, or if I should go for adGuard or something else. There is no risk of adblocking breaking because of the changes in plugin API. 2) Integrated optional ad network that by def…

1) uBlock Origin has been around and without selling out for 6-7 years now. You don't have to worry that the plugin is bought out but you do have to worry that the browser is. You don't have to figure out which adblocker to use, because there is only one right answer. And it takes barely thirty seconds of effort.

I have no opinion about 2.

3 is fair, but I have similar objections about Brendan Eich.

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#303
post #254

I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?

I was driven back to Firefox the second I noticed that Chrome had started logging me into my Google account. Been using it happily ever since (FF on MacOS). The only time I open Chrome now is to test websites I'm working on.

That may be a deal breaker for you. But for others it's a necessary feature! Firefox added it as a feature and I love it! And I say that as a person with a very anti-Google stance. Perhaps it's an area that is ripe for disruption but without using the browser or Javascript.

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#304

I've always used Chrome but recently I've been trying out Brave and its been quite interesting. I still use chrome, but if they were to remove adblock i'd move for good.

Brave is okayish if I got through and turn off all the default shit like:

- Sponsored backgrounds

- Cards

- Brave Rewards icons

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#305

The moment uBlock Origin stops working on Chrome is the moment I will switch to a different browser. Fortunately I have no loyalty to a browser.

You might aswell switch today.

https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#306

This is particularly amusing considering Google's extreme lack of v3 documentation. Their samples and examples Github, for example, has only 2 examples, iirc. They also introduce a lot of silliness like the inability to nest content scripts within folders. Not to mention all the limitations of the Chrome browser. The continuous difference between console.log and console.dir. The former only shows you a very limited v…

It's interesting that you mention Chrome’s silliness when I find Firefox’ dev tools to be severely lacking, especially for WebExtensions. Examples include:

    - complete inability to run code from the console into the content script context
    - content script errors are not shown in the console, you have to open a separate Browser Console
    - overall buggy dev tools (I don't remember anymore because I stopped using them a long time ago)
I guess every browser lacks something, it's just that we notice when we compare "my browser" to the next one.

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#307

As someone who is intimately familiar with the Chrome extensions internals and is not employed by a big tech company, I believe most of the changes seem like a step in the right direction.* I've been working towards implementing greater support for Chrome extensions in Electron which has involved reading and interacting with Chromium code [0]. - Using service workers instead of a hidden background webpage is more idi…

>idiomatic

>less resources

Are you an extension developer? Here is a list of issues that extension developers have with requiring Service Workers:

https://github.com/w3c/webextensions/labels/topic%3A%20servi...

Just take a look at this work-in-progress MV3 version of a fairly popular webpage-saver extension called SingleFile:

https://github.com/gildas-lormeau/SingleFile-Lite#readme

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#308

As someone who is intimately familiar with the Chrome extensions internals and is not employed by a big tech company, I believe most of the changes seem like a step in the right direction.* I've been working towards implementing greater support for Chrome extensions in Electron which has involved reading and interacting with Chromium code [0]. - Using service workers instead of a hidden background webpage is more idi…

I remember some people saying Safari's extension changes and specific content blocker API would be a good thing because ad blockers would use less resources. The change happened, uBlock Origin broke for Safari and here we are several years later and the Safari ad blocker ecosystem is an absolute joke and most of it barely works or demands subscription fees (and the ones that do are certainly not worth paying for beca…

Enrolled in the Orion browser beta and haven't looked back. I get Safari's engine with all the energy optimziations with the ability to run uBlock Origin, Dark Reader, and they're working on greater WebExtensions API support.

I still use Safari for banking and eCommerce because its beta, but for everything else its wonderful. I even get a quality vertical tabs implementation built into the browser; can also shrink the top bar to pre-14/15 size in combination.

The browser will eventually be behind a paywall once the beta is up, but I'm all onboard for paying for an alternative to both Chromium and non-XUL Gecko.

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#309

Earlier quoted context omitted.

Chrome syncs things like bookmarks and credit card numbers across browsers whenever a user logs into a Google property. Pocket is Firefox trying not to fall behind on features. And presumably from Mozilla's perspective, if it has some sponsored content giving them some non-Google income, so much the better.

Firefox has Bookmark, Settings, Extension sync and send-tab to device features independently of Pocket.

pocket is mainly an article reader and not really a bookmark service. the whole point is you don't have to send tab of some js heavy news website, you can just have the clean reader view from pocket.

Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow

#310

Earlier quoted context omitted.

It did for me. I went back to firefox a year ago.

I never left. But then I again, I replaced everything Google with paid or self-hosted alternatives about 10 years ago. From what I hear, the Google ecosystem itself can be pain on Firefox. Although I check my old Gmail once every couple of weeks and I find it to work well enough. Maybe if you live in things like Google Docs, you start getting annoyed by accumulating papercuts? No idea..

I've never had an issue doing anything in gsuite on firefox and i run ublock origin too.
Post reply on HN