zlacker

[parent] [thread] 4 comments
1. smolde+(OP)[view] [source] 2024-01-18 18:35:21
This is like suing somebody for using chopsticks to eat a meal you sold them. Where is the financial damage? Do they sell their own automation products? Even if that's the case, and they're fork-sellers on the side in my analogy, there's absolutely no good to come from suppressing these plugins.
replies(1): >>agilob+j
2. agilob+j[view] [source] 2024-01-18 18:36:42
>>smolde+(OP)
>Where is the financial damage?

They offered API that they don't want people to use. Maintaining APIs and uptime costs, but they only wanted their API to be used by their apps that collect data about you.

replies(1): >>hunter+Ld
◧◩
3. hunter+Ld[view] [source] [discussion] 2024-01-18 19:39:47
>>agilob+j
> They offered API that they don't want people to use.

I wonder how this would play out if instead of serving responses for nonhuman consumption (i.e., an API), it was serving responses for human consumption (i.e, HTML documents). In that scenario, if a subset of requests were of a high-frequency nonhuman nature (i.e., polling and scraping), would a court find it equally abusive or materially different?

replies(1): >>agilob+Oh
◧◩◪
4. agilob+Oh[view] [source] [discussion] 2024-01-18 19:58:30
>>hunter+Ld
HTLM documents evolve much more frequently and there were dozens of HA addons that simply gave up updating their regexes extracting certain information from HTML and emails.
replies(1): >>quotem+xv3
◧◩◪◨
5. quotem+xv3[view] [source] [discussion] 2024-01-19 18:30:54
>>agilob+Oh
Ah, but now we have LLMs that can understand human interfaces without manual tweaking!
[go to top]