berserk du soleil
LightNews LightNews
banner
aetataureate.bsky.social
berserk du soleil
@aetataureate.bsky.social
520 followers 190 following 7.9K posts
just some white she/her older millennial. "a villain that fights by the book of arithmetic." not a professional account. i hate reply guys and will make it weird.
Posts Replies Media Videos
Pinned
aetataureate.bsky.social
berserk du soleil @aetataureate.bsky.social · 29d
hi i'm going issue a challenge for 2026! if you have $20+ that you can comfortably spare at some point, commission an artist to illustrate something for you. a calligraphy version of an inside joke. a caricature of a relative. your pet but as the king of spades idk. spot art for your website. &c &c
aetataureate.bsky.social
i love devon! oh wow.

i adopted my bonded pair of cats in 2018, and they are each other's best friend, snuggle buddy, and wrestling playmate. they're so funny and sweet, and mine were also littermates, so they have similar body language at times despite looking very different. love bonded pairs!!
catsofyore.bsky.social Cats of Yore @catsofyore.bsky.social · 12h
The shelter I volunteer with has a unique adoption situation right now and I'd be so grateful if people could share to anyone they know in Vermont who might be a good fit. This is Devon, and his story is a little complicated so please click this link to find out more! www.hsccvt.org/Cats#sl_embe...
Photo of a handsome shorthaired tabby cat with white paws and a white stripe down his nose, lying on his side on asphalt and looking brightly at the camera with pale green eyes.
February 18, 2026 at 12:49 AM
Reposted by berserk du soleil
jamescomins.bsky.social
stop showing me the nipples of bobby kennedy's son
February 17, 2026 at 11:27 PM
Reposted by berserk du soleil
karobit.bsky.social
I've been adding more videos -- up to about 270 now -- and now I'm faced with a conundrum: does the promotional video for Konya wa Hurricane belong on this list? Hm.
www.youtube.com/watch?v=y48Z...
February 17, 2026 at 6:06 PM
Reposted by berserk du soleil
duckvalentine.bsky.social
my therapist chastised me last session because i keep bragging about how i have eight pairs of corduroy overalls, all in different colors, and in a year of therapy she's only ever seen the blue pair (which I have apparently worn numerous times)
February 17, 2026 at 4:12 PM
Reposted by berserk du soleil
kk-maker.bsky.social
> At 32, nothing says ‘happy birthday’ like everyone sharing photos of you sleeping. Booboo the bear celebrated her big day in torpor, somewhere between hibernating and being awake, conserving energy and perfecting the art of the nap.

[📸: Zookeeper Brinley | John Ball Zoo]
February 17, 2026 at 4:09 PM
Reposted by berserk du soleil
prisonculture.bsky.social
I appreciate this way of evaluating one's life.
TEXT: “Everything that I’ve done has been in some context,” Jackson said on his 65th birthday in 2007 when asked to weigh his achievements and failings, “and I’m convinced that we look back like the true judge and ultimately you judge yourself by your cumulative box score. It’s not the home run you hit one inning; it’s not the strikeout the next inning. It is the box score. And our box score — my batting average — has been one I can accept.”
February 17, 2026 at 3:47 PM
aetataureate.bsky.social
It Happened to Me: i saw my partner liking my posts, went to say good morning, he told me he was still sleeping, then i saw him liking MORE of my posts! SIR!

good morning, how are you? i'm watching youtube and crocheting, and i'm going to eat something and take some meds.
February 17, 2026 at 2:09 PM
Reposted by berserk du soleil
mrsambarlow.bsky.social
Tag yourself! What kind of girlboss are you?

