| ▲ | infogulch 3 hours ago | ||||||||||||||||||||||
It seemed like this part gives you the exception you wanted: > provided that you may display Output to your authorized end users within your own application so long as such Output is integrated into your application's functionality, is incident to the end user’s real-time query ... but it continues: > ... and is not independently accessible, extractable, or downloadable by end users or third parties How can you prevent end users from extracting it if its visible? Why even have the exception if you just throw it out with an impossible to meet restriction like this? | |||||||||||||||||||||||
| ▲ | Loquebantur an hour ago | parent | next [-] | ||||||||||||||||||||||
So they crawled the web, stole the information to populate their own database and then pretend it was "illegal" for others to steal it back? The weird attitude in the Internet Tech company scene is akin to Gold Rush scenarios. Who are the native people? | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | foota 2 hours ago | parent | prev [-] | ||||||||||||||||||||||
Not to mention: "retain, cache, or store Output beyond what is reasonably necessary to display such Output to your authorized end users in the ordinary and real-time course of use" which would seem to preclude storing it in a long lived session. | |||||||||||||||||||||||
| |||||||||||||||||||||||