<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ClippyIsAnArchUser</id>
	<title>Consumer Rights Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://consumerrights.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ClippyIsAnArchUser"/>
	<link rel="alternate" type="text/html" href="https://consumerrights.wiki/w/Special:Contributions/ClippyIsAnArchUser"/>
	<updated>2026-04-29T08:16:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Apple%27s_planned_obsolescence_incidents&amp;diff=20254</id>
		<title>Apple&#039;s planned obsolescence incidents</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Apple%27s_planned_obsolescence_incidents&amp;diff=20254"/>
		<updated>2025-08-17T00:14:09Z</updated>

		<summary type="html">&lt;p&gt;ClippyIsAnArchUser: Added a summary sentence at the top and separated it from the main-body text with a heading.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Apple actively makes it near-impossible for third-parties and consumers to repair their products while maintaining their full, intended functionality.&lt;br /&gt;
&lt;br /&gt;
==Product repair issues and software allegations==&lt;br /&gt;
Apple&#039;s implementation of planned obsolescence is primarily driven by technological obsolescence, encompassing hardware, firmware, and software limitations. The company&#039;s hardware design choices, such as proprietary screws, glued components, and complex internal layouts, make repairs difficult for consumers and third-party repair shops.&amp;lt;ref&amp;gt;{{Cite journal|url=https://www.researchgate.net/publication/353685307_From_Planned_Obsolescence_to_the_Circular_Economy_in_the_Smartphone_Industry_an_evolution_of_strategies_embodied_in_product_features|DOI=10.1017/pds.2021.422|first1=Mário|first2=Eric|last1=Barros|last2=Dimla|journal=Proceedings of the Design Society 1:1607-1616|title=From Planned Obsolescence to the Circular Economy in the Smartphone Industry: an evolution of strategies embodied in product features|date=August 2021}} &amp;lt;/ref&amp;gt; Firmware restrictions further limit repairability by disabling key functionalities when non-Apple components are used, as seen in battery and camera replacements, where users receive error messages and lose features like battery health monitoring and Face ID.&amp;lt;ref&amp;gt;{{Cite web |last=Disotto |first=John-Anthony |date=2023-05-16 |title=Does Apple build &#039;planned obsolescence&#039; into its products? French investigation to find out begins |url=https://www.imore.com/apple/does-apple-build-planned-obsolescence-into-its-products-french-investigation-to-find-out-begins |website=iMore}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Until recently, software updates also contributed to planned obsolescence by leading to performance degradation. Research has confirmed that Apple&#039;s software updates negatively impacted battery performance, often slowing down older devices and making them less functional over time.&amp;lt;ref&amp;gt;{{Cite news |date=2020-03-02 |title=Apple settles iPhone slowdown case for $500m |url=https://www.bbc.com/news/technology-51706635 |work=BBC}}&amp;lt;/ref&amp;gt; Apple has been criticized for discontinuing software support for older iPhone models, which forces consumers to upgrade to newer devices to maintain essential functions such as web browsing and email.&lt;br /&gt;
&lt;br /&gt;
Despite growing regulatory pressure, Apple continues to control its repair ecosystem by restricting access to spare parts and discouraging third-party repairs. On the French Repairability Index (&#039;&#039;[https://www.indicereparabilite.fr Indice de réparabilité]&#039;&#039;), the majority of iPhone models obtain a score lower than five out of ten.&amp;lt;ref&amp;gt;{{Cite web |title=Indice de réparabilité Smartphone |trans-title=Smartphone repairability scores |url=https://www.indicereparabilite.fr/appareils/multimedia/smartphone/page/3/?orderby=price |access-date=13 Feb 2025 |website=French Repairability Index |language=fr}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The EU-mandated transition in charging cables from Lightning to USB-C, affecting all smartphone manufacturers, required updates to existing accessories, reflecting a broader industry-wide standardization rather than forced obsolescence. &lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
In December 2022, French prosecutors opened an investigation into Apple over its part-pairing practice, which restricts third-party repairs. HOP, part of the Right to Repair Campaign, had previously filed a complaint, leading to Apple paying €25 million to the French treasury in 2020. HOP argues that this practice fosters planned obsolescence and harms sustainability efforts, advocating for a European ban on part-pairing. The investigation continues as part of broader efforts to protect consumer rights and encourage repairability.&amp;lt;ref&amp;gt;{{Cite web |date=15 May 2023 |title=Plainte contre Apple: le Procureur de la République ouvre l’enquête |trans-title=Complaint against Apple: the Public Prosecutor opens the investigation |url=https://www.halteobsolescence.org/plainte-contre-apple-le-procureur-de-la-republique-ouvre-lenquete/ |language=fr}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal actions against independent repair shops further solidify its control, making it difficult for users to extend the lifespan of their devices without relying on Apple’s costly repair services.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Apple IPhones]]&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;br /&gt;
[[Category:Planned obsolescence]]&lt;/div&gt;</summary>
		<author><name>ClippyIsAnArchUser</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Apple%27s_planned_obsolescence_incidents&amp;diff=20250</id>
		<title>Apple&#039;s planned obsolescence incidents</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Apple%27s_planned_obsolescence_incidents&amp;diff=20250"/>
		<updated>2025-08-17T00:05:12Z</updated>

		<summary type="html">&lt;p&gt;ClippyIsAnArchUser: 1. Added a couple of necessary citations. 2. Changed a couple sentences on the second paragraph to past-tense; making it clear that this was an incident of the past.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{StubNotice}}&lt;br /&gt;
&lt;br /&gt;
Apple&#039;s implementation of planned obsolescence is primarily driven by technological obsolescence, encompassing hardware, firmware, and software limitations. The company&#039;s hardware design choices, such as proprietary screws, glued components, and complex internal layouts, make repairs difficult for consumers and third-party repair shops.&amp;lt;ref&amp;gt;{{Cite journal|url=https://www.researchgate.net/publication/353685307_From_Planned_Obsolescence_to_the_Circular_Economy_in_the_Smartphone_Industry_an_evolution_of_strategies_embodied_in_product_features|DOI=10.1017/pds.2021.422|first1=Mário|first2=Eric|last1=Barros|last2=Dimla|journal=Proceedings of the Design Society 1:1607-1616|title=From Planned Obsolescence to the Circular Economy in the Smartphone Industry: an evolution of strategies embodied in product features|date=August 2021}} &amp;lt;/ref&amp;gt; Firmware restrictions further limit repairability by disabling key functionalities when non-Apple components are used, as seen in battery and camera replacements, where users receive error messages and lose features like battery health monitoring and Face ID.&amp;lt;ref&amp;gt;{{Cite web |last=Disotto |first=John-Anthony |date=2023-05-16 |title=Does Apple build &#039;planned obsolescence&#039; into its products? French investigation to find out begins |url=https://www.imore.com/apple/does-apple-build-planned-obsolescence-into-its-products-french-investigation-to-find-out-begins |website=iMore}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Until recently, software updates also contributed to planned obsolescence by leading to performance degradation. Research has confirmed that Apple&#039;s software updates negatively impacted battery performance, often slowing down older devices and making them less functional over time.&amp;lt;ref&amp;gt;{{Cite news |date=2020-03-02 |title=Apple settles iPhone slowdown case for $500m |url=https://www.bbc.com/news/technology-51706635 |work=BBC}}&amp;lt;/ref&amp;gt; Apple has been criticized for discontinuing software support for older iPhone models, which forces consumers to upgrade to newer devices to maintain essential functions such as web browsing and email.&lt;br /&gt;
&lt;br /&gt;
Despite growing regulatory pressure, Apple continues to control its repair ecosystem by restricting access to spare parts and discouraging third-party repairs. On the French Repairability Index (&#039;&#039;[https://www.indicereparabilite.fr Indice de réparabilité]&#039;&#039;), the majority of iPhone models obtain a score lower than five out of ten.&amp;lt;ref&amp;gt;{{Cite web |title=Indice de réparabilité Smartphone |trans-title=Smartphone repairability scores |url=https://www.indicereparabilite.fr/appareils/multimedia/smartphone/page/3/?orderby=price |access-date=13 Feb 2025 |website=French Repairability Index |language=fr}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The EU-mandated transition in charging cables from Lightning to USB-C, affecting all smartphone manufacturers, required updates to existing accessories, reflecting a broader industry-wide standardization rather than forced obsolescence. &lt;br /&gt;
&lt;br /&gt;
==Lawsuit==&lt;br /&gt;
In December 2022, French prosecutors opened an investigation into Apple over its part-pairing practice, which restricts third-party repairs. HOP, part of the Right to Repair Campaign, had previously filed a complaint, leading to Apple paying €25 million to the French treasury in 2020. HOP argues that this practice fosters planned obsolescence and harms sustainability efforts, advocating for a European ban on part-pairing. The investigation continues as part of broader efforts to protect consumer rights and encourage repairability.&amp;lt;ref&amp;gt;{{Cite web |date=15 May 2023 |title=Plainte contre Apple: le Procureur de la République ouvre l’enquête |trans-title=Complaint against Apple: the Public Prosecutor opens the investigation |url=https://www.halteobsolescence.org/plainte-contre-apple-le-procureur-de-la-republique-ouvre-lenquete/ |language=fr}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Legal actions against independent repair shops further solidify its control, making it difficult for users to extend the lifespan of their devices without relying on Apple’s costly repair services.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:Apple IPhones]]&lt;br /&gt;
[[Category:Incidents]]&lt;br /&gt;
[[Category:Lawsuits]]&lt;br /&gt;
[[Category:Planned obsolescence]]&lt;/div&gt;</summary>
		<author><name>ClippyIsAnArchUser</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Chromium&amp;diff=20192</id>
		<title>Chromium</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Chromium&amp;diff=20192"/>
		<updated>2025-08-16T20:18:02Z</updated>

		<summary type="html">&lt;p&gt;ClippyIsAnArchUser: 1. Removed the old introduction paragraph due to a misunderstanding. 2. Made the &amp;#039;Background&amp;#039; the new initiating summary paragraph. 3. Made the paragraph under Controversies more concise.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ToneWarning}}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Chromium&#039;&#039;&#039; is a [[Free and open-source software|free and open-source]] [[:Category:Web browsers|web browser]] developed by and primarily maintained by [[Google]].&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Google |date= |title=Chromium |url=https://www.chromium.org/Home/ |access-date=2025-08-12}}&amp;lt;/ref&amp;gt; Its code-base serves as the foundation for several major web browsers, including [[Google Chrome]],&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; [[Microsoft Edge]],&amp;lt;ref&amp;gt;{{Cite web |date=2019-05-06 |title=10 cool things to check out at Microsoft Build 2019 |url=https://blogs.microsoft.com/blog/2019/05/06/10-cool-things-to-check-out-at-microsoft-build-2019/ |url-status=live |access-date=2025-08-14 |website=blogs.microsoft.com}}&amp;lt;/ref&amp;gt; [[Opera]]/[[Opera GX]],&amp;lt;ref&amp;gt;{{Cite web |date=2013-08-27 |title=Today, Opera 15 has been updated to Opera 16 |url=https://blogs.opera.com/news/2013/08/today-opera-15-has-been-updated-to-opera-16/ |url-status=live |access-date=2025-08-14 |website=blogs.opera.com}}&amp;lt;/ref&amp;gt; [[Brave browser|Brave]],&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-14 |title=Brave - Homepage |url=https://brave.com/ |url-status=live |access-date=2025-08-14 |website=brave.com}}&amp;lt;/ref&amp;gt; and others.&lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
Chromium&#039;s code is published under the 3-clause BSD license &amp;lt;ref&amp;gt;{{Cite web |last=Google |title=LICENSE |url=https://chromium.googlesource.com/chromium/src/+/master/LICENSE |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
&lt;br /&gt;
===Manifest V3===&lt;br /&gt;
Manifest V3 is an update to the manifest structure used by browser-extensions across the majority of the  browser market; it is presented as an upgrade to security, privacy and performance.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=David |title=Resuming the transition to Manifest V3 |url=https://developer.chrome.com/blog/resuming-the-transition-to-mv3 |url-status=live |access-date=24 Mar 2025 |website=Chrome for developers}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=12 Sep 2024 |title=Overview and timelines for migrating to Manifest V3 |url=https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/manifest-v3 |url-status=live |access-date=24 Mar 2025 |website=[[Microsoft]]}}&amp;lt;/ref&amp;gt; Manifest V3&#039;s changes restrict the access browser-extensions can have, presenting a security benefit by not allowing them to load remote resources on the fly or deeply alter rendered content, by doing so the effectiveness of the browser market&#039;s most effective ad-blockers is diminished.&amp;lt;ref&amp;gt;{{Cite web |last=Siddiqui |first=Aamir |date=17 Nov 2023 |title=Google&#039;s Manifest V3 changes will soon disable uBlock Origin on Chrome |url=https://www.androidauthority.com/google-chrome-manifest-v3-changes-3386506/ |url-status=live |access-date=24 Mar 2025 |website=Android Authority}}&amp;lt;/ref&amp;gt; Workarounds and updated versions of Manifest V3 have been made but are less effective since, for example, blocked domains cannot be updated as conveniently.&amp;lt;ref&amp;gt;{{Cite web |last=Buria |first=Taras |date=3 Aug 2024 |title=uBlock Origin developer recommends switching to uBlock Lite as Chrome flags the extension |url=https://www.neowin.net/news/ublock-origin-developer-recommends-switching-to-ublock-lite-as-chrome-flags-the-extension/ |url-status=live |access-date=24 Mar 2025 |website=Neowin}}&amp;lt;/ref&amp;gt; This manifest change is backed by leading Chromium browsers, making it difficult for other browsers to match previous ad-blocking abilities without committing to sustaining Manifest V2 (such as Firefox which also uses chromium-sourced manifests&amp;lt;ref&amp;gt;{{Cite web |last=Sullivan |first=Edward |date=13 Mar 2024 |title=Manifest V3 &amp;amp; Manifest V2 (March 2024 update) |url=https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/ |url-status=live |access-date=24 Mar 2025 |website=[[Mozilla]]}}&amp;lt;/ref&amp;gt;) or sustaining their own ad-blocking solutions&amp;lt;ref&amp;gt;{{Cite web |date=27 Jun 2024 |title=What Manifest V3 means for Brave Shields and the use of extensions in the Brave browser |url=https://brave.com/blog/brave-shields-manifest-v3/ |url-status=live |access-date=24 Mar 2025 |website=[[Brave]]}}&amp;lt;/ref&amp;gt; of varied effectiveness.&amp;lt;ref&amp;gt;{{Cite web |date=17 Jun 2024 |title=Manifest v3 update: Vivaldi is future-proofed with its built-in functionality |url=https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ |url-status=live |access-date=24 Mar 2025 |website=[[Vivaldi]]}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Citations support controversies of Google, Google Chrome, and other third-party companies/products. I suggest this be a part of those articles, and not Chromium.  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=References= &lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>ClippyIsAnArchUser</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Chromium&amp;diff=20173</id>
		<title>Chromium</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Chromium&amp;diff=20173"/>
		<updated>2025-08-16T19:57:00Z</updated>

		<summary type="html">&lt;p&gt;ClippyIsAnArchUser: 1. Changed the tone and summarized the initial paragraph. 2. Added a source/link.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{ToneWarning}}&lt;br /&gt;
&lt;br /&gt;
Google&#039;s update to it&#039;s browser-extension software - Manifest - was falsely advertised as being more secure, private, and performant while restricting features of privacy and performance focused browser-extensions - driving them more revenue.&amp;lt;ref&amp;gt;{{Cite web |last=Barnett |first=Daly |date=2021-12-09 |title=Chrome Users Beware: Manifest V3 is Deceitful and Threatening |url=https://www.eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening |website=eff.org}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Background==&lt;br /&gt;
&#039;&#039;&#039;Chromium&#039;&#039;&#039; is a [[Free and open-source software|free and open-source]] [[:Category:Web browsers|web browser]] developed by and primarily maintained by [[Google]].&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Google |date= |title=Chromium |url=https://www.chromium.org/Home/ |access-date=2025-08-12}}&amp;lt;/ref&amp;gt; Its code-base serves as the foundation for several major web browsers, including [[Google Chrome]],&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; [[Microsoft Edge]],&amp;lt;ref&amp;gt;{{Cite web |date=2019-05-06 |title=10 cool things to check out at Microsoft Build 2019 |url=https://blogs.microsoft.com/blog/2019/05/06/10-cool-things-to-check-out-at-microsoft-build-2019/ |url-status=live |access-date=2025-08-14 |website=blogs.microsoft.com}}&amp;lt;/ref&amp;gt; [[Opera]]/[[Opera GX]],&amp;lt;ref&amp;gt;{{Cite web |date=2013-08-27 |title=Today, Opera 15 has been updated to Opera 16 |url=https://blogs.opera.com/news/2013/08/today-opera-15-has-been-updated-to-opera-16/ |url-status=live |access-date=2025-08-14 |website=blogs.opera.com}}&amp;lt;/ref&amp;gt; [[Brave browser|Brave]],&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-14 |title=Brave - Homepage |url=https://brave.com/ |url-status=live |access-date=2025-08-14 |website=brave.com}}&amp;lt;/ref&amp;gt; and others.  &lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
Chromium&#039;s code is published under the 3-clause BSD license &amp;lt;ref&amp;gt;{{Cite web |last=Google |title=LICENSE |url=https://chromium.googlesource.com/chromium/src/+/master/LICENSE |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
&lt;br /&gt;
===Manifest V3===&lt;br /&gt;
Manifest V3 is an update to the manifest structure used by extensions across most of the browser market, presented as an upgrade to security, privacy and performance.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=David |title=Resuming the transition to Manifest V3 |url=https://developer.chrome.com/blog/resuming-the-transition-to-mv3 |url-status=live |access-date=24 Mar 2025 |website=Chrome for developers}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=12 Sep 2024 |title=Overview and timelines for migrating to Manifest V3 |url=https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/manifest-v3 |url-status=live |access-date=24 Mar 2025 |website=[[Microsoft]]}}&amp;lt;/ref&amp;gt; Manifest V3&#039;s changes restrict the access extensions can have, presenting a security benefit by not allowing them to load remote resources on the fly or alter rendered content as deeply, by doing so the effectiveness of the browser market&#039;s most effective ad-blockers is diminished.&amp;lt;ref&amp;gt;{{Cite web |last=Siddiqui |first=Aamir |date=17 Nov 2023 |title=Google&#039;s Manifest V3 changes will soon disable uBlock Origin on Chrome |url=https://www.androidauthority.com/google-chrome-manifest-v3-changes-3386506/ |url-status=live |access-date=24 Mar 2025 |website=Android Authority}}&amp;lt;/ref&amp;gt; Workarounds and updated versions have been made but are less effective since, for example, blocked domains cannot be updated as conveniently.&amp;lt;ref&amp;gt;{{Cite web |last=Buria |first=Taras |date=3 Aug 2024 |title=uBlock Origin developer recommends switching to uBlock Lite as Chrome flags the extension |url=https://www.neowin.net/news/ublock-origin-developer-recommends-switching-to-ublock-lite-as-chrome-flags-the-extension/ |url-status=live |access-date=24 Mar 2025 |website=Neowin}}&amp;lt;/ref&amp;gt; This manifest change is backed by leading Chromium browsers, making it difficult for other browsers to match previous ad-blocking abilities without committing to sustaining Manifest V2 (such as Firefox which also uses chromium-sourced manifests&amp;lt;ref&amp;gt;{{Cite web |last=Sullivan |first=Edward |date=13 Mar 2024 |title=Manifest V3 &amp;amp; Manifest V2 (March 2024 update) |url=https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/ |url-status=live |access-date=24 Mar 2025 |website=[[Mozilla]]}}&amp;lt;/ref&amp;gt;) or sustaining their own ad-blocking solutions&amp;lt;ref&amp;gt;{{Cite web |date=27 Jun 2024 |title=What Manifest V3 means for Brave Shields and the use of extensions in the Brave browser |url=https://brave.com/blog/brave-shields-manifest-v3/ |url-status=live |access-date=24 Mar 2025 |website=[[Brave]]}}&amp;lt;/ref&amp;gt; of varied effectiveness.&amp;lt;ref&amp;gt;{{Cite web |date=17 Jun 2024 |title=Manifest v3 update: Vivaldi is future-proofed with its built-in functionality |url=https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ |url-status=live |access-date=24 Mar 2025 |website=[[Vivaldi]]}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Citations support controversies of Google, Google Chrome, and other third-party companies/products. I suggest this be a part of those articles, and not Chromium.  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=References= &lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>ClippyIsAnArchUser</name></author>
	</entry>
	<entry>
		<id>https://consumerrights.wiki/index.php?title=Chromium&amp;diff=20127</id>
		<title>Chromium</title>
		<link rel="alternate" type="text/html" href="https://consumerrights.wiki/index.php?title=Chromium&amp;diff=20127"/>
		<updated>2025-08-16T19:16:43Z</updated>

		<summary type="html">&lt;p&gt;ClippyIsAnArchUser: 1. Hyphenated ad-block for readability 2. Added a &amp;#039;Background&amp;#039; heading above the Chromium paragraph. 3. Wrote a summary paragraph at the top.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Google&#039;s update to the browser-extension engine - Manifest - is falsely advertised to the consumers of Chromium as being more secure, private, and performant while in reality it restricts privacy and performance focused browser-extensions&#039; access to the necessary features they need to operate properly. This actually makes the platform less of all of those things - Google benefits by causing ad-blocking browser-extensions to malfunction, earning them more revenue.&lt;br /&gt;
&lt;br /&gt;
== Background ==&lt;br /&gt;
&#039;&#039;&#039;Chromium&#039;&#039;&#039; is a [[Free and open-source software|free and open-source]] [[:Category:Web browsers|web browser]] developed by and primarily maintained by [[Google]].&amp;lt;ref name=&amp;quot;:0&amp;quot;&amp;gt;{{Cite web |last=Google |date= |title=Chromium |url=https://www.chromium.org/Home/ |access-date=2025-08-12}}&amp;lt;/ref&amp;gt; Its code-base serves as the foundation for several major web browsers, including [[Google Chrome]],&amp;lt;ref name=&amp;quot;:0&amp;quot; /&amp;gt; [[Microsoft Edge]],&amp;lt;ref&amp;gt;{{Cite web |date=2019-05-06 |title=10 cool things to check out at Microsoft Build 2019 |url=https://blogs.microsoft.com/blog/2019/05/06/10-cool-things-to-check-out-at-microsoft-build-2019/ |url-status=live |access-date=2025-08-14 |website=blogs.microsoft.com}}&amp;lt;/ref&amp;gt; [[Opera]]/[[Opera GX]],&amp;lt;ref&amp;gt;{{Cite web |date=2013-08-27 |title=Today, Opera 15 has been updated to Opera 16 |url=https://blogs.opera.com/news/2013/08/today-opera-15-has-been-updated-to-opera-16/ |url-status=live |access-date=2025-08-14 |website=blogs.opera.com}}&amp;lt;/ref&amp;gt; [[Brave browser|Brave]],&amp;lt;ref&amp;gt;{{Cite web |date=2025-08-14 |title=Brave - Homepage |url=https://brave.com/ |url-status=live |access-date=2025-08-14 |website=brave.com}}&amp;lt;/ref&amp;gt; and others.  &lt;br /&gt;
&lt;br /&gt;
==Licensing==&lt;br /&gt;
Chromium&#039;s code is published under the 3-clause BSD license &amp;lt;ref&amp;gt;{{Cite web |last=Google |title=LICENSE |url=https://chromium.googlesource.com/chromium/src/+/master/LICENSE |access-date=2025-08-12}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Controversies==&lt;br /&gt;
&lt;br /&gt;
===Manifest V3===&lt;br /&gt;
Manifest V3 is an update to the manifest structure used by extensions across most of the browser market, presented as an upgrade to security, privacy and performance.&amp;lt;ref&amp;gt;{{Cite web |last=Li |first=David |title=Resuming the transition to Manifest V3 |url=https://developer.chrome.com/blog/resuming-the-transition-to-mv3 |url-status=live |access-date=24 Mar 2025 |website=Chrome for developers}}&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;{{Cite web |date=12 Sep 2024 |title=Overview and timelines for migrating to Manifest V3 |url=https://learn.microsoft.com/en-us/microsoft-edge/extensions-chromium/developer-guide/manifest-v3 |url-status=live |access-date=24 Mar 2025 |website=[[Microsoft]]}}&amp;lt;/ref&amp;gt; Manifest V3&#039;s changes restrict the access extensions can have, presenting a security benefit by not allowing them to load remote resources on the fly or alter rendered content as deeply, by doing so the effectiveness of the browser market&#039;s most effective ad-blockers is diminished.&amp;lt;ref&amp;gt;{{Cite web |last=Siddiqui |first=Aamir |date=17 Nov 2023 |title=Google&#039;s Manifest V3 changes will soon disable uBlock Origin on Chrome |url=https://www.androidauthority.com/google-chrome-manifest-v3-changes-3386506/ |url-status=live |access-date=24 Mar 2025 |website=Android Authority}}&amp;lt;/ref&amp;gt; Workarounds and updated versions have been made but are less effective since, for example, blocked domains cannot be updated as conveniently.&amp;lt;ref&amp;gt;{{Cite web |last=Buria |first=Taras |date=3 Aug 2024 |title=uBlock Origin developer recommends switching to uBlock Lite as Chrome flags the extension |url=https://www.neowin.net/news/ublock-origin-developer-recommends-switching-to-ublock-lite-as-chrome-flags-the-extension/ |url-status=live |access-date=24 Mar 2025 |website=Neowin}}&amp;lt;/ref&amp;gt; This manifest change is backed by leading Chromium browsers, making it difficult for other browsers to match previous ad-blocking abilities without committing to sustaining Manifest V2 (such as Firefox which also uses chromium-sourced manifests&amp;lt;ref&amp;gt;{{Cite web |last=Sullivan |first=Edward |date=13 Mar 2024 |title=Manifest V3 &amp;amp; Manifest V2 (March 2024 update) |url=https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/ |url-status=live |access-date=24 Mar 2025 |website=[[Mozilla]]}}&amp;lt;/ref&amp;gt;) or sustaining their own ad-blocking solutions&amp;lt;ref&amp;gt;{{Cite web |date=27 Jun 2024 |title=What Manifest V3 means for Brave Shields and the use of extensions in the Brave browser |url=https://brave.com/blog/brave-shields-manifest-v3/ |url-status=live |access-date=24 Mar 2025 |website=[[Brave]]}}&amp;lt;/ref&amp;gt; of varied effectiveness.&amp;lt;ref&amp;gt;{{Cite web |date=17 Jun 2024 |title=Manifest v3 update: Vivaldi is future-proofed with its built-in functionality |url=https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ |url-status=live |access-date=24 Mar 2025 |website=[[Vivaldi]]}}&amp;lt;/ref&amp;gt;&amp;lt;!-- Citations support controversies of Google, Google Chrome, and other third-party companies/products. I suggest this be a part of those articles, and not Chromium.  --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=References= &lt;br /&gt;
&amp;lt;references /&amp;gt;&lt;br /&gt;
[[Category:{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>ClippyIsAnArchUser</name></author>
	</entry>
</feed>