@micha
Tech-, PopCulture-, Sci-Fi-Nerd @1E9tech @focusdigital @gq_germany ~ Ex-@WIRED ~ Photo/AI Stuff ~ Kurator42-Newsletter ~ 私は日本語が話せません | April 2023 | User #25.627 on bsky https://1e9.community | http://kurator42.substack.com | https://michaelfoertsch.de
Some personal news: I’m transitioning from CEO to a new role as Bluesky’s Chief Innovation Officer! I’m excited to welcome @toni.bsky.team as our interim CEO.
More here: bsky.social/about/blog/0...
Wir sind seit meinen ersten Deepfake-Versuchen von 2019/2020 sehr weit gekommen. Es ist schon echt gruselig.
2025 hat die Berliner Polizei 62 Mal mit Tasern auf Menschen geschossen. Dabei wurden 58 Menschen verletzt. Die extrem schmerzhafte Waffe wurde oft gegen suizidale Personen eingesetzt.
netzpolitik.org/2026/polizei...
Ich pendle regelmäßig mit dem RE von Bremen nach Hannover. In diesem Jahr war noch keine Fahrt pünktlich. Weil ich sonst nichts besseres zu tun hab, dokumentiere ich den März mal.
At the new ProPublica Narrated, you can listen to narrated versions of our important new investigations alongside the most compelling journalism from the ProPublica archives.
Give it a listen here:
Unser Autor Michael Förtsch wollte wissen, ob der Hype um OpenClaw gerechtfertigt ist – und hat den KI-Assistenten ausprobiert. Jetzt versteht er, warum sich OpenAI dessen Entwickler geschnappt hat.
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...
🥌👈
Months after the killing of Charlie Kirk, a growing number of lawsuits by people claim they were illegally punished, fired and even arrested for making negative comments about Kirk.
According to ICE, the Ecuadorian consulate is not clearly marked as the consulate. How much clearer does it need to be marked for ICE? www.independent.co.uk/news/world/a...
Unser Autor @micha.bsky.social trauert um den Verlust des Lesezeichen-Dienstes Delicious. Er hat nun versucht, ihn mit Vibe Coding nachzubauen – und das erfolgreich.
I just wanted to remind you that this video exists. You're welcome.
Das würde mich sehr erfreuen.
Die ganzen Studien über Mikroplastik im menschlichen Körper sind möglicherweise bullshit. www.theguardian.com/environment/...
It's Hard Fork Friday! This week on the show:
-- A hard look at Glazegate, and why it's bad when AI models are too nice
-- I got scanned by a Worldcoin orb
-- And @pjvogt.bsky.social joins us for a new segment about what's going on in our group chats
www.youtube.com/watch?v=3Lum...
It's not perfect yet. There may still be a few glitches here and there, and I think there are still a few chunks of German in some places. I used Gemini 3, Deepseek R1, Mistral Code and also did some manual programming.
The result is Emyn. It can be run on your own server, on Cloudflare Pages, on Github Pages, or anywhere else. It works with Supabase, whereby the freetier should be perfectly adequate for a handful of users.
But what I really missed was a feed reader with a good bookmarking feature that offered more than just ‘Read it later’. So I vibe coded a feed reader and incorporated the functionality of my little bookmarking service into it. Something that took a little longer than originally anticipated.
I know it's risky to release a Vibe coding project to the public. But after the penultimate hard fork episode from @caseynewton.bsky.social and @kevinroose.com, I felt inspired. I had already created a small private clone of Del.ico.us.
github.com/micha42-dot/...
😘
With Vibe Coding, people can once again express their personality and create wild, cool and stylish designs that are always different, instead of using pre-made designs from hosts such as Squarespace. It's like the 90s all over again!
My site is pretty much the complete opposite of Casey's website. I've kept it extremely minimalistic, i wanted to keep it as small as possible (without images, it is only 95 kilobytes in size). And it's hosted for free on GitHub Pages. These different approaches is what makes it so exciting!
I'm so glad that @caseynewton.bsky.social spoke so enthusiastically about how he built his website with Claude Code. Because I felt the same way about Gemini 3 Pro. I also built myself a new website and was thrilled — and almost felt silly for being so enthusiastic about it. michaelfoertsch.de
Auch das Jahr 2026 verspricht ein spannendes Kino- und Streaming-Jahr zu werden. Zahlreiche Science-Fiction-Filme sollen im Kino, auf Netflix, Amazon Prime Video und Co. ihre Premiere feiern. #sfcd #film #sciencefiction #kino #netflix #amazon #DisneyPlus #AppleTVPlus #streaming
#Quake Brutalist Jam 3 is fantastic! It's a package of 77 maps created for a mapping jam on the theme of brutalism. They are now available for download as a map pack or as a complete bundle with the source port Libre Quake – free of charge and ready to play right away.
A screenshot of Waterfox Git repo that reads: About Waterfox: Waterfox is an open-source, privacy-focused browser based on the popular open source browser with a red panda as a mascot. It is designed to be a drop-in replacement for said browser that offers enhanced privacy features, performance improvements, and customizability while maintaining compatibility with existing extensions. Key Features: - Privacy-focused: Removal of telemetry and tracking, with bare minimum of data collection for operation. - Performance-oriented: Optimized for modern systems - Customizable: Support for classic and modern extensions Cross-platform: Available for Windows, macOS, Linux and Android - Modern: Regular updates to stay current with web standards
Waterfox is a free and opensource browser based on Firefox with all LLM or AI stuff removed. This might be the replacement.
Repo github.com/BrowserWorks...
Home page www.waterfox.com
Blog post www.waterfox.com/blog/no-ai-h...
Wortneuschöpfung des Tages: "leidensinnlich".
Donald Trump granted 238 pardons and commutations in his first term. In his second, he has issued nearly 2,000. https://www.newyorker.com/magazine/2025/11/24/the-meaning-of-trumps-presidential-pardons
