People and blogs involved with and about the IndieWeb community, the fediverse, and/or the open web in general.
OpenClaw is run like the bleeding-edge project you’d expect it to be. An excerpt from of a longer post by Peter Steinberger on X:
Part of what excites me so much about working on OpenClaw is that I’m trying to answer the question:
How would we build software in the future if tokens don’t matter?
We constant run ~100 codex in the cloud, reviewing every PR, every issue. If a fix on main lands, clawsweeper will eventually find that 6 month old issue and close it with an exact reference.
Spurs vs. Timberwolves game 6 tonight is going to be big. Nice article at ESPN on the organization’s culture and longevity:
On any given day at the facility, a current Spur can walk into a room filled with championship players from the past. It’s not uncommon to go to lunch and find Ginobili dining with three-time champion Bruce Bowen, whose No. 12 jersey is retired in San Antonio. Duncan, who once had a space in the coaches’ locker room at the old facility, is a fixture at the new spot, too, along with two-time champ and 10-time All-Star David Robinson and Sean Elliott…
I remain skeptical of Tesla robotaxis and this report doesn’t make me feel better:
Tesla Robotaxis have crashed at least twice since July 2025 while a teleoperator was remotely driving the vehicles…
Waymo has the right approach. When stuck, cars can be given hints on what to do by remote staff, but the cars still drive based on their training, they can’t be controlled like a video game.
Andrew Sharp has one of the best blog posts I’ve read recently about not just the OpenAI trial, but stepping back to see the big picture of OpenAI’s founding and where things are now. On the evidence:
Musk is wrong here and he should lose. […] Across a two-week trial where Musk and his lawyers have worked every single day to put Altman’s dishonesty at the forefront of the jury’s mind, Elon is the most dishonest character in that courtroom, at least with respect to the facts at hand.
It’s a medium-long post and goes through the text messages and other surrounding details.
I work every day on a lot of different things. This requires being able to flow between projects without hitting walls. App review is a wall. It’s a momentum killer. It’s like wading through mud when you want to run.
ChatGPT personal finance is going to be popular, eventually, but initially I expect people to be cautious about giving AI access to their bank accounts. It’s read-only, which I assume is enforced by Plaid:
When you connect your accounts, ChatGPT can access your balances, transactions, investments, and liabilities to help visualize your finances or answer your questions. It cannot see full account numbers or make any changes to your accounts.
This year I had planned to download all my bank statements and feed them to Codex to help organize things for taxes. Feels more transparent that way.
Now four days since I appealed the Inkwell rejection. I’ve drafted a full blog post explaining all the problems I’ve run into with app review. Going to hold the post until Monday, just to give Apple a little more time.
I wish they had an outliner in Claude. I would use it. ;-)
BTW, here's the JSONL version of Scripting News. It has the same data as the RSS file, but in the format that AI apps are looking for, so I am told. I thought I'd try to kick this off by pushing an RSS flow through the pipe. It's like using the Grateful Dead to boot up podcasting. I needed something to put out on the wire and I had this feed handy.
Thinking about adding <source:inReplyTo> to the source namespace. Its value is a URL, by default, and has an optional isPermaLink attribute, a boolean, to indicate if it's not a permalink. Works just like the guid element in RSS 2.0. I will also add support for that in the FeedLand database, and flow it out through the socket interface. Actually that's pretty close to a full spec, at least in rss.land where we take simplicity seriously. ;-)
Is breá leat é a fheiceáil.
Last year Jeremy Keith blogged about completing Duolingo Irish, and I’ve added that as a goal for myself. I found myself in London with him in February at State of the Browser. It’s probably the last place you’d expect to hear Irish spoken, yet we had an earnest conversation over lunch, using as much as we could.
Having a proper conversation as Gaeilge with Paul was an absolute highlight for me!
Codex has had a section in the ChatGPT mobile app for a while, but only for the cloud version. The update this week is a rewrite (apparently in SwiftUI) and can connect to a Mac running Codex. Seems good. If you have a desktop Mac somewhere, the lines are starting to blur between Codex and OpenClaw.
I reached a point in my Claude work where now I can do vibe coding, in a world that I used to just be a programmer in. This means if I want to do a heavy lift, I can tell Claude what I want and it can do really big corner turns, which is something I am (as a human) terrible at, and thus resist. Today I redesigned the basic user interface of the app, and didn't read any code, I was just giving orders, and it was doing what I asked, even if every little thing it did would have been a full day's work. It's remarkable how it can do very complex things in a few seconds.
And the web framework i'm working on can do almost all the things I want to do for now, but I want to suck everything into it, and turn the whole thing into a vibe coding amusement park. So many projects I want to do, and so many I want to do with you.
We have lots of native apps, but I will never use that as an excuse to write generic “bug fixes” release notes. I like including good release notes both for our users and for myself later, as I look back on what we’ve shipped.
Still, it is a lot to keep up with. Lately I’ve been turning to Codex to get me started with a release notes draft. I use a prompt like this:
Please review all the git commits since the tag “release/3.8.4” and write some release notes for the major changes. Read the release notes from the web page here help.micro.blog/t/micro-b… and follow that style of what is important and how to phrase the changes.
It’s usually not quite right, a little too verbose, so I can then edit it to fit what I would’ve written by hand anyway. Saves a lot of time.
Manuel Moreale — Everything Feed
• Manuel Moreale
nooneshappy.com/article/native-apps-should-be-avoided-whenever-possible/
The browser is the security boundary. Websites operate within it. Native apps bypass it.
But there’s still one thing that native apps do better than the web. If you want to be able to monitor and track users to an invasive degree, the web can’t compete with the capabilities of native apps. That’s why you’ll see so many websites on your mobile device that implore to install their app from the app store.
This piece goes into the details:
Most native apps collect far more data than their website equivalents ever could. They request permissions to hardware, sensors, and background processes that browsers deliberately restrict. The third-party software embedded in these apps frequently transmits your location, device identifiers, and behavioral data to third parties before you even see a consent prompt.
ArtLung
• Joe Crawford
