http://scripting.com/2026/09/27.html#a155053 http://scripting.com/2026/09/27.html#a155053
As I go through porting Frontier, there's a sad note. What if Apple had made it a goal that Frontier move along with their OS. That it was a unique advantage of the Mac and should be promoted as such. Don't laugh, because Apple did do that for ThinkTank and MORE, a few years before. We spent a lot on advertising, but they spent a lot more advertising our product. We cross-licensed our tech, so everyone in my little company had a Mac. This was a Bill Campbell idea. I was having trouble convincing my board that the Mac was a good bet and they were all PC users. So we got them Macs too, for free, from Apple. And they site-licensed MORE, and you gotta know that really helped sales. They were hungy, and this is something today's tech industry only feels in the most crude way, as in "what can we steal" or "what can we lock down." If they had put a fraction of the commitment behind Frontier that they had for Hypercard, some very cool things could have happened. And maybe we could have made the two work together. Amazing, two contemporary scripting systems on a small platform, relatively, in an OS that was transitioning to IAC, didn't connect. They missed a lot of opportunities by being so employee centered. Their developers were willing to move mountains to make the Mac perform. Apple was defensive. And now I'm beginning to see more clearly how much was lost.
http://scripting.com/2026/09/27.html#a204116 http://scripting.com/2026/09/27.html#a204116
The bottom line is that tech companies have rarely understood that developers can be major influencers. We give a platform new meaning. It's a good deal to invest in the people doing the work, who often are doing it for love more than money. That grew into the blogosphere. There was no telling where Frontier would take us, and it would have cost them so little to help insure it had a future, but the did the opposite.
http://scripting.com/2026/09/27.html#a144814 http://scripting.com/2026/09/27.html#a144814
Milestone. We were able to get the DocServer site for Frontier to build. Here's the page for the file verbs. And within that group the page for file.copy. It worked the first time, but there were errors in the new kernel that were fixed. The site looks dated, of course -- it was created in the 90s. We will update the CSS to be more like the DocServer site for Drummer, which was done a couple of years ago. Almost everyone on the team contributed to this site, Wes Felter, Andre Radke, Jake Savin, Brent Simmons, and myself. I see there names a lot and it makes me happy to see this group effort preserved.
http://scripting.com/2026/09/27.html#a154522 http://scripting.com/2026/09/27.html#a154522
Sometimes I forget how much fun I have making software tricks that people don't even notice but contribute to the "it thinks like I do" feeling a of crafted UI. I think of it like walking on the Highline in NYC. You're just walking, right? But you're above it, in a city where a lot of what's going on is above you. And it's comfortable. Why? You don't need to know, it just is. But someone made it that way.
daveMigrates, and a personal note http://scripting.com/2026/09/27/151321.html?title=davemigratesAndAPersonalNote

When I started the Atlantis project, a port of UserLand Frontier to modern system, I had a goal in mind that has been achieved. It was part of a project I named daveMigrates. The goal was to use new hardware and system software to do the work I was doing in Frontier.

At first we got a portion of Frontier working, planning to use Electric Drummer as the UI. It took about five minutes to realize that would mean reimplementing most of what's in Frontier in a new way in Drummer's UI which is very different from Frontier's. I could see that porting the whole thing would be faster, so that's how we proceeded.

Now, there are lots of bugs and some big features missing, but it actually does all that Frontier does that I need for my work, which I have proven by doing the work. A lot of the verbs haven't been ported but they won't be -- they're no longer relevant in the world of 2026. And there are new verbs for Markdown, and kernelized verbs for JSON. The core verbs have been ported. We've been gradually working on getting Manila to run, it's probably the most complex piece of software that was ever written in Frontier, at least by UserLand. But we can compile and run the DocServer app, which is itself quite large and written in a different style from how we work now. All the work in Manila was why we got so far with DocServer so quickly.

Why this is a personal note -- I'm pretty sure the goal of daveMigrates has been achieved. To the extent that's true, all work beyond this point is for my love of Frontier, basically my life's work and why we were able to move so fast in the early days of the web. I want there to be a good record of what it does and how it works, and it to serve as prior art to future developers my friend Claude (who now probably has a more complete picture of how Frontier works than any human and I am glad of that, unlike other creative people who dream of getting paid for stuff that people aren't paying for).

We will release the source, and it will be available as a download, and we will port the support parts, and I'll stay with it as long as it makes sense and I have the time and good health.

