Permanently hack/fixing Chrome/Chromium-legacy browsers from deleting extensions?

[Minghold]

Screen-clipped from this discussion:
____________________________

____________________________

Concerning the corruption, that's just straight-up lying. Google is an adpimp, it knows that we know it, but gaslights us all anyway peddling its excuses for deleting our adblocking extensions (these are the overwhelming favorite of everyone who knows how to enable them in the first place).

Concerning the last paragraph, my conclusion is that it's making hardware ID checks. For example, installing Chromium-legacy on an old Mac, it'll retain extensions for...awhile anyway. But if the boot-drive is an external, and I sneaker to another Mac and boot it, all browser extensions are wiped & settings defaulted. (The same behavior is noticed in Google Chrome, Chromium, Chromium-legacy, Opera, Brave, and Vivaldi, as it seems the same code is shared by all chrome-based browsers.)

I'd like to hope there's an about:config toggle-setting to disable this behavior, or something else as easily carved out with a knife.

 

[Okerew]

The only solution I think would be viable is google sync, the behavior you are describing is most likely because some app is trying to edit the manifsest.json file

 

[Minghold]

The only solution I think would be viable is google sync, the behavior you are describing is most likely because some app is trying to edit the manifsest.json file

While that would probably also trigger it, it's not what's happening here. For instance, I have a USB boot drive, and all this required to trigger the behavior is booting a different machine -- which makes it a PITA to mass-refurb dozens of machines with curated browser-extension load-outs.

 

[Okerew]

While that would probably also trigger it, it's not what's happening here. For instance, I have a USB boot drive, and all this required to trigger the behavior is booting a different machine -- which makes it a PITA to mass-refurb dozens of machines with curated browser-extension load-outs.

Well then there is a posibility that some app does a hwid check, I don't beleive that this is a problem with chromium.

 

[Minghold]

Well then there is a posibility that some app does a hwid check, I don't beleive that this is a problem with chromium.

It's a problem with, insofar as I am aware, all chome-based browsers. I.e., none of the various forks have expunged the offending code.