4 ms·
One of the issues is that responsibility for maintaining the integrity of the code is 100% on the seller's side. Like you said, if you used this service, it wou
by shirakawasuna 9y ago
One of the issues is that responsibility for maintaining the integrity of the code is 100% on the seller's side. Like you said, if you used this service, it would become extremely expensive over the long term. Since the purpose is to give clients value in the case that you're unable to continue providing service, why not give them an encrypted version of the code and make the key the failsafe? There still has to be trust, but then the client gets to choose the cost of maintaining that code snapshot.
- ddewit 9y agoYou are right it's exactly the combination of ongoing snapshots and the need to only provide access when there's a verified release event. We try to provide that balance. We also do verification, but that's mainly when there is 'less than optimal' trust between the developer and the licensee.