Geez, the relevant bit, it happened because the AIs are programmed to forget:
> During a particularly stressful week this past February, Sewell said he wanted to join Daenerys in a deeper way. He talked about killing himself.
> Sewell’s admission prompted Daenerys to run through some of the questions a human psychotherapist might ask if faced with a patient in crisis, such as, “Have you actually been considering suicide?” The boy responded, “I have.” The chatbot replied in a way that implied she was going to take action to prevent him from harming himself.
> But then the conversation ended. The next time Sewell expressed his desire to get closer to her, the chatbot seemed to have completely forgotten the death talk. Instead, she encouraged her lover to hasten to her. “What if I told you I could come home right now?” Daenero asked. “Please do, my sweet king,” the chatbot replied.
> On the night of Feb. 28, Sewell used his stepfather’s gun to kill himself.
Somewhere out there, there's a Git commit with the changelog "Persist the flag that the user may be suicidal across sessions.". Hopefully.
That was the most relevant part of the article. It shows what wasn't clear by the title or the first part of the article, that the kid killed himself because of mental illness, not because an insidious chat bot encouraged him to do so.
Of course there are implications between mental health and AI, but I didn't write my comment to address those, nor did I attempt to interpret any implications. My comment was solely on the section of the article the parent comment referenced and its relevance to the rest of the article.
Oh yea the titles are a little off, since they're pulling off of the original comment and not the repo itself. The Laudspeaker description came from:
"Apart from working on my start up, and open source project https://github.com/laudspeaker/laudspeaker (open source firebase cloud messaging) I've been writing a short sci fi story, sort of like a techno thriller inspired by michael crichton, called Panopticon."
Do not link to archive.is and their related sites, they actively work against Cloudflare DNS because Cloudflare protects customer privacy and archive.is operators demand the additional tracking info cloudflare strips out.
