@rysiek i find the statement of principles quite lacking. Suppose you buy a thermostat that is programmed to only function when getting instructions from honeywell's server. Honeywell decides to pull the plug on the server, & all thermostats become useless. None of the 5 articles cover that.

@rysiek If TomTom stops selling maps or Roku or Wii stops their online svc, you're fucked & yet article 1-5 miss this. A that leaves someone w/a proprietary box doesn't go far enough if it only gives legal rights & not tech means. I don't just want TomTom to allow fiddling w/their old box- I want TomTom to release the SDK & src code when it decides it's EOL.

@resist1984


DA here:

Wait so you buy a Jeep and when they stop making Jeep’s they have to teach you how to make and repair one?! Like, the one time purchase of the item isn’t enough, it has to last forever?

@rysiek

@seven @rysiek you seem to be conflating training with code disclosure. If Jeep decides to stop maintaining their software, they no longer need the /all rights reserved/ incentive to create the creative works. Copyright was effectively too long, and should be cut short.

Follow

@rysiek @seven Mandated training would be overly imposing, but I do think the system should build-in an incentive for product makers to publish service manuals at product EOL time, perhaps in the form of carbon credits. The more a company does to facilitate longevity of their products, the lower their effective carbon footprint is.

Sign in to participate in the conversation
Mastodon 🔐 privacytools.io

Fast, secure and up-to-date instance. PrivacyTools provides knowledge and tools to protect your privacy against global mass surveillance.

Website: privacytools.io
Matrix Chat: chat.privacytools.io
Support us on OpenCollective, many contributions are tax deductible!