I was going to tell you how much I like the Lever podcast, and wanted to recommend it, but they make it impossible to find the RSS url for the feed. The usual hacks don't seem to work. Since I'm subscribed to it on Pocket Casts, I thought I might be able to find the URL on their web interface, and it's possible I might have found it that way. Nope. It just points to the web page for the podcast, which did not have the RSS feed. I know they must have one. I was looking for a way to download my OPML file, would be nice if you could do it from the desktop.

We ought to be thinking about a filtering system for feed readers based on loose instructions written by users, and shared on the web, to be parsed by our AI. Design your personal algorithm with AI. Share the good ones with your friends, and have it work on the web, in any feed reader. There are ways to do that.

Spoilers follow. Like Doc, I have trouble getting into TV series, but not Pluribus, probably because it came from the showrunner of Breaking Bad and Better Call Saul, two series that I have watched from beginning to end at least three times. The star of Pluribus, Rhea Seaho...

Interesting thought with a small Pluribus spoiler. We should all think of our AI pseudo-people with as much disdain as Carol has for the "people" who watch over her. They aren't people, in either case. In Pluribus they give you the hint in everything they say. It's not "I think this" it's "we think this." I'd like my chatbot friends to use similar language. Never behave like a person. That should be as forbidden. We'll regret not controlling this, I think.

With any luck this will be the last of the tests for this particular feature. If this continues to work, tomorrow or Monday I'll switch it over to cross-posting to daveverse instead of the throw-away test site. Below are the debugging messages I used today. Nothing really ...

How did the regression test go? Wellll, I did break a bunch of stuff. But I put the pieces back in place. And with any luck this post will show up on the other end. It did.

I have been thinking, for years now, why not reconceive the discourse system on the social web to factor out moderation. It is the web, so anyone can add a feature any time without having to rewrite the whole web. I've been trying ideas out for years, but everyone preferred the silos. Hoping now at least there are enough people to start a bootstrap. Won't be much of a discourse system if people don't course.

Today's song: Folsom Prison Blues.

Tim Bray did an analysis of how the Sarah Kendzior suspension on Bluesky would have played out in the Mastodon world. The thing I keep thinking of is this -- why not reconceive the whole discourse system on the social web to factor out moderation. Something a lot less contentious. That's what I hope to be using soon. That's, finally, what I am working on now.

This is one of those days I am pretty sure I have nothing to write about but as I get going I'll remember stuff to write about.

Now I have the other half of the bridge working. This post is full of the testing I did on this, and yes it all worked. I'm going to post something new and see if it makes it through to the other side. And you get to see if it works or not. And now I'm going to make a change. Having made the change I want to see if it made it through. It's kind of remarkable to me that I got this much done in one day. That's what happens when you invested in good tools. And this is where the changes have been visible, on a scratch site used just for these occasions. Tomorrow, the third day of this project, I clean up the loose ends and then we should be good to go with the posts I make on scripting showing up in daveverse. Then I can get started with the next project that depends on this.

I absolutely love Pluribus, but it has the hardest freaking name to remember. I love stories like this, with new assumptions about what is, and people coping with what may or may not be great, or boring, or who knows what. I know they've got me thinking about it all the time, and that is what I like in a good televised story.

It's kind of weird for me to be hanging out around WordPress, but I like it. They've been very welcoming. It's kind of like I imagine it would be for Ward Cunningham to be working with Wikipedia. It may not have been everything he wanted from wiki's but it might be the best ...

Some pre-dinner testing. That was correctly recognized as a new item.

Here's what I'm doing. I want to get all my blog posts together in one place. I still want to use Electric Drummer to write stuff for scripting.com, there's a whole system built around it being where it is. But, I want all the posts on scripting to also appear on the daveverse site, so that they first version of my discourse module can be simple to create, debug and use. So I've got the first half working, I've got a script that hooks in via WebSockets to FeedLand and is notified every time Scripting News updates. It mirrors the updates to a site on WordPress (for testing) and once it works, I'll have it send the stuff to Daveverse. That part remains to be done. Not sure if it'll be a desktop app or a server-based app. But now I need a break. ;-)

One more before lunch.

The hits keep comin! ;-)

As promised here is another test post. I will now add another sentence to the post...

You will probably see a series of test posts here, as the day goes on.

Good morning. I like how things are going in FeedLand and WordLand today. The dots are starting to connect.

A short podcast about Sarah Kendzior, Johnny Cash and Bluesky.

I've added the NetNewsWire blog to my blogroll.

The big news is that there are now docs for source:markdown. The goal is to have a writer-friendly standard for text on the net that's as useful as the one for audio was. We've never had that for RSS. As with everything in RSS-land, cooperation among the different vendors was never its strong point. I hope to change that, and plan to build a network for written text as open and powerful as the one that developed for podcasting.

Fixed a longstanding performance bug on the scripting.com home page. Sometimes it'd just sit there for five seconds. Really embarrassing. It might feel faster now. Still diggin!

New developer notes for source:markdown. Report problems here.

As part of the process I reviewed the developer notes I posted in 2022. I see why there was confusion, it was so early in the process. I'm replacing those developer notes with new ones, that's based on more practical experience.

An example feed that has lots of source namespace elements.

Today I'm going to work on re-shaping the docs for source:markdown because it seems to becoming a thing that people are supporting in their feeds and in their feed consumer apps. We're going to have discuss how it's supported, on both ends. What goes into a source:markdown element, and what does not, and how should readers use it. I will assume the role of benevolent dictator, as I did with RSS 2.0, with a bit more of an understanding of what's important. See Rule #1 in Rules for Standards-makers. "The only reason we have open formats and protocols is so our software can interoperate." And the Rule of Users: "People choose to interop because it helps them find new users. If you have no users to offer, there won't be much interest in interop."

BTW, if you have a question about source:markdown, or want to raise an issue, this is the place to do it.

Scripting News' feed now supports source:markdown.