sabreW4K3@lazysoci.al to Technology@beehaw.org · 29 days agoChatbot that caused teen’s suicide is now more dangerous for kids, lawsuit saysarstechnica.comexternal-linkmessage-square39fedilinkarrow-up181arrow-down10cross-posted to: [email protected]
arrow-up181arrow-down1external-linkChatbot that caused teen’s suicide is now more dangerous for kids, lawsuit saysarstechnica.comsabreW4K3@lazysoci.al to Technology@beehaw.org · 29 days agomessage-square39fedilinkcross-posted to: [email protected]
minus-squaresabreW4K3@lazysoci.alOPlinkfedilinkarrow-up8·29 days agoThe title is straight from the article
minus-squarekinttach@lemm.eelinkfedilinkEnglisharrow-up7·29 days agoThat is odd. It’s not what I see:
minus-squaresabreW4K3@lazysoci.alOPlinkfedilinkarrow-up7·29 days agoCould be different headlines for different regions?
minus-squarekinttach@lemm.eelinkfedilinkEnglisharrow-up11·29 days agoOr they changed the headline and due to caches CDNs or other reasons you didn’t get the newer one. archive.today has your original headline cached. Thanks for posting. While it’s a needlessly provocative headline, if that’s what the article headline was, then that is what the Lemmy one should be.
minus-squaretechnocrit@lemmy.dbzer0.comlinkfedilinkarrow-up4·edit-229 days agoThey most likely changed the headline because the original headline was so bad. If people are still seeing old headline, it’s probably cached. Try a hard refresh or a different browser or a private browser, etc.
The title is straight from the article
That is odd. It’s not what I see:
Could be different headlines for different regions?
Or they changed the headline and due to caches CDNs or other reasons you didn’t get the newer one.
archive.today has your original headline cached.
Thanks for posting. While it’s a needlessly provocative headline, if that’s what the article headline was, then that is what the Lemmy one should be.
They most likely changed the headline because the original headline was so bad.
If people are still seeing old headline, it’s probably cached. Try a hard refresh or a different browser or a private browser, etc.