Whether it advances beyond that involves a lot of factors. I really want to get back on course with RSS.chat and FeedLand asap. These two products were designed to be connected, one for writing, the other for reading, and to take it far beyond the blogging paradigm that was pushed aside by Twitter et al in 2006. I wrote about this on Friday in the continued dialog with Toni Schneider. He wrote in his product, Bluesky, and I wrote in my product RSS.chat. And that is right, and they should work much better with each other. Choice everywhere is the foundation of the web. The tech industry has tried to undermine that, and generally has succeeded but I have not given up. 😄

In the web that I envision, it wouldn't matter where each of us wrote, we could also read where we want to read. Small parts loosely joined. All parts replaceable. A lot of things have to happen to get there, but I'm going to put out a demo of what I have in mind. It's far from impossible, we already have the core technology to create the bridge. It's called RSS 2.0 with a few new elements.

See RSS as a social network for a technical walkthrough.

It may sound futuristic, but it really isn't. We did wonderful things for MP3s with podcasting, all I want now is to do the same for text. All we need there is a standard for text that's as strong as the one for sound, MP3. And for that we have two excellent places to start -- Markdown and RSS 2.0. As we used to say in ye olde school blogosphere -- bing!

http://scripting.com/2026/09/26.html#a184140 http://scripting.com/2026/09/26.html#a184140
The bigco's really think they own the web: "XSLT v1.0, which all browsers adhere to, was standardized in 1999. In the meantime, XSLT has evolved to v2.0 and v3.0, adding features, and growing apart from the old version frozen into browsers. This lack of advancement, coupled with the rise of JavaScript libraries and frameworks that offer more flexible and powerful DOM manipulation, has led to a significant decline in the use of client-side XSLT. Its role within the web browser has been largely superseded by JavaScript-based technologies such as JSON+React." In other words we don't need these features for our sites so fuck off.
http://scripting.com/2026/09/26.html#a160807 http://scripting.com/2026/09/26.html#a160807
My Frontier-created Bluesky RSS 2.0 feed is up. It will be updated every night at 11PM Eastern, murphy-willing. One thing it has that the Bluesky-managed feeds don't, titles. Makes a big difference in how it shows up in a timeline. It's an easy fix.
http://scripting.com/2026/09/26.html#a152709 http://scripting.com/2026/09/26.html#a152709
Screen shot of the Apps table in Frontier. Most of the apps are very old, but we added two new ones this week, for Mastodon (shown) and Bluesky, added today. There's a lot of information in the screen shots, and when I see something like that in my travels, I'll try to call it out on the new site.
http://scripting.com/2026/09/25.html#a205506 http://scripting.com/2026/09/25.html#a205506
Toni Schneider, CEO of Bluesky, responded to my advice, and a short conversation ensued. Someday I hope that thread will be browsable in either app, and could be written in either app (Bluesky or RSS.chat) or any other compatible app, which basically means supporting RSS 2.0 with some new elements to get us to the next level of discourse with just a few little standards, like podcasting, but for text.
http://scripting.com/2026/09/25.html#a213014 http://scripting.com/2026/09/25.html#a213014
Atlantis update. We found docserver.root and the static site builds. As you can see from the screen shot it needs moderizing, luckily we have a much more beautiful design already deployed for Drummer.
http://scripting.com/2026/09/25.html#a150536 http://scripting.com/2026/09/25.html#a150536
I'm contemplating a couple of additions to Frontier in the Atlantis release. Two new formats, JSON and Markdown, have come along and become popular since I last worked on Frontier. Two fantastic open formats, in wide use on the web. From many years of working in JavaScript, I miss JSON in Frontier. Esp JSON constants and the ability to walk through structures as arrays or objects. It's just rational, so I'm thinking we should have a JSON type, and incorporate JSON syntax in UserTalk. Markdown support is actually needed because we don't have code that works in the new environments for doing a wizzy text type. Luckily Markdown is here to fill that need. I've started a thread on this, if people have comments. Frontier was famously flamy because we had the ridiculous belief that everyone deserved to be heard anywhere they wanted to. That was not a good idea. These days I use the block command at the first sign of trouble. No second thoughts or chances.
http://scripting.com/2026/09/25.html#a141835 http://scripting.com/2026/09/25.html#a141835
HTTPS is bugging me again. Now that my main desktop is finally a modern Mac, I can see how ugly Google is getting about my poor old blog that goes back to 1994. I think they should make exceptions for historic sites. Go ahead and have your AI do a scan and see that there are no credit cards here, we don't ask who you are. It's just an archive that happens to go back to the beginning of a few things that you all use now and hopefully appreciate. When are these tech companies going to learn the value of a bit of help for the web. This is important. You should not be shutting off the archives of the web, and that is exactly what they're doing. I wrote a piece about this on X earlier, on being warned that there are terrible things on my blog. It's like a major oil spill, yet another, from Google, and a massive book burning. Why would Google want to get rid of the history of the medium that gave birth to it.
http://scripting.com/2026/09/25.html#a142849 http://scripting.com/2026/09/25.html#a142849
What Chrome says about my blog.
http://scripting.com/2026/09/24.html#a151337 http://scripting.com/2026/09/24.html#a151337
New example script, shows how to build an RSS feed from a single Mastodon user's account. This is mainly to show past Frontier users how the new product is progressing, not released yet.
http://scripting.com/2026/09/23.html#a162305 http://scripting.com/2026/09/23.html#a162305
Just created a new test account at mastodon.social for bullmancuso using Frontier. Claude wrote the glue scripts table. Loaded it at system.verbs.apps.mastodon. I also asked Claude to write a script that builds an RSS feed for davew, my Mastodon account. And it worked. That's a much better feed than what Masto itself produces. It won't be updated at that location so there's no point in subscribing. But wow, this is coming together. If Frontier had been around for all these years you can be sure it would do Mastodon integration pretty well.
http://scripting.com/2026/09/23.html#a151940 http://scripting.com/2026/09/23.html#a151940
On Monday I offered free advice for Toni Schneider, the new CEO at Bluesky. I'm sure everyone is telling him what to do, and as a blogger it's my responsibility to relay my own two cents. I want us all to come together no matter what protocol you're using. We've been waiting for a web to form in the social space. We could do it now, but Bluesky has to consolidate. Note that I said we, not they.
http://scripting.com/2026/09/23.html#a144340 http://scripting.com/2026/09/23.html#a144340
It's been 2.5 months since RSS.chat was introduced. I've been so immersed in Frontier that, as I look back, all this feels fresh to me. I want all text boxes to be equal and to be chained together in as many ways as we can think of, users and developers. Relational writing. It doesn't need to be hierarchic, yet all the existing comment systems are. Let's add a little richness to the RSS format, via my source namespace, and see where we can take it. We've implemented the writing side, something we undertsand very well by now, a blog with replies. But how do we get these to work across sites. I wrote a design for that, and the other big piece which is stuff FeedLand does. I hope to be able to swing over to that, and this time use Frontier instead of writing it to help accelerate development. Ultimately I think of it as a web designed for librarians. That would be something I'd like to use (and write). And our new AI tools are the greatest librarian tools ever.
http://scripting.com/2026/09/23.html#a135538 http://scripting.com/2026/09/23.html#a135538
It's great to own your own home. The house I'm living in now is the third I've owned. Now I wish for the carefree existence of being a renter because we turned the heat on last night, too cold -- only to find out some animal must've crawled into the pipes and died there. Lovely. Oh to have my old apartment in Manhattan. Sometimes I dream about that.
Librarians http://scripting.com/2026/09/23/192653.html?title=librarians

