Discontinuation bricking: Difference between revisions

ADRdaniel (talk | contribs)
Examples: big contribs all day every day yeet
Raidarr (talk | contribs)
m still a red link but a proper one at least
 
(4 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{StubNotice}}
{{StubNotice}}


'''Discontinuation bricking''' occurs when a product is "bricked" — no longer functional — because the producer has discontinued it. Discontinuation bricking almost exclusively occurs in products that require a connection to a remote server hosted by the producer. The product may become bricked if the company decides to shut down services or if the company goes out of business entirely, which is a significant harm to consumer rights.  
'''Discontinuation bricking''' occurs when a product is renderered no longer functional ("bricked") because the manufacturer has decided to discontinue it. Discontinuation bricking almost exclusively occurs in products that require a connection to a remote server hosted by the producer. The product may become bricked if the company decides to shut down services or if the company goes out of business entirely, while not allowing the consumer to substiture those services with alternative and/or [[self-hosted]] solutions. End-of-life for a produt does not require the product be bricked.


== Bricking- vs proper EOL ==
{| class="wikitable mw-collapsible" style="margin: auto;
{| class="wikitable mw-collapsible"
|+ End-of-Life compared to bricking
|+
!x
![[EOL]]
!ideal EOL
!Soft BRICK
!'''Discontinuation bricking'''
!
!
!EOL
!Soft brick
!Discontinuation bricking
|-
|-
|hardware boots
|Device boots
|
|yes
|yes
|yes
|yes
|sometimes
|sometimes
|
|-
|-
|basic functionality
|Basic functionality
|
|yes
|yes
|sometimes
|sometimes
|no
|no
|
|-
|-
|software updates
|Software updates
|
|sometimes
|sometimes
|no
|no
|no
|no
|
|}<!-- Please expand chart  -->
|}<!-- Please expand chart  -->


==Warning signs of discontinuation bricking==
Discontinuation bricking is usually an unintended consequence of a remote service shutting down that the product depends on for complete functionality. The risk of discontinuation bricking occurring can be detected beforehand by observing warning signs, such as:
#'''Product requires an internet connection to a remote server:''' if a product requires connection to a remote server for functionality, there is a risk that the company may shut down the server and brick some function, if not all functions of the product. These connections may be necessary because:
##'''Product requires remote authorization:''' product only works if you can receive authorization from an authorization server. If the authorization server shuts down, login will become impossible. An unusual example being the Spotify Car Thing which stopped functioning after Spotify unauthorized the Car Thing from interacting with the Spotify App API.
##'''Product has features dependent on remote sources:''' product may brick if it is unable to access remote information because of server outages.
#'''Product depends on a phone application to work:''' updates to the app may remove support for the discontinued product. An example being the [[Spotify Car Thing]] which stopped functioning after Spotify unauthorized the Car Thing from interacting with the Spotify App API.<ref>[https://www.motortrend.com/news/spotify-car-thing-music-streaming-device-discontinued/ "Spotify's Oddball In-Car Music Device Is Getting Bricked. Turns Out There's an App For That."] - motortrend.com - accessed 2025-01-25</ref><!-- Maybe include a different example here? It feels a bit redundant considering this was the example for the previous point. --><!-- To be fair we may be better of just merging 1 and 2 and expanding upon 1, there's nearly no difference as the product and app go hand-in-hand -->
#'''Product requires physical input on a regular basis:''' as an example, [[HP Inc.]] printer ink has a [[Digital rights management|DRM]] that forces consumers to exclusively use HP ink, and does not allow third-party cartridges. If HP goes out of business or decides to stop producing their ink cartridges, any printer depending upon it will become bricked, '''effectively discontinuing the printer''' even if not explicitly stated.
==How discontinuation bricking impacts consumer rights==
Discontinuation bricking is similar to [[planned obsolescence]] in which it harms the consumer and the environment by making a product they paid for stop functioning, which not only is anti-consumer but also contributes to E-waste.<!-- "e-waste" may be too specific of a term. "waste" refers to all waste while "e-waste" is more specific towards electronics. Consider changing to "waste" in the final draft. -->


===How discontinuation bricking contributes to E-waste===
Discontinuation bricking will inevitably generate waste given that the product is no longer functional, and consumers will be forced to discard the product.


===Loss of ownership===
==Impact to consumer rights==
Discontinuation bricking and the possibility that a product may brick itself in the future due to discontinuation, directly harms the ability for a consumer to own their product, as a consumer does not truly own their product if the product is at risk of being bricked and no longer functional.
Discontinuation bricking, similarly to [[planned obsolescence]], harms the consumer by making a product they paid for stop functioning, resulting to loss of ownership of said product, as functionality is stripped from it.


===Dependence on third-party bypasses===
===Dependence on third-party bypasses===
Line 63: Line 41:
#Customers may learn about the discontinuation and decide to sell the product without providing adequate details, even without any malicious intent.
#Customers may learn about the discontinuation and decide to sell the product without providing adequate details, even without any malicious intent.


===Methods to avoid discontinuation bricking===
==Environmental impact==
Discontinuation bricking will inevitably generate waste given that the product is no longer functional, and consumers will be forced to discard the product.


#'''Avoid internet and smart products:''' if the product has to connect to an external server to work, the product is vulnerable to being bricked.
==Warning signs of discontinuation bricking==
#'''Use [[Open source|open source/schematic]] products:''' open source/schematic products are inherently resistant to discontinuation bricking as the consumer is typically given everything they need to resolve outages themselves.
Discontinuation bricking is usually a consequence of a remote service shutting down that the product depends on for complete functionality. The risk of discontinuation bricking occurring can be assessed beforehand by observing warning signs, such as:
#'''Buy products that contractually guarantee source/schematic release on discontinuation:''' if a company decides to include a legally binding agreement to provide source and schematics, this is usually a good sign that they are willing to accept blame for discontinuation bricking and take action to alleviate it.


