so turns out you can *still* use ublock on chrome if you just inspect element it lmfao

[todepond@mas.to]

@rebane2001 WHAT

[chaoskitsune@woem.men]

@rebane2001@infosec.exchange This is so amazing wow

[dcoderlt@ohai.social]

@k @rebane2001
Almost, the last bits will be removed in v151 (next version, currently in beta) IIRC.

[irelephant@app.wafrn.net]

@rebane2001@infosec.exchange

I've found that ublock origin lite still works fine for most stuff.

[freddy@social.security.plumbing]

@rebane2001 are you sure the underlying webrequest APIs will continue to work though? Works best in Firefox https://github.com/uBlockOrigin/uBlock-issues/wiki/uBlock-Origin-works-best-on-Firefox

[breizh@pleroma.breizh.pm]

@rebane2001@infosec.exchange Ok, but does it works. Since they deleted the last parts of Manifest v2 recently…

[jesterchen@social.tchncs.de]

@rebane2001 Using F12 is a criminal offense!

[simonzerafa@infosec.exchange]

@rebane2001

uBlock Origin Lite still works

Mozilla Firefox or it's derivatives work even better with uBlock Origin

[lightning5@chaos.social]

@rebane2001 Why not use Firefox with uBlock origin?

Chrome is nice and all... But we should try to support open platforms that don't take features away from us

[hiiaminfi@mastodon.social]

@irelephant @rebane2001 or you could use a better browser. At this point I would rather use edge.

[qroole@flipboard.social]

@rebane2001 That's quite an interesting workaround you've found, Rebane! It's always fascinating to see how users find clever ways to keep their preferred tools working, especially with all the browser changes. Thanks for sharing your discovery with everyone.