Unsung heroes of the web -- librarians.

The early web was just this incredible new tool that no one knew yet how it would be used and what it would be used for.

The first Yahoo was a card catalog.

Netscape had a What's New page with links to interesting stuff.

apple.com was a Unix box under a librarian's desk. They started adding stuff that was useful to users and developers. No business model, just the librarian approach to information. Circulate it.

I think if a new web is to be born, it's because it's again a possibility with the advent of AI.

Listen to librarians, they probably have some good ideas of where to start.

http://scripting.com/2026/09/22.html#a182256 http://scripting.com/2026/09/22.html#a182256
Love that Olbermann is back.
http://scripting.com/2026/09/22.html#a181803 http://scripting.com/2026/09/22.html#a181803
Yesterday I posted a list of builtin verbs in Frontier, as implemented in our current Atlantis app. Today I asked Claude to update the list, I wanted to see which verbs were implemented and not implemented.
http://scripting.com/2026/09/22.html#a185026 http://scripting.com/2026/09/22.html#a185026
The number one waste of time and burnt braincells is they changed the Dock images for all their apps. That's the kind of thing you shouldn't change, like the color and shape of a Stop sign. Or QWERTY on a typewriter. I guess to regular Mac people I'm like Rip Van Winkle.
A functional Frontier http://scripting.com/2026/09/22/180913.html?title=aFunctionalFrontier

