4 ms·

Your AI should not be in a position to submit a resignation email or send a text to your partner asking for a divorce.

stronglikedan 7mo ago
As long as the email or text includes the disclaimer "generated with the assistance of artificial intelligence" then you should be fine.
- irishcoffee 7mo ago
  You forgot the /s... at least I hope you did.
- ASalazarMX 7mo ago
  It is a charming solution that addresses the optics with great efficiency while leaving the rot entirely undisturbed. By all means, let us proceed if the goal is to feel busy. But when the inevitable occurs, please ensure you have a second, more serious suggestion ready. Disclaimer: generated with the assistance of artificial intelligence
  - 7777777phil 7mo ago
    The auth logic was literally inverted. Blocking people it should allow, allowing people it should block. Probably any human reviewer would catch that in seconds, but AI code generation optimizes for code that runs, not code that's correct in domain-specific ways. I wrote about this pattern recently, AI converges to plausible output but misses the reasoning that requires actual expertise: https://philippdubach.com/posts/the-impossible-backhand/ https://philippdubach.com/posts/the-impossible-backhand/
- bdangubic 7mo ago
  but if that disclaimer means that you have to verify whether or not the "sender" agrees with the content that defeats its purpose, no? if we are all going to be like "did you mean to send this text/email...?"
- ljm 7mo ago
  Hi $wife, You're absolutely right. Let's divorce. I've emailed every lawyer in the state. -- Sent from my OpenClaw
jzkdroid2 7mo ago
I tested openclaw for a few days. The way I got around this was creating openclaw it's own gmail. Any email sent would be from that email. I gave that email access to a shared calendar so it could add events to mine. It gets to act as a second email. Edit: the costs were through the roof at the time so I discontinued use rather than using some hacky workaround. I ran it in a docker container on an undraid server with nothing else running on the server. I also tested it in ubuntu server.

As long as the email or text includes the disclaimer "generated with the assistance of artificial intelligence" then you should be fine.

irishcoffee 7mo ago
You forgot the /s... at least I hope you did.
ASalazarMX 7mo ago
It is a charming solution that addresses the optics with great efficiency while leaving the rot entirely undisturbed. By all means, let us proceed if the goal is to feel busy. But when the inevitable occurs, please ensure you have a second, more serious suggestion ready. Disclaimer: generated with the assistance of artificial intelligence
- 7777777phil 7mo ago
  The auth logic was literally inverted. Blocking people it should allow, allowing people it should block. Probably any human reviewer would catch that in seconds, but AI code generation optimizes for code that runs, not code that's correct in domain-specific ways. I wrote about this pattern recently, AI converges to plausible output but misses the reasoning that requires actual expertise: https://philippdubach.com/posts/the-impossible-backhand/ https://philippdubach.com/posts/the-impossible-backhand/
bdangubic 7mo ago
but if that disclaimer means that you have to verify whether or not the "sender" agrees with the content that defeats its purpose, no? if we are all going to be like "did you mean to send this text/email...?"
ljm 7mo ago
Hi $wife, You're absolutely right. Let's divorce. I've emailed every lawyer in the state. -- Sent from my OpenClaw

jzkdroid2 7mo ago

I tested openclaw for a few days. The way I got around this was creating openclaw it's own gmail. Any email sent would be from that email. I gave that email access to a shared calendar so it could add events to mine. It gets to act as a second email. Edit: the costs were through the roof at the time so I discontinued use rather than using some hacky workaround. I ran it in a docker container on an undraid server with nothing else running on the server. I also tested it in ubuntu server.