Google: Difference between revisions
NotARobot06 (talk | contribs) Add details of why Manifest V2 shutdown is anti consumer (prevents ad content blockers from working). Minor grammar correction ("In <date>" replaced with "On <date>") |
|||
| Line 34: | Line 34: | ||
Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.<ref>{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here's how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central}}</ref> | Google Stadia controllers were limited to Wi-Fi connectivity, however upon shut down they started offering an update to allow them to connect through Bluetooth, the update service website was scheduled to shut down on the 31st December 2025.<ref>{{Cite web |last=Devine |first=Richard |date=17 Jan 2023 |title=Bluetooth support for Google Stadia Controller arrives — Here's how to enable it and play PC games |url=https://www.windowscentral.com/gaming/pc-gaming/bluetooth-support-for-google-stadia-controller-arrives-heres-how-to-enable-it-and-play-pc-games |url-status=live |access-date=5 Apr 2025 |website=Windows Central}}</ref> | ||
==== '''Manifest V2 shutdown''' ==== | ===='''Manifest V2 shutdown'''==== | ||
On July 24, 2025, Google permanently disabled all Manifest V2 extensions for Chrome 138 users, and disabled the ability to turn them back on.<ref>{{Cite web |date=2021-09-23 |title=Manifest V2 support timeline |url=https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-url=https://web.archive.org/web/20250808191702/https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline |archive-date=2025-08-08 |access-date=2025-08-12}}</ref> | |||
Manifest V3 disabled the <code>webRequestBlocking</code> permission in the <code>webRequest</code> API<ref>{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers}}</ref>, preventing many ad content blockers from working.<ref>{{Cite web |date=2024-09-26 |title=Understanding Manifest V3 and the Future of uBlock Origin |url=https://ublockorigin.com/ |url-status=live |archive-url=https://web.archive.org/web/20250812114916/https://ublockorigin.com/ |archive-date=2025-08-12 |access-date=2025-08-12 |website=uBlock Origin - Free, open-source ad content blocker}}</ref> Google cites performance reasons <ref>{{Cite web |date=2023-03-09 |title=Replace blocking web request listeners {{!}} Chrome Extensions {{!}} Chrome for Developers |url=https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |url-status=live |archive-url=https://web.archive.org/web/20250614074559/https://developer.chrome.com/docs/extensions/develop/migrate/blocking-web-requests |archive-date=2025-06-14 |access-date=2025-08-12 |website=Chrome for Developers |quote="In Manifest V2, blocking web requests could significantly degrade both the performance of extensions and the performance of pages they work with."}}</ref>, but the more likely reason is to restrict user conrol as content blockers impede their tracking and surveillance of users, decreasing their profits. | |||
==Controversies== | ==Controversies== | ||