> If it's auth-gated, it needs to be, well, authenticated.
AFAIK, there isn't an single auth scheme on earth that guarantee human intervention[1]. Anyone can set-up a robot creating new users on a whim using single-use email addresses and even phone numbers. In fact, we know that OpenAI's agent have been doing exactly that when attacking Rubygem. And all AI labs are likely doing it for scrapping social media as well.
Who are you gonna sue then?
[1] the closest thing is Altman iris scanning venture, but without a broad adoption it's remains functionally useless.
By setting that up, you take on the liability for it. The defendant is whoever set it up. No different from "if I roll a car down a hill and it hits something at the bottom, how can you hold the car liable?"
> How can an automated process be a party in the terms of services though?
If it's auth-gated, it needs to be, well, authenticated.
The person who provides that, and the subsequent automated scraping, is the party, and would be the recipient of a civil suit.
> If it's auth-gated, it needs to be, well, authenticated.
AFAIK, there isn't an single auth scheme on earth that guarantee human intervention[1]. Anyone can set-up a robot creating new users on a whim using single-use email addresses and even phone numbers. In fact, we know that OpenAI's agent have been doing exactly that when attacking Rubygem. And all AI labs are likely doing it for scrapping social media as well.
Who are you gonna sue then?
[1] the closest thing is Altman iris scanning venture, but without a broad adoption it's remains functionally useless.
The person who sets up that robot is the person responsible and effectively signing the contract by those actions.
> Who are you gonna sue then?
The person who set up the robot.
By setting that up, you take on the liability for it. The defendant is whoever set it up. No different from "if I roll a car down a hill and it hits something at the bottom, how can you hold the car liable?"
4 replies →