Advertisement · 728 × 90

Posts by Benj Edwards

I decided to collect new board games even though I am too ADHD to play them 😂 They look like so much fun, and it kinda osmotically rubs off when you just look at them

20 hours ago 16 0 7 1

Petition to widen parking spaces

1 day ago 13 0 5 0

You didn't hear it from me but everything's going to be OK.

2 days ago 205 20 15 2

I am very thankful for my friends and the kind people out there who have checked in over time. I am doing well, getting some rest, taking time to care for my mom with Alzheimers at the moment

In particular I want to thank @textfiles.com who is literally one of the best humans ever made

1 week ago 54 0 1 0

I’m on a news vacation at the moment but I tried to mostly read social media feeds from people who work at tech companies and experimenting with tech to see where the wind is blowing

1 week ago 1 0 0 0
A young boy sits at a computer desk with an Atari 800 computer and various accessories. In his chair, he holds a joystick to play a game.

A young boy sits at a computer desk with an Atari 800 computer and various accessories. In his chair, he holds a joystick to play a game.

A gamer in his natural habitat.

Photo scan by @benjedwards.com

1 week ago 20 3 1 0

Thanks man

1 week ago 1 0 0 0

Thank you

1 week ago 2 0 0 0

Thanks

1 week ago 0 0 0 0

When I was a kid, I thought gregariousness was a disease that turned you into Greg

1 week ago 15 0 7 0
Advertisement
Post image

Same.

3 weeks ago 8 1 0 0

As I roam my house from room to room or in the car throughout the day I find myself carrying a small constellation of gadgets with me, a Game Boy, laptop, Switch 2, etc. So now I just put them all in what I call a “nerd bag” to make it easier. Waxed canvas with lots of pockets

3 weeks ago 22 2 1 0
Post image

The Activision Rainbow awaits! 😁

(Atari 2600 cartidges)

3 weeks ago 68 6 2 0
Red Thermos brand “Photon” lunch box with various stickers including Toad, Hammer Bros, Nintendo Magic Mushrooms, and Billy Lee from Double Dragon

Red Thermos brand “Photon” lunch box with various stickers including Toad, Hammer Bros, Nintendo Magic Mushrooms, and Billy Lee from Double Dragon

My late 1980s lunchbox 😂

1 month ago 43 0 7 0

I wonder if consciousness evolved as an internal self-evaluation loop that can probe the brain’s network and generate additional context on an event (rumination) to give the event more meaning and aid survival

1 month ago 12 0 7 0

Thanks for the kind words of support, it means a lot. It’s no secret that I have been struggling with effects of many covid infections over time. It’s been grinding me down and I ignored it for too long, but I am working with new doctors to get fully well so I can figure out the next chapter ahead

1 month ago 96 1 15 0
A 1980s bedroom with an Apple II on a desk and a giant pencil on the wall. From “How to Design and Build Storage Projects,” Ortho Books 1983, p.22

A 1980s bedroom with an Apple II on a desk and a giant pencil on the wall. From “How to Design and Build Storage Projects,” Ortho Books 1983, p.22

This is perhaps the most ideal bedroom
I have ever seen 😁

1 month ago 33 2 7 2
Preview
Robert Tinney: 'Byte' Magazine and Beyond Robert Tinney's a big name in retro tech. Here's a collection of lesser-known facts and art from the famed Byte magazine cover artist.

This post about Robert Tinney is incredible. Very in-depth and lots of great images to browse: 70s-sci-fi-art.ghost.io/robert-tinne...

1 month ago 46 15 3 1

Thanks I deeply appreciate it

1 month ago 37 0 0 0
Advertisement

Thanks I appreciate it

1 month ago 4 0 0 0

I agree completely

1 month ago 47 0 3 0

Thanks man, it’s been a rough week, even before all this happened!

1 month ago 17 0 0 0

I agree I am very sorry I have been remiss to explain it! Here is my statement: bsky.app/profile/benj...

1 month ago 0 0 0 0

I agree I am very sorry I have been remiss to explain it! Here is my statement: bsky.app/profile/benj...

1 month ago 0 0 1 0

I agree I am very sorry I have been remiss to explain it! Here is my statement: bsky.app/profile/benj...

1 month ago 0 0 1 0

I agree I am very sorry I have been remiss to explain it! Here is my statement: bsky.app/profile/benj...

1 month ago 2 0 0 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

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

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...

1 month ago 437 59 76 100
Advertisement
“We will launch during a dynamic political environment where many civil society groups that we would expect to attack us would have their resources focused on other concerns,” according to the document from Meta’s Reality Labs, which works on hardware including smart glasses.

“We will launch during a dynamic political environment where many civil society groups that we would expect to attack us would have their resources focused on other concerns,” according to the document from Meta’s Reality Labs, which works on hardware including smart glasses.

At least one Meta employee thinks it's a good time to add facial recognition technology to glasses because we're too distracted by fascism to effectively protest www.nytimes.com/2026/02/13/t...

1 month ago 285 159 13 36

macOS 26 Tahoe is so painfully ugly...why Apple, why??

Between the travesty of Tahoe and iOS 26, somebody needs to do a hard reset on the software design team over there

1 month ago 25 1 2 0

Thanks!

1 month ago 1 0 0 0