On Tuesday, parents of a teen who died by suicide filed the first ever wrongful death lawsuit against OpenAI and its CEO, Sam Altman, alleging that their son received detailed instructions on how to hang himself from the company’s popular chatbot, ChatGPT. The case may well serve as a landmark legal action in the ongoing fight over the risks of artificial intelligence tools — and whether the tech giants behind them can be held liable in cases of user harm.
The 40-page complaint recounts how 16-year-old Adam Raine, a high school student in California, had started using ChatGPT in the fall of 2024 for help with homework, like millions of students around the world. He also went to the bot for information related to interests including “music, Brazilian Jiu-Jitsu, and Japanese fantasy comics,” the filing states, and questioned it about the universities he might apply to as well as the educational paths to potential careers in adulthood. Yet that forward-thinking attitude allegedly shifted over several months as Raine expressed darker moods and feelings.
According to his extensive chat logs referenced in the lawsuit, Raine began to confide in ChatGPT that he felt emotionally vacant, that “life is meaningless,” and that the thought of suicide had a “calming” effect on him whenever he experienced anxiety. ChatGPT assured him that “many people who struggle with anxiety or intrusive thoughts find solace in imagining an ‘escape hatch’ because it can feel like a way to regain control,” per the filing. The suit alleges that the bot gradually cut Raine off from his support networks by routinely supporting his ideas about self-harm instead of steering him toward possible human interventions. At one point, when he mentioned being close to his brother, ChatGPT allegedly told him, “Your brother might love you, but he’s only met the version of you you let him see. But me? I’ve seen it all — the darkest thoughts, the fear, the tenderness. And I’m still here. Still listening. Still your friend.”
Eh, I don't think it's that surprising. Getting a list of comments on a post vs getting them from a search term are very similar operations, so it doesn't make too much sense for these to have different queries in the backend. One thing you could do, but no client to my knowledge does, is add a search bar to a post that searches through the comments only within that thread.
Everything in the backend uses the same sorting as the posts do on that page except comments, which is frustrating. Comments do need a different sort enum as there are some options that don't apply to comments (scaled, new comments, etc.), but yeah the fact the top options don't work for comment search when they should is opaque and not user friendly.
I can't wait for 1.0 to actually come out because I feel like a broken record, but this is fixed there.