Hacker News Reader

(IANAL) You can normally safely ignore such things.

My nightmare scenario is that I build my own crucial database of information partially derived from a search API... and then later get into legal trouble which forces me to delete that data, which is now intermingled with other information I've collected.

So we don't have just data now, but data-obtained-by-particular-process? If you have a database, should it matter how it was gathered?

Yes - it's important to me that I understand the source of the data I've collected and if that source results in restrictions on what I can do with that data.

Especially when I'm building databases that I want other organizations to be able to use.

Fun fact: many geocoding APIs have restrictions on what you can do with the data you get back from that geocoder - including how long you can store it and whether you are allowed to re-syndicate to other people. That's one of the reasons I like OpenCage: https://opencagedata.com/guides/how-to-compare-and-test-geoc...

I agree with you in spirit, but that’s not an answer you can apply when there’s someone else’s money at stake.

Reply on news.ycombinator.com