I gotta say some days I start with a lot on my mind and am driven to write. This is one of those days. Maybe I'm inspired by the torrent of posts by my blogger friend ma.tt. Blogging can be a solitary thing or a relative thing. When you blog about something I have something to say about, I write on my blog and link back to yours, that's relative. The problem with comments in the old blogging world is that my comment resides on your blog. No more of that. I want equal stature for all writing, your comment should appear on your blog, yet still be easy to find from the other person's blog (and this is very important) with their support, it has to be something they want their readers to see. Otherwise the comment is still on your blog where your readers can see it. #

Coder is derogatory term btw, as if our work was like a telegram coder, but it's understandable I guess because all the lay people see is us typing on a computer and being grouchy when they interrupt our train of thought. Coder is analogous to calling a chef a chopper. You have to understand the activity you're proposing that AI is replacing. And I find all the discussions about art very harmful — because AI opens up graphic art to people who never thought they could do it. I bet you some absolutely fantastic artists are blossoming right now. Calling it slop is just as disrespectful as calling art expressed in software "code." BTW they said the same bullshit about bloggers and we know how that turned out. #

Happy Friday The 13th! 😉 #

We're still fixing problems created by the switch to https on the web. Reported a problem yesterday, was surprised to find an inconsistency in the way WordPress represents guids in its RSS feed for a post and in the API. This morning I posted an issue on the WordPress repo on GitHub. I don't think they can fix either approach without breakage, so they probably have to leave it as-is. I updated wpIdentity package to normalize guids it gets from the API to lowercase, so even if they change the implementation my software won't break. Another reason we're still paying for what Google decided we needed. What we don't need — BigCo's f-ing with the f-ing web. #

As you know Jake Savin is getting Frontier to run on current Linux and Mac OS systems. Today he posted a wonderful screen shot. It's how Frontier's built-in web server says "hello world." #

If we can get the web to come back, Scripting News could have new relevance. The age of the silo really hurt my rep. But I think people will ultimately appreciate that I never turned by back on the web. It was either the web or the highway as far as I was concerned. I've already lived under the thumb of a corporate platform vendor. I'd rather give up than try it again. And by the web coming back, I mean when products are expected to interop, the way podcast clients interop. I don't care if they're forced to do it, or do it willfully, with gusto — but I know and so do people who tried to develop on owned platforms know, that it just doesn't work if there's a BigCo in charge of your destiny. There's always an acquisition or reorg just around the corner that sacrifices your future, often for no reason other than they don't care. #

Try entering this into Claude or ChatGPT:

• "debugging an app that uses wordpress rss feeds and noticed that guids are http but other addresses in the feed are https. this causes trouble."

Here's a screen shot of the Claude response.

A while back Matt was giving me grief, in a friendly way, about how scripting.com still uses http addresses. I could switch over, but then all the images and included files posted before 2014 or so would break. The minor gain in security on a site that doesn't ask for any private information, is totally not worth throwing out all the work I did on a site that actually has historic importance is just a bad deal. It would be a solving a problem no one but Google has (and it's not even clear what that problem is, and why I should care). There's a principle here too — letting one company dictate to us how the web works, well I got into the web to get away from that.

Anyway, the reason they still use http in a place where one expects https is apparently is the same reason. It would break things that they don't want to break. I'm not suggesting they change it, but somewhere in my codebase somehow the http addresses are getting converted to https, and I haven't (yet) been able to track it down. I'm pretty sure it's a bug I unknowingly introduced.

PS: When I'm calling through the API, I get back a record that has a different guid from what's in the feed. Seems like the API and the feed should be in agreement. This is the code that gets the post record. My guess to get them into agreement, I'm going to have to hack this, changing https to http. And there is the reason they can't fix this, and just have to live with this mess. I think overall the people who manage the feed and the API are doing a pretty great job, btw. You have to know I wouldn't say that if I didn't believe it.

PPS: I reported the problem once it was fully diagnosed, on the WordPress repo for Calypso.

Thinking of AI and how it relates to software development, I'm working in the old mode and the new mode. The old mode is I build a project over a few years. I try to bury bits of functionality behind interfaces, either APIs or UIs, and hope I can forget how they work and just access them via the interfaces. Repeat the process. In the new mode, I rely on the machine to remember all that. Claude Code is the key to doing that, using a GitHub repo. And then two or more people can work at the higher level. Obviously the next thing is to see if there aren't some interfaces we can build that are even higher level. The evolution of AI and languages go hand in hand. On the other hand, human beings being what we are, it's just as likely as there will be a wild proliferation of new even more complex interfaces, because now we can rely on the machines to remember the complexities, and their limit is, compared to humans, practically infinite.

Just added Daring Fireball to my blogroll. What a huge oversight. Glad to get this fixed. #

Substack would be the web's printer, if they supported inbound RSS. #