Web ad giant Google to block ad-blockers in Chrome

Email
Comment *
File	Select/drop/paste files here
Password	(Randomized for file and post deletion; you may also set your own.)
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Comment *

File

Select/drop/paste files here

Password

(Randomized for file and post deletion; you may also set your own.)

* = required field

[▶ Show post options & limits]
Confused? See the FAQ.

Flag
Oekaki	Show oekaki applet (replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, pdf Max filesize is 16 MB. Max image dimensions are 15000 x 15000. You may upload 3 per post.

Flag

Oekaki

Show oekaki applet
(replaces files and can be used instead)

Options

Do not bump
(you can also write sage in the email field)

Spoiler images
(this replaces the thumbnails of your images with question marks)

Allowed file types:jpg, jpeg, gif, png, webm, mp4, pdf
Max filesize is 16 MB.
Max image dimensions are 15000 x 15000.
You may upload 3 per post.

[–]

▶Web ad giant Google to block ad-blockers in Chrome Anonymous 01/27/19 (Sun) 02:06:54 No.1023713[Watch Thread][Show All Posts]

Web ad giant Google to block ad-blockers in Chrome.

https://archive.fo/190dp

>Google engineers have proposed changes to the open-source Chromium browser that will break content-blocking extensions, including ad blockers.

>If the overhaul goes ahead, Adblock Plus and similar plugins that rely on basic filtering will, with some tweaks, still be able to function to some degree, unlike more ambitious extensions, such as uBlock Origin, which will be harder hit.

>In a note posted Tuesday to the Chromium bug tracker, Raymond Hill, the developer behind uBlock Origin and uMatrix, said the changes contemplated by the Manifest v3 proposal will ruin his ad and content blocking extensions, and take control of content away from users.

>Content blockers may be used to hide or black-hole ads, but they have broader applications. They're predicated on the notion that users, rather than anyone else, should be able to control how their browser presents and interacts with remote resources.

▶Anonymous 01/27/19 (Sun) 02:31:27 No.1023717

Prepare to be bumplocked

▶Anonymous 01/27/19 (Sun) 02:50:47 No.1023719>>1023792

>Following a huge outcry from plugin developers and netizens, Google has reiterated that the proposed changes are not set in stone, and are subject to revision. While the internet goliath wants to rein in the level of access granted to Chrome browser extensions, it is prepared to work through the messy matter with third-party coders -- who will have to rewrite parts of their software if this all goes ahead.

So FUD for now?

▶Anonymous 01/27/19 (Sun) 03:47:03 No.1023735

We already have a thread on this mongloid

▶Anonymous 01/27/19 (Sun) 07:31:35 No.1023792

>>1023719

This is the same thing mozilla said. "We will work with developers." They don't give a fuck, they want to do a rewrite. If you get burned it's because they don't give a fuck about you. If you complain, they'll tell you that 40% of people don't even use addons, and you're lucky they're keeping any at all. You think google is going to be more willing to compromise then mozilla was? Get real.

This is standard marketdroid speak. Deny there is an issue constantly, say that everything will work out just fine if you wait. Then after it happens, they say yes this is an issue but it's too late, it already went through. They want to keep people calm, without having to actually change their business plans. Until they say "every feature of ubo will be supported in their full existing capacity" then I will continue to call bullshit.

Some food for thought: suppose that ubo and other addons used these apis in a way google plans to support in manifest v3. In that case, there would exist a version of these apis that contained whatever changes google wants, but were backwards compatible. Someone in one of threads suggested running the web request filtering code in a vm with restricted run time. That would enable existing addons to continue working, while preventing abuse of the api. Google isn't doing that, because they don't want existing addons to keep working. There are addons they want to break, and they're breaking compat with these apis to do that.

▶Anonymous 01/27/19 (Sun) 07:44:57 No.1023795

This will just push people to network layer solutions like Adguard.

▶Anonymous 01/27/19 (Sun) 07:48:48 No.1023798

Just enable the blocker-blockers then.

▶Anonymous 01/27/19 (Sun) 08:49:02 No.1023821

lol chrome is the browser for idiots anyway

/tech/ - Technology★

General

WebM

Theme

User JS

Do not paste code here unless you absolutely trust the source or have read it yourself!

Favorites

Customize Formatting

Filters