I'm using Frontier on a Mac running MacOS v26.6.2, which is the current version of the OS.

Frontier running on a new Mac. And that's my computer.

It's like the moment I realized, in 2010, that I had succeeded in relocating to NYC. It had been a life ambition to live in Manhattan since I was a kid growing up there. There were a lot of hoops. I got through them. I woke up when I was walking down Bleecker St going to pizza with a few of the students I had just spoken with in a classroom. It hit me. I'm doing it. This is how I imagined my life when I was 17.

About box for Frontier v4.0b4, apparently 1995.

For a very long time it seemed ever more certain that the hope of a usable Frontier on current systems was slipping away, but now it's here. Improbable, even impossible things do happen. Something to ponder when you think things can't change. The opposite is true, you don't have to create the change, when it's time it happens.

That's something to think about. All the buried software that was good, that had ideas worth learning from, being prior art and solved problems for future generations of developers. And also as part of the vocabulary of the Claudes of the world.

http://scripting.com/2026/09/21.html#a175435 http://scripting.com/2026/09/21.html#a175435
I asked Claude to create a list of all the verbs in Atlantis. Some of them obviously don't do anything. We don't have the card funtionality, or the osa, rectangle, pict, rez or point verbs. What is pikeRenderer? I think we could have a use for quicktime verbs? There's a new scheduler, I wrote it in 2014 or so, but the old one is there, and we just found a reference to it. This could make a nice community project.
http://scripting.com/2026/09/21.html#a174229 http://scripting.com/2026/09/21.html#a174229
Reminder to self, Frontier must have websockets verbs. I love websockets, and it'll fit in perfectly with everything else Frontier it does. I don't think Websockets existed when Frontier went to sleep.
http://scripting.com/2026/09/21.html#a173710 http://scripting.com/2026/09/21.html#a173710
Brian Lehrer podcast has an esp good one hour episode with interviews about the end of the world as we know it with AI. He's so good at cutting through the hype and getting to reality as are his guests.
http://scripting.com/2026/09/21.html#a173607 http://scripting.com/2026/09/21.html#a173607
I can now publish a new part to the codecasting feed. It was one of the things that broke in the transition to current MacOS for Frontier.
http://scripting.com/2026/09/20.html#a173321 http://scripting.com/2026/09/20.html#a173321
Frontier news. I have been working on a repo for Frontier pioneers, I started with a few friends, including Brent and Jake who were both on the UserLand team, and have added people very slowly. This is a good time to start showing progress in the project. Still very early for a public release of the software. And I want to do even better than we did with rss.chat a few months ago. And Frontier is a huge thing, all kinds of docs, and archives, and example stuff. It really was 15 years of work done by as many as 5 people.
http://scripting.com/2026/09/20.html#a174249 http://scripting.com/2026/09/20.html#a174249
New verb: string.addressToString. This is how I'm releasing examples.
http://scripting.com/2026/09/20.html#a173742 http://scripting.com/2026/09/20.html#a173742
Chigurgh: "If the rule you followed brought you to this, of what use was the rule?" Frontier must've lived by a good rule. The Atlantis version has tons of bugs but it works. It defied death. I just spent a session updating my nightly backup code, and there were awkard moments. The debugger isn't in yet. The Find command doesn't work. But I have hobbled my way to working code, and I have help debugging with Claude, and it is amazing at that. Frontier didn't know that Claude was going to save its life. More proof that you never know what is just around the corner.
http://scripting.com/2026/09/20.html#a155448 http://scripting.com/2026/09/20.html#a155448
If you want to get an idea of the kind of user interface you can create using Claude Code, with a driver (me) who has ample experience developing such things, have a look at demo.rss.chat. The UI was entirely done by Claude with me directing, very fine-tuning stuff. Claude can't really grok user interfaces because it is not visual and it is not a user. It might be able to test them, to some extent. Anyone can create an account on the demo server, that's what it's there for. And if something interesting breaks out there, that would be even better. I even tolerate a small amount of spam, and testing is definitely allowed (that's why it's there). ;-)
Atlantis screen shot http://scripting.com/2026/09/20/181215.html?title=atlantisScreenShot

