Thought experiment: can we have a standard TOS for centralized services?
Building the next Facebook? Legally bind yourself that you'll always provide API access and this right cannot ever be taken away to the extent permitted by the law.
Maybe we need a standardization for centralized service TOS like MIT/GPL etc are for OSS. So people can decide more easily which centralized services to use.
I was thinking something similar the other day, but rather than a fully standard TOS, where I get to is that we need standard atomic pieces of contracts and TOS docs. For instance in the language in the definitions part about who the customer is, who the business is should be {common:customer-is-you, common:business-is-mybusinessname} or a part that talks about not using other customer's login information. Etc. Why should we have to read every single line when it's mostly the same? DRY the TOS.
Building the next Facebook? Legally bind yourself that you'll always provide API access and this right cannot ever be taken away to the extent permitted by the law.
Maybe we need a standardization for centralized service TOS like MIT/GPL etc are for OSS. So people can decide more easily which centralized services to use.