Google: Difference between revisions

Line 37:

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 this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.

'''Google Jamboard shutdown'''

In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.

The Jamboard product was a $5,000 device that Google pitched as a collaborative tool through its Google Workspace service. After the service no longer existed, however, the device became a brick and the users as well as the buyers were left unsupported and uncompensated.

Situations like this highlight the vulnerability of the consumer market since proprietary products are completely at the hands of developers who can cut services on a whim. Thus, consumer protection must be taken to another level to ensure that no matter what companies get rid of, support and compensatory avenues exist.

===Google Assistant 3rd Party List Support===

@@ Line 37: / Line 37: @@
 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 this is dubious; restricting content blockers prevents users from impeding their tracking and surveillance, meaning they can create a larger profit from the data gained. This is likely the ulterior motive, although unproven.
+'''Google Jamboard shutdown'''
+In September 2023, Google revealed plans to retire its Jamboard service, as the product would be transitioned to a view-only format by October 1, 2024, and completely shut down by December 31, 2024. As a result, users had little time to transfer their data before the final transition and no refunds were ever issued to hardware buyers.
+The Jamboard product was a $5,000 device that Google pitched as a collaborative tool through its Google Workspace service. After the service no longer existed, however, the device became a brick and the users as well as the buyers were left unsupported and uncompensated.
+Situations like this highlight the vulnerability of the consumer market since proprietary products are completely at the hands of developers who can cut services on a whim. Thus, consumer protection must be taken to another level to ensure that no matter what companies get rid of, support and compensatory avenues exist.
 ===Google Assistant 3rd Party List Support===