Right to repair: Difference between revisions

Line 15:

In the case of parts that aren't used in other devices, this can cause repair prices to shoot up, since there isn't an incentive for repair shops to have this part readily available. Using phones as an example, Phone A and Phone B are both from the same manufacturer, and are physically indistinguishable. However, on the inside Phone A uses a completely different screen connection than Phone B, and Phone B has a completely different battery shape than Phone A. The parts are no longer interchangeable between the phones, and more parts need to be stocked as a result. As well, the repair shop takes a risk on keeping a stock of parts that may or may not sell because they are exclusive to a certain phone. This can also lead to people not wanting to have their phone repaired, since they will be without their phone for a week or two while the shop waits for a part to ship.

==== Software ====

Some ways that companies can and (some) have been making software worse for consumers is among the following:

* Requiring a subscription for software which doesn't need constant updates or cloud content to function

* Introducing proprietary protocols or file types without any innovation or real addition of features (for instance, if a company introduces a word processor which doesn't have any more features than a standard .odt or .docx file, then there likely isn't a real reason for it to use its own proprietary format).

* Not providing troubleshooting or issue workaround information on reasonable terms (for instance, requiring an absurd amount of money and/or technical certificates for said information is beyond what would be reasonable)

* Making software needlessly dependent on cloud infrastructure

* Regressing features and usability for unnecessary reasons

These can interfere with daily lives and the ability of professionals to rectify any software issues. For instance, a company charging an absurd amount of money for information on the location of one checkbox in one of their settings dialog can lead to a professional spending an extra hour or two to locate the dialog and the specific checkbox.

Proprietary filetypes and protocols can make hardware useless if the company who made it closes their business without disclosing the software, protocol, or filetype to the public or surviving entity before doing so.

[[Category:Common Term]]

@@ Line 15: / Line 15: @@
 In the case of parts that aren't used in other devices, this can cause repair prices to shoot up, since there isn't an incentive for repair shops to have this part readily available. Using phones as an example, Phone A and Phone B are both from the same manufacturer, and are physically indistinguishable. However, on the inside Phone A uses a completely different screen connection than Phone B, and Phone B has a completely different battery shape than Phone A. The parts are no longer interchangeable between the phones, and more parts need to be stocked as a result. As well, the repair shop takes a risk on keeping a stock of parts that may or may not sell because they are exclusive to a certain phone. This can also lead to people not wanting to have their phone repaired, since they will be without their phone for a week or two while the shop waits for a part to ship.
+==== Software ====
+Some ways that companies can and (some) have been making software worse for consumers is among the following:
+* Requiring a subscription for software which doesn't need constant updates or cloud content to function
+* Introducing proprietary protocols or file types without any innovation or real addition of features (for instance, if a company introduces a word processor which doesn't have any more features than a standard .odt or .docx file, then there likely isn't a real reason for it to use its own proprietary format).
+* Not providing troubleshooting or issue workaround information on reasonable terms (for instance, requiring an absurd amount of money and/or technical certificates for said information is beyond what would be reasonable)
+* Making software needlessly dependent on cloud infrastructure
+* Regressing features and usability for unnecessary reasons
+These can interfere with daily lives and the ability of professionals to rectify any software issues. For instance, a company charging an absurd amount of money for information on the location of one checkbox in one of their settings dialog can lead to a professional spending an extra hour or two to locate the dialog and the specific checkbox.
+Proprietary filetypes and protocols can make hardware useless if the company who made it closes their business without disclosing the software, protocol, or filetype to the public or surviving entity before doing so.
 [[Category:Common Term]]