@mcc How hard could it be to create Gecko, Chromium, and WebKit extensions to send, and Apache and Nginx modules to require, HTTP headers containing some lawyer-crafted language binding the entities causing request initiation to not being part of AI companies and not disclosing response contents to AI companies?
#Lawfedi, can you craft a statement that turns it into perjury, or fraud, or a CFAA (and non-US counterpart law) violation for an AI crawler or a person collecting data for an AI company to send a request with that statement, but not for anyone else? How about civil causes of action too, such as breach contract?
Perhaps, for brevity, the HTTP header would have to refer to terms at a defined .well-known/legal/declaration-not-ai.txt
location and a hash of that file's contents? And that file could have standard terms (like the GPL or the Creative Commons licenses, but for converting a false declaration into as many crimes and civil offences as possible), so the same boilerplate legal declaration can be replicated across services and domains?
Just a whimsical idea.