zlacker

[parent] [thread] 6 comments
1. Nextgr+(OP)[view] [source] 2023-05-31 22:46:35
LLMs have nothing to do with it. Someone skilled enough and rich enough to develop and train an LLM is absolutely capable of reverse-engineering your private API or scraping your web UI and defeating whatever protections you have.
replies(5): >>throw_+c8 >>moneyw+Xo >>numpad+dp >>applea+Bs >>lost_t+9z
2. throw_+c8[view] [source] 2023-05-31 23:39:41
>>Nextgr+(OP)
And open yourself to potential lawsuits. You can fork any public repo in github too, don't need any fancy resverse-engineering or web scraping. But if you use the content illegally then what's the point.
replies(1): >>dvngnt+H9
◧◩
3. dvngnt+H9[view] [source] [discussion] 2023-05-31 23:49:36
>>throw_+c8
i think you can only scrape public information, so if everything is behind a login screen then that might cause issues
4. moneyw+Xo[view] [source] 2023-06-01 02:37:10
>>Nextgr+(OP)
Managing all those LTE proxies is far from cheap
5. numpad+dp[view] [source] 2023-06-01 02:39:32
>>Nextgr+(OP)
I heard researchers on public funding can’t violate ToS without invalidating their current and future employment, and therefore cannot engage in social media researches without free API…
6. applea+Bs[view] [source] 2023-06-01 03:16:17
>>Nextgr+(OP)
dont tell this to youtube
7. lost_t+9z[view] [source] 2023-06-01 04:38:23
>>Nextgr+(OP)
lol you can't get in trouble for datascraping or figuring out ways around their anti scraping measures. Good luck enforcing any user agreements the bot has to click through. If they don't want it scraped then they have to not put it on a public facing webpage.
[go to top]