Google’s campaign against ad blockers across its services just got more aggressive. According to a report by PC World, the company has made some alterations to its extension support on Google Chrome.
Google Chrome recently changed its extension support from the Manifest V2 framework to the new Manifest V3 framework. The browser policy changes will impact one of the most popular adblockers (arguably), uBlock Origin.
The transition to the Manifest V3 framework means extensions like uBlock Origin can’t use remotely hosted code. According to Google, it “presents security risks by allowing unreviewed code to be executed in extensions.” The new policy changes will only allow an extension to execute JavaScript as part of its package.
Over 30 million Google Chrome users use uBlock Origin, but the tool will be automatically disabled soon via an update. Google will let users enable the feature via the settings for a limited period before it’s completely scrapped. From this point, users will be forced to switch to another browser or choose another ad blocker.
If it keeps going on like this, it won’t be long before I’ll just say fuck it and switch to elinks…
Hmm, on that note - is there any CLI web browser that can do javascript and css? Because iirc, elinks doesn’t, though I havent used it in years.
Lynx ftw! Not sure if that’s been maintained since the 90s though.
You can’t improve on perfection!
Lynx is still actively maintained. I use it from time to time when I don’t feel like leaving the command line to look something up or whatever. It works really well still. So long as all you care about is text.
If you like to use reader mode you’ll probably like Lynx.
browsh does, but uses FF as backend renderer
Holy mother of BASED
The sooner you abandon javascript and css, the sooner you can be free
Elinks for can do basic CSS & JS. I wish there were better support for like 256 or 16 color modes for CSS to better support TUIs. The reading UX is generally pretty good, but stuff like syntax highlighting really helps. …That is if website makers did their job correctly & treated JavaScript as an enhancement. The bigger issue is even in the case of limited JS support like Netsurf, most developers aren’t going to be writing ES3 or ES5-compatible code which is about all most of these systems can support which means the JS will be broken anyhow without keeping their engines up to date.
https://github.com/fathyb/carbonyl
This is more usable than browsh, in my experience, but has the very unfortunate downside of being based on Chromium (🤢)