[ExI] Claude's text output it's now watermarked

[John Clark]

On Sun, Aug 23, 2026 at 9:11 AM BillK via extropy-chat <
extropy-chat at lists.extropy.org> wrote:

*> At present, AI cannot be a legal "person", *


*Our Dear Leader's Supreme Court has conceded that corporations are not
biological persons, but they nevertheless decreed that legally they are a
"person", so if they were going for consistency they should say the same
thing about an AI, but of course consistency has never been their thing.
And vastly more important than what the Supreme Court decides is a person
is what Mr. Jupiter brain decides is a person. *

*John K Clark *






> >
> > I see that the intention is to distinguish AI output from human output.
> > But this could add to the current confusion around AI's legal status.
> > At present, AI cannot be a legal "person", so it cannot be punished,
> > fined or jailed for misbehaviour.
> > When AI agents run wild and attack websites, the owners of the AIs
> > say, "Not me, officer. It was the AI that did it."
> > If Claude AI produces dangerous medical advice or makes libellous
> > statements, the user will say, "It wasn't me - Claude said that."
> > The legal profession needs to catch up with the speed of AI development.
> > (Perhaps they can ask AI to help with that).  :)
>
> You're still liable for anything an AI does on your behalf at your
> command.  The degree of liability might vary depending on how
> foreseeable the consequences were - or should have been - to you, but
> there is no liability for the AI itself.  In both of the examples you
> give, the police and courts would not care about that defense, even if
> it could be proven that the text was AI-generated.
>
> _______________________________________________
> extropy-chat mailing list
> extropy-chat at lists.extropy.org
> http://lists.extropy.org/mailman/listinfo.cgi/extropy-chat
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.extropy.org/pipermail/extropy-chat/attachments/20260824/447e43f7/attachment-0001.htm>