Hacker News new | ask | show | jobs
by lcall 1988 days ago
Yes, like we do with Creative Commons or FLOSS licenses, so you don't have any reason to read them more than once or occasionally. Whether somebody. Maybe something like the uniform commercial code, in the USA. That would be a nice contribution by some organization.

Even if only some sections are standardized and others not, that would be a comparative win. Maybe an "exceptions/additions" part.

Edit: also, there are some few sites I recall that summarized terms and/or pointed out problematic parts, to help someone who cared but didn't want to read them all. I might be able to hunt up (a) link(s) if desired.

What I do currently is read them once, mentally note the date displayed, save them, and when they change, use a short script to make it easy to see differences (uses fmt to make lines to shorter first, and get sometimes fewer differences that way). Sometimes I have pushed back and contacted the organization, or just not used them. I wrote a bunch of complaints about this kind of thing, at my site -- it takes us further down the slippery slope of saying things we don't mean to each other, habitually, which is sadly dishonest IMO.

1 comments

For reference in case useful, though I haven't even read their site carefully: https://stonecutters.law/

They say "Stonecutters publishes legal forms and clauses for other legal craftsmen to incorporate by reference."