I agree but I think it needs to be slightly more practical. Sometimes a line of business just dries up and it would damage the company to try and keep that service going. It wouldn’t make sense to force a company into bankruptcy to keep one line going that few people use anymore.
Earlier today, though, I was thinking about sunsetting guarantees. Companies can and should decommission things when it makes business sense, but the user generated content it has gathered shouldn’t just disappear, and they shouldn’t be allowed to destroy the user experience of things people have bought.
So I would propose rules like:
If a service is being decomissioned or an entry point to that service being shut down, the content available on that service must be made available as a bulk export. Personal data, such as account data, messages, etc should be made available to users individually, while publicly accessible content should be made available publicly.
If a public service is being taken down completely, source code should be made available publicly.
If the service for a device which was physically purchased by consumers is being taken down, an update must be provided to allow users to use a local or alternative backend service. The source code for the service must be released publicly.
If features are being removed from a service which backed a physically purchased device, an update must be offered which allows users to point to a local or alternative service for either all functionality or, at minimum, the removed functionality. Looking at you, Google, keep removing features…
Yeah, as always, the devil is in the details. For now I think that we need a simple and clear articulation of the main idea. In the exceedingly unlikely event that it ever gets traction, I look forward to hammering out the many nuances.
I agree but I think it needs to be slightly more practical. Sometimes a line of business just dries up and it would damage the company to try and keep that service going. It wouldn’t make sense to force a company into bankruptcy to keep one line going that few people use anymore.
Earlier today, though, I was thinking about sunsetting guarantees. Companies can and should decommission things when it makes business sense, but the user generated content it has gathered shouldn’t just disappear, and they shouldn’t be allowed to destroy the user experience of things people have bought.
So I would propose rules like:
If a service is being decomissioned or an entry point to that service being shut down, the content available on that service must be made available as a bulk export. Personal data, such as account data, messages, etc should be made available to users individually, while publicly accessible content should be made available publicly.
If a public service is being taken down completely, source code should be made available publicly.
If the service for a device which was physically purchased by consumers is being taken down, an update must be provided to allow users to use a local or alternative backend service. The source code for the service must be released publicly.
If features are being removed from a service which backed a physically purchased device, an update must be offered which allows users to point to a local or alternative service for either all functionality or, at minimum, the removed functionality. Looking at you, Google, keep removing features…
Yeah, as always, the devil is in the details. For now I think that we need a simple and clear articulation of the main idea. In the exceedingly unlikely event that it ever gets traction, I look forward to hammering out the many nuances.