I’m cursed doll.
mrsambarlow.bsky.social Sam Barlow 🔥 @mrsambarlow.bsky.social · 1d
Absolutely unhinged collection here from HBO (also includes The Brood and the 1984 Supergirl)
What kind of girlboss do you want to be? A mutated goop addict? Warrior princess?…. murderous cursed doll??
February 17, 2026 at 5:01 AM
Reposted by berserk du soleil
mismatched.bsky.social
Felt cute earlier in my cozy sweater and biology is bigger than binaries shirt
A white person wearing a black shirt with an orange bee and white text (“Biology is bigger”). Theres a green dinosaur cardigan over the shirt.
February 17, 2026 at 5:11 AM
Reposted by berserk du soleil
tofeklund.bsky.social
There are two kinds of people in the world: those who divide people into two kinds and those who
February 17, 2026 at 9:17 AM
aetataureate.bsky.social
kirkus is my choice for book reviews that usually steer me right, and today i only looked at the tl;dr sentence before picking up a horror book. this is making me think about how much we are typically told by jacket copy and even cover copy at this point. i genuinely have no idea what will happen
February 17, 2026 at 12:46 AM
Reposted by berserk du soleil
cheryllynneaton.bsky.social
This is super embarrassing for a writer because it's an admission that there are people in love with bridges and roller coasters who have a better imagination than you.
thatpetewoods.bsky.social Pete Woods @thatpetewoods.bsky.social · 1d
2 things:

First she was using ChatGPT to write a screenplay so zero sympathy.

Second seeing the number of folks who get sucked down these delusional rabbit holes- like this AI psychosis and the Q Anon phenomenon- makes me afraid we all have this potential.

www.npr.org/2026/02/14/n...
ChatGPT promised to help her find her soulmate. Then it betrayed her
ChatGPT sent screenwriter Micky Small down a fantastical rabbit hole. Now, she's finding her way out.
www.npr.org
February 16, 2026 at 11:07 PM
Reposted by berserk du soleil
catsofyore.bsky.social
People are requesting more Marcel and Francie so here are a couple more recent pics! The one of Francie showing off her magnificent tufted beans was just yesterday. 🫘
Photo of a black and white tuxedo kitten with only one eye which is gold in color, looking up brightly to the left with a red curtain in the background. photo of a fluffy white cat who looks very soft, caught in the middle of cleaning her belly so she's got one foot up in the air displaying the big tufts of white fur between her pink toe beans.
February 15, 2026 at 8:49 PM
Reposted by berserk du soleil
girldiner.bsky.social
Orange cat
February 16, 2026 at 4:38 PM
aetataureate.bsky.social
i'm still doing these! i would also love for you to donate to a u.s. immigration law center. let me know if you do and would like a pixel portrait.
aetataureate.bsky.social berserk du soleil @aetataureate.bsky.social · 23d
hi! if you'd like a pixel art portrait, please show me the animal or person + a receipt for a $25+ payment to one of the MN groups or orgs on this list:

www.standwithminnesota.com

if you can't redact, want privacy, email me: cdelbert@gmail.com
a chipper bird drawn in shades of purple chunky pixels. the background is a cheery cyan. a cat making a relaxed face, drawn in navy blue pixels with a rainbow gradient fill, on a cheery cyan background. a surprised cat in shades of purple pixels and purple fill, on a background of pale gold with colorful "noise" the late actress maggie smith, in shades of dark olive green pixels over a pale seafoam green background.
February 16, 2026 at 4:01 PM
aetataureate.bsky.social
chainette yarn says trans rights
a ball of yarn, with strands that look braided or chained. the side facing the camera looks like the trans rights flag, with blue, pink, white, pink, and blue, roughly in stripes.
February 16, 2026 at 3:48 PM
aetataureate.bsky.social
yessss i RAN to back this!!
jon.inkle.co Jon Ingold @jon.inkle.co · 1d
14 years ago we accidentally hired a genius to write the script for 80 Days. Now she’s narrative director on a deck-builder about billionaire busting.

Check out All Will Rise:
All Will Rise: a narrative courtroom deck-builder
A game about taking a billionaire to court for the murder of a river.
www.kickstarter.com
February 16, 2026 at 3:22 PM
Reposted by berserk du soleil
boxbrown.bsky.social
One time in school, I was so sick that I copied my term paper out of the dictionary. It seems like the right idea at the time.
February 16, 2026 at 2:13 PM
aetataureate.bsky.social
the sycophancy has only turned up. i am a journalist and i cover AI as part of my hard science beat. what this man did is inexcusable. "can't believe they made him work while sick!" they didn't, and he still chose to cheat. sick people go to work all the time and don't have the option to cheat.
benjedwards.com Benj Edwards @benjedwards.com · 2d
Sorry all this is my fault; and speculation has grown worse because I have been sick in bed with a high fever and unable to reliably address it (still am sick)

I was told by management not to comment until they did. Here is my statement in images below

