53 ms·
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
by joshka 6y ago
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.
- joshka 6y agoLooks like someone actually started doing some of this already: is https://stonecutters.law/ https://stonecutters.law/