<ol>
<li>'''Product requires an internet connection to a remote server:'''</li>if a product requires connection to a remote server for functionality, there is a risk that the company may shut down the server and brick some function, if not all functions of the product. These connections may be necessary because:
<ul>
<li>'''Product requires remote authorization:'''</li> product only works if you can receive authorization from an authorization server. If the authorization server shuts down, login will become impossible. An unusual example being the Spotify Car Thing which stopped functioning after Spotify unauthorized the Car Thing from interacting with the Spotify App API.
<li>'''Product has features dependent on remote sources:'''</li> product may brick if it is unable to access remote information because of server outages.
</ul>
<li>'''Product depends on a phone application to work:'''</li> updates to the app may remove support for the discontinued product. An example being the [[Spotify Car Thing]] which stopped functioning after Spotify unauthorized the Car Thing from interacting with the Spotify App API.<ref>[https://www.motortrend.com/news/spotify-car-thing-music-streaming-device-discontinued/ "Spotify's Oddball In-Car Music Device Is Getting Bricked. Turns Out There's an App For That."] - motortrend.com - accessed 2025-01-25</ref><!-- Maybe include a different example here? It feels a bit redundant considering this was the example for the previous point. --><!-- To be fair we may be better of just merging 1 and 2 and expanding upon 1, there's nearly no difference as the product and app go hand-in-hand -->
<li>'''Product requires physical input on a regular basis:'''</li> as an example, [[HP Inc.]] printer ink has a [[Digital rights management|DRM]] that forces consumers to exclusively use HP ink, and does not allow third-party cartridges. If HP goes out of business or decides to stop producing their ink cartridges, any printer depending upon it will become bricked, effectively discontinuing the printer even if not explicitly stated.</li>
</ol>
== Examples ==
== Examples ==
[[Spotify Car Thing]]
[[Spotify Car Thing]]


[[Sonos|sons]] smart speaker
[[Sonos]]


[[Nest Revolv Hub]]<ref>https://www.eff.org/deeplinks/2016/04/nest-reminds-customers-ownership-isnt-what-it-used-be</ref><ref>https://www.zdnet.com/article/revolv-is-dead-google-killed-it-long-live-innovation/</ref>
[[wikipedia:Orphaned_technology|Orphaned technology]] on wikipedia.org


[https://www.theverge.com/circuitbreaker/2017/11/8/16623076/logitech-harmony-link-discontinued-bricked Logitech Harmony Link hub]<ref>https://support.logi.com/hc/en-us#!?return_to=%2Fhc%2Fen-us%23!%2Fs%2Fquestion%2F0D55A0000745EkC%2Fharmony-link-eos-or-eol</ref>  
[[Logitech Harmony Link hub]]<ref>https://support.logi.com/hc/en-us#!?return_to=%2Fhc%2Fen-us%23!%2Fs%2Fquestion%2F0D55A0000745EkC%2Fharmony-link-eos-or-eol</ref><ref>https://www.theverge.com/circuitbreaker/2017/11/8/16623076/logitech-harmony-link-discontinued-bricked</ref>


[[Astro Amazons security robot,|Astro Amazons security robot.]]<ref>https://www.inc.com/amazon-bricking-its-astro-for-business-robots.html</ref> <ref>https://press.aboutamazon.com/2023/11/introducing-astro-for-business-a-customizable-security-solution-bringing-peace-of-mind-to-owners-of-small-and-medium-sized-businesses</ref> November 15, 2023 -  '''JUL 5, 2024'''
[[Nest Revolv Hub]]<ref>https://www.eff.org/deeplinks/2016/04/nest-reminds-customers-ownership-isnt-what-it-used-be</ref><ref>https://www.zdnet.com/article/revolv-is-dead-google-killed-it-long-live-innovation/</ref>
 
 
 
From Wikipedia : [[wikipedia:Orphaned_technology|Orphaned technology]]
 
"Some examples of orphaned technology include:


* Apple Lisa - 16/32-bit graphical computer
[[Astro Amazons security robot|Astro Amazons security robot.]]<ref>https://www.inc.com/amazon-bricking-its-astro-for-business-robots.html</ref> <ref>https://press.aboutamazon.com/2023/11/introducing-astro-for-business-a-customizable-security-solution-bringing-peace-of-mind-to-owners-of-small-and-medium-sized-businesses</ref>
* Apple Newton PDA (Apple Newton) - tablet computer
* Apple Classic Mac OS - m68k and PowerPC operating system
* Coleco ADAM - 8-bit home computer
* DEC Alpha - 64-bit microprocessor
* Finale (scorewriter) music notation software developed by MakeMusic from 1988 until 2024
* HyperCard - hypermedia
* ICAD (KBE) - knowledge-based engineering
* Javelin Software - modeling and data analysis
* LISP machines - LISP oriented computers
* Mattel Aquarius
* Microsoft Bob - graphical helper
* Mosaic notation program - music notation application by Mark of the Unicorn
* Open Music System - Gibson
* OpenDoc - compound documents (Mac OS, OS/2)
* Poly-1 - parallel networked computer designed in New Zealand for use in education and training
* Prograph - visual programming system
* TI 99/4A - 16-bit home computer
* Windows 9x - x86 operating system"


== Also see ==
== Also see ==