Yeah with Chrome’s announcement they are bringing back “Manifest API” next year, the internet is going to become really fragmented. Many sites will slowly switch to only supporting browsers that support it, and in turn don’t support ad blockers. And switching to another browser, or changing your user agent string will no longer work.
Step 1. Get a lot of smart people interested in working on technology.
Step 2. Make the world a shitty place so many of those people will do whatever jobs pay the highest.
Step 3. Corner software markets so that the goal of widely used software is purely to accelerate quarterly profits.
“Manifest API” has always been a thing. It’s only for extensions and DO NOT affect website support. You’re misreading the situation with Manifest v3 almost completely. Here, “Manifest” refers to the API used for extensions. The biggest differences are 1. Switching from always-on pages to services 2. Sabotaging the Adblock API, basically. User agents are unaffected. Websites do not care about it (except those who are anti Adblock).
You may be confusing things with WebEnvironmentIntegrity, which has been canceled with the team shifting focus to an Android-exclusive WebViews API which I haven’t studied yet.
Yeah with Chrome’s announcement they are bringing back “Manifest API” next year, the internet is going to become really fragmented. Many sites will slowly switch to only supporting browsers that support it, and in turn don’t support ad blockers. And switching to another browser, or changing your user agent string will no longer work.
Step 1. Get a lot of smart people interested in working on technology.
Step 2. Make the world a shitty place so many of those people will do whatever jobs pay the highest.
Step 3. Corner software markets so that the goal of widely used software is purely to accelerate quarterly profits.
“Manifest API” has always been a thing. It’s only for extensions and DO NOT affect website support. You’re misreading the situation with Manifest v3 almost completely. Here, “Manifest” refers to the API used for extensions. The biggest differences are 1. Switching from always-on pages to services 2. Sabotaging the Adblock API, basically. User agents are unaffected. Websites do not care about it (except those who are anti Adblock).
You may be confusing things with WebEnvironmentIntegrity, which has been canceled with the team shifting focus to an Android-exclusive WebViews API which I haven’t studied yet.