Editing Software locks (section)

==Noteworthy bad practice examples==

===Anti Interoperability===
 Also see: [[wikipedia:Proprietary_protoco|Proprietary protocols]], [[Anti Interoperability]], [[Hardware Anti Interoperability]]<ref>[https://en.wikipedia.org/wiki/Proprietary_hardware? https://en.wikipedia.org/wiki/Proprietary_hardware?]</ref>
wip  stub example you can't use our competitors Bluetooth headset with our XYZ operating system because we invented a our own new proprietary XYZ Bluetooth audio codec and that product doesn't support it. 

real example apple mfi certifications on charging and data transfer accessories  

apple's history of anti-Interoperability

===Account-required products===

=====Mobile phones=====
[https://pirg.org/articles/refurbishers-repairers-and-recyclers-call-on-the-fcc-to-stop-phone-software-locks/ ref] Small preamble focused on how mobile phones require an account in order to be used, reference Google Pixels and specific Android devices requiring a Google account, and iPhones needing an Apple account.

=====in appliances=====
hvac app activation of furnace control boards (also an example of [[Forced app download]]  (editors note hard to find credible ref this is a thing with ruud furnace control boards) ) 

====Binding hardware features to non-transferable user accounts / activation & licensing locks<!-- This needs a much shorter name -->====
-wip

===Server connectivity reliance===
 Also see: [[Subscription service]], [[Digital rights management]]
-wip