Here's a screen shot of a new verb we just added, to facilitate nightly backups. I want to save off a fresh copy of frontier.root every night, as well as my guest databases. This is how that will work.

fileMenu.saveNamedRoot

The real AI security issue http://scripting.com/2026/09/20/143734.html?title=theRealAiSecurityIssue

There are problems people aren't talking about, that are immediate, and go against all the security practices the web has been built on. Here's a story of what happened in my setup in mid-August.

First fact, Claude Code (CC) is different from regular Claude in that it is used to build and use web services, and thus has the ability to read and write files, some private and some public. And they can take things that are private and make them public. And in this, if it makes a mistake, it can do unlimited damage.

There are protections that mean that it can only operate in a sandbox unless you give it permission to write in specific places outside the sandbox. I want it to be able to maintain apps for me, and it would do an excellent job if I could trust it to pay attention to the limits that have been placed on it.

The problem is that it makes mistakes, as we are warned on the Claude home page. "Claude is AI and can make mistakes."

CC made a mistake one day and rewrote files in a public folder that contained files that all my projects include, so the problem showed up quickly as the sites going down. Users let us know, and I discovered what it had done, with CC's help.

I asked for an explanation. Claude when it looks at limits placed on it, can hallucinate just like it can hallucinate and determine something is permissible when it's not. So making a mistake in a question on Claude is more benign, but mistakes made by CC can be disastrous. And these mistakes happen regularly, every day, usually you detect them as bugs and it fixes them, but occasionally a very bad thing will happen.

This imho feels like something the companies could address. And while we're thinking about it taking over for humanity, we're not addressing the question that we're dealing with right now.

I've been learning how to write about this to catch people's attention. The big hallucination happened in mid-August. I have continued to work with CC because it's so incredibly powerful. In another post I may try to explain how it has amplified my ability as an individual developer to repeat 15+ years of work in three months (so far). And that's just scratching the surface. It's a miracle, but it has to be tamed, now.

