https://tldrlegal.com/api/license
is available w/ default REST pagination/query params for content on TLDRLegal
291 karma · joined July 4, 2012
https://tldrlegal.com/api/license
is available w/ default REST pagination/query params for content on TLDRLegal
1. It's hard work summarizing licenses. I'd like to give people a chance to get credited for their contributions to the community and be social about licenses.
2. A little harder to make bold/troll edits if all of them are moderated by both license submitters and admins on the site. Any information around legal things are very sensitive and impactful - although TLDR doesn't claim to be a law firm or provide legal advice, we still try our best to have good quality content.
3. Future ability to build tools for the community on this dataset, where data is attached to user accounts.
4. Easier way to understand how many people are participating and announce new, important features.
Finally, TLDR doesn't encourage you to ignore the license. It provides you an out before you delve in deep.
1. You're totally right about ToS. Tldrlegal was just code and OSS licenses for a while -- I just added terms of service and the apple tos today. They're in the autocomplete to just feature both types but you're right -- it's irresponsible to suggest that before it's ready.
2. The back button issue is just a redirect one from the js routing on that page. The reason is because it defaults to the first tab link, which is kept as an anchor for js-disabled loaders.
Thanks for the notes!
It would also be great if all of your images were synced to the latis cloud, so you can straight D&D a url into a textbox by dragging an item from the stack.