Lemmy.zip

2,809 readers
220 users here now

Welcome to Lemmy.zip - a community for like minded people to come and have a chat about almost anything. From games to tech, to anything else, come and have a chat.

If you're new and would like to join Lemmy.zip, please fill in the sign up form. Email verification is required. (Please check your spam folder!)

Once you're signed up, come and introduce yourself in our Home community!


Useful Links


Instance Rules

To maintain the high standard of discourse and interaction we all value, each user must adhere to the guidelines outlined in our Code of Conduct. This set of rules is designed not just to maintain order but also to ensure a safe and inclusive environment for everyone to share their thoughts and ideas.

What to Expect in Our Code of Conduct:

If you enjoy reading legal stuff, you can check out legal.lemmy.zip.


Funding

If you would like to contribute to the upkeep of Lemmy.zip, please head over to OpenCollective.
Anything you're happy to donate is very highly appreciated!
You'll even get your name in the Thank You thread.

Open Collective backers

If you want to use PayPal, you can donate via Ko-Fi:


Server

Uptime


founded 1 year ago
ADMINS
1
 
 

cross-posted from: https://lemmy.ml/post/19172415

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.

Archive link

2
 
 

Google ramps up its campaign against ad blockers on Chrome.

3
 
 

Google ramps up its campaign against ad blockers on Chrome.

4
 
 

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.

Archive link

5
6
7
8
 
 
  • Google is transitioning Chrome's extension support from the Manifest V2 framework to the V3.
  • This means users won't be able to use uBlock Origin to block ads on Google Chrome.
  • However, there's a new iteration of the app — uBlock Origin Lite, which is Manifest V3 compliant but doesn't boast the original version's comprehensive ad-blocking features.
9
 
 
This is an automated archive made by the Lemmit Bot.

The original was posted on /r/technology by /u/Old_One_I on 2024-08-14 20:34:11+00:00.

view more: next ›