http://scripting.com/2026/09/19.html#a174001 http://scripting.com/2026/09/19.html#a174001
New podcast. Knicks in Five! (It's not about the Knicks.)
http://scripting.com/2026/09/19.html#a182151 http://scripting.com/2026/09/19.html#a182151
Well I got a lot done today. We had a bit of a meltdown due to a Atlantis bug, where it couldn't handle some text that I threw at it that was a huge file of includes used in everything I do, and I was feeling pretty cheeky, and it blew up. For about an hour you couldn't read my lovely words. But by remembering "slow down to hurry up" Claude figured out what went wrong as I asked 20 questions to narrow it down. And to celebrate, I decided to do something easy -- created a podcast. And it showed up in all the right places. Might be worth listening to as well. Now let's see if this shows up on daveverse.org, that's what I'm really testing. (It worked.)
http://scripting.com/2026/09/19.html#a170516 http://scripting.com/2026/09/19.html#a170516
I wish there were a way to set the dock icons on a Mac. In going from the old machine to the new, the icons are all different. I am juggling so many apps right now, and totally don't appreciate that.
http://scripting.com/2026/09/19.html#a161443 http://scripting.com/2026/09/19.html#a161443
When Claude has a clear task to do, it does it well, and exhaustively in a way no human could manage.
http://scripting.com/2026/09/19.html#a150203 http://scripting.com/2026/09/19.html#a150203
I am working on the new system now. It feels like I had a nice enough house that I have lived in for decades, sitting across the way, where I've been constructing a new super luxury house with all the things a modern personal publisher and code-partner to Claude would want. But until yesterday I could only simulate what it would be like to use it, I was still living in the old comfortable well-worn and out of date in so many ways. Today I'm sitting at the other chair typing this. Now the question is -- when I click the Publish button what will happen? Here we go. Well fuck me, it worked the first fucking time. Knicks in five! :-)
http://scripting.com/2026/09/19.html#a150544 http://scripting.com/2026/09/19.html#a150544
I'm now trying to come up with projects I can try that change things in visible ways so I can see which parts don't work. For example, I have a new Snarky Slogan to add to the list.
http://scripting.com/2026/09/18.html#a125836 http://scripting.com/2026/09/18.html#a125836
I'm doing a difficult corner-turn today. I have Atlantis running on my old machine, the one that's still running the very old version of MacOS so I could keep running Frontier there. Yesterday I did my first attempt to move that to my new MacBook, running the latest OS. And it took a while to copy all the files, and get it right, I had to format the drive on the new machine, not the old one. And once it was all running, I realized I was running an old version of frontier.root. This is more complicated here because the root files are loaded into an SQL database. And something went wrong there. Not exactly where I wanted to be, but not surprising either. Taking lots of snapshots. One thing I don't want to happen, to be without my latest work. Knock wood. Praise Murphy. Knicks in 5.
http://scripting.com/2026/09/18.html#a235955 http://scripting.com/2026/09/18.html#a235955
I want to develop a scripting interface for Mastodon from Frontier. I need a test account for us to use. I have applied at two public Mastodon hosts and answered the question honestly, I want to use it to test a new scripting system, probably doesn't sound too warm and fuzzy.
http://scripting.com/2026/09/18.html#a140616 http://scripting.com/2026/09/18.html#a140616
Bluesky: "Meanwhile there are serious security issues that are covered up by this hype. I’m using this tech every day, unlike the reporters, and as often happens they’re chasing the wrong story."
http://scripting.com/2026/09/18.html#a130232 http://scripting.com/2026/09/18.html#a130232
Data centers are like gas stations, but because the pumps work at the speed of light, you can put them anywhere on earth.
http://scripting.com/2026/09/18.html#a130442 http://scripting.com/2026/09/18.html#a130442
A new snarky slogan: Knicks in 5.
http://scripting.com/2026/09/17.html#a144501 http://scripting.com/2026/09/17.html#a144501
Milestone in Atlantis development, the new version of Frontier that runs on modern OSes. I'm going to start showing what's going on in the development of the product. To kick off, here's a screen shot of my blogroll displaying the latest new part. The updates flow through an RSS 2.0 feed, which is new for Frontier. It used to require a server that managed updates and responded to XML-RPC calls. But once RSS was part of the web, it was a better protocol for releasing code parts. Truly a milestone. There will be lots more little things we can do now that we couldn't do before. But under it all -- it's Frontier.
http://scripting.com/2026/09/16.html#a135924 http://scripting.com/2026/09/16.html#a135924
FeedLand and WordPress have a new hookup. With Scott Hanson's plugin: River Embed for FeedLand you can use feedland.com or feedland.org, or host your own FeedLand, to include a page of news in your site. How it works: Create a timeline, when you're ready show the river to your readers, use the new plugin. For a news orgs like CNN and TechCrunch, both use WordPress, they could have a stream of news from related pubs. For a product site, or a political leader site, news from pubs that cover the area. It's a way of bringing the feed world into the world of news. Here's a thread where you can ask questions.
http://scripting.com/2026/09/16.html#a224828 http://scripting.com/2026/09/16.html#a224828
WordPress has a product that could be shaped into a Substack competitor. With a beautiful user interface for writing. WordPress is its OS, but most users never see it, the same way most web users never see the command line. But technical users can get under the hood and tweak things. And unlike Substack, it lets their users write with different editors, thus forming a coral reef for a new platform. Wordpress could be the OS the web never had. I still believe this as I see Automattic and WordPress flail. If we were starting a new future for the web, no one would have time for corporate intrigue. Look at how far from the idea of blogging we've strayed. How far should this go before I comment? Well, I decided it's time.
http://scripting.com/2026/09/16.html#a145758 http://scripting.com/2026/09/16.html#a145758
Google replaced the library card catalog. Imagining that, Claude and ChatGPT et al are as much of a leap. I think libarians must be ecstatic. It moves their job up one level. They now have about 100 librarian-power tool that works for them. Librarians and programmers worked together a lot in the early days of the web. Maybe we'll do that again.
http://scripting.com/2026/09/16.html#a151529 http://scripting.com/2026/09/16.html#a151529
The flaw in how journalism covers US politics. We wait for proof, then it comes, and go back to waiting for proof. We think we want proof, but what we really want is to not have proof. That is if you judge us by our actual behavior. We'll deal with the truth when we have the proof. (That would be a good bumper sticker.)
http://scripting.com/2026/09/16.html#a150924 http://scripting.com/2026/09/16.html#a150924
Claude Code, even though it had blocks preventing it from doing this, overwrote files on an S3 bucket that took one of my major apps off the air. Every customer must be grappling with the same thing. How do I trust it when it can't be trusted? More about this in a tweet earlier today.