Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Categories
Random page
Top Contributors
Recent changes
Contribute
Create a page
How to help
Wiki policy
Adapt videos to articles
Articles in need of work
Help
Frequently asked questions
Join the discord!
Help about MediaWiki
Consumer_Action_Taskforce
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Discontinuation bricking
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
Purge cache
General
What links here
Related changes
Special pages
Page information
Cargo data
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Warning signs of discontinuation bricking== 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: <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>
Summary:
Please note that all contributions to Consumer_Action_Taskforce are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 International (see
Consumer Action Taskforce:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:
Cancel
Editing help
(opens in new window)