arstechnica.com/staff/2026/0...
I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026
February 16, 2026 at 2:42 PM
Reposted by berserk du soleil
josie.zone
To everyone saying "This guy was working on what should have been a sick day — Ars Technica needs a union!!!": they ALREADY have a union, it's @arsunion.bsky.social

Even unionization can't keep people from being absolute pinecone-brains about the ethics of A.I. use
benjedwards.com Benj Edwards @benjedwards.com · 2d
Sorry all this is my fault; and speculation has grown worse because I have been sick in bed with a high fever and unable to reliably address it (still am sick)

I was told by management not to comment until they did. Here is my statement in images below

arstechnica.com/staff/2026/0...
I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026
February 16, 2026 at 9:55 AM
aetataureate.bsky.social
i just also want to urge people reading this statement not to repeat or link it and say things like "here's the timeline of what happened." he wrote this completely unverifiable statement. some of this seems . . . unlikely. and i don't believe for a second that this was his first time "trying" it
benjedwards.com Benj Edwards @benjedwards.com · 2d
Sorry all this is my fault; and speculation has grown worse because I have been sick in bed with a high fever and unable to reliably address it (still am sick)

I was told by management not to comment until they did. Here is my statement in images below

arstechnica.com/staff/2026/0...
I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026
February 16, 2026 at 12:57 AM
Reposted by berserk du soleil
cailin.dev
Oliver leads a difficult life
Oliver, an orange and white cat, is lying very comfortably in my lap
February 15, 2026 at 11:12 PM
aetataureate.bsky.social
sorry but i'm so fascinated by these absolute trainwrecks and how so many of them are aging white men in these journalism roles. people younger than them, from less overrepresented groups, have survived in these roles behind them for 10+ years and do not have this luxury.
February 15, 2026 at 11:13 PM
aetataureate.bsky.social
this is a shocking judgment error, and i would be really, really surprised if this was really the first time he used a tool in this way. sorry, you're so sick you can't read a website to pull quotes, but you're healthy enough to "try an experimental AI tool" for that work? that makes no sense
benjedwards.com Benj Edwards @benjedwards.com · 2d
Sorry all this is my fault; and speculation has grown worse because I have been sick in bed with a high fever and unable to reliably address it (still am sick)

I was told by management not to comment until they did. Here is my statement in images below

arstechnica.com/staff/2026/0...
I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026 I have been sick with COVID all week and missed Mon and Tues due to this. On Friday, while working from bed with a fever and very little sleep, I unintentionally made a serious journalistic error in an article about Scott Shambaugh. Here’s what happened: I was incorporating information from Shambaugh’s new blog post into an existing draft from Thursday. During the process, I decided to try an experimental Claude Code-based AI tool to help me extract relevant verbatim source material. Not to generate the article but to help list structured references I could put in my outline. When the tool refused to process the post due to content policy restrictions (Shambaugh’s post described harassment). I pasted the text into ChatGPT to understand why. I should have taken a sick day because in the course of that interaction, I inadvertently ended up with a paraphrased version of Shambaugh’s words rather than his actual words. Being sick and rushing to finish, I failed to verify the quotes in my outline notes against the original blog source before including them in my draft. Kyle Orland had no role in this error. He trusted me to provide accurate quotes, and I failed him. The text of the article was human-written by us, and this incident was isolated and is not representative of Ars Technica’s editorial standards. None of our articles are AI-generated, it is against company policy and we have always respected that. I sincerely apologize to Scott Shambaugh for misrepresenting his words. I take full responsibility. The irony of an AI reporter being tripped up by AI hallucination is not lost on me. I take accuracy in my work very seriously and this is a painful failure on my part. When I realized what had happened, I asked my boss to pull the piece because I was too sick to fix it on Friday. There was nothing nefarious at work, just a terrible judgement call which was no one’s fault but my own. —Benj Edwards, February 15, 2026
February 15, 2026 at 11:00 PM
Reposted by berserk du soleil
jondresner.bsky.social
I would pay a subscription fee for the ability to turn off reposts for *some* users...
aetataureate.bsky.social berserk du soleil @aetataureate.bsky.social · 2d
hi! most users never touch the settings. try turning off reposts and trending topics and see how you feel

click bottom left corner gear button
click Content and media
switch off Enable Trending Topics
switch off Enable Trending Videos
click Following feed preferences
switch off Show reposts
February 15, 2026 at 8:17 PM