RSS/Atom Feed Analyzer
Analysis of http://scripting.com/rss.xml
Feed fetched in 288 ms.
Content type is text/xml.
Feed is 172,637 characters long.
Feed has an ETag of "a146338d9be64ef36527b3e4619b09a0".
Feed has a last modified date of Wed, 29 Jul 2026 17:15:30 GMT.
Feed is well-formed XML.
Warning Feed has no styling.
This is an RSS feed.
Feed title: Scripting News
Warning Feed is missing a self link.
Feed has an image at https://imgs.scripting.com/2025/06/04/curly.png.
Feed has 50 items.
First item published on 2026-07-29T16:27:58.000Z
Last item published on 2026-07-16T22:20:32.000Z
All items have published dates.
Newest item was published on 2026-07-29T17:08:22.000Z.
Info Feed's Last-Modified date is newer than the newest item's published date (2026-07-29T17:15:30.000Z > 2026-07-29T17:08:22.000Z).
Home page URL: http://scripting.com/
Home page has feed discovery link in <head>.
Error Home page does not have a link to the feed in the <body>.
Formatted XML
<?xml version="1.0" encoding="UTF-8"?>
<!-- RSS generated by oldSchool v0.8.16 on Wed, 29 Jul 2026 17:15:29 GMT -->
<rss version="2.0" xmlns:source="https://source.scripting.com/">
<channel>
<title>Scripting News</title>
<link>http://scripting.com/</link>
<description>Dave Winer, OG blogger, podcaster, developed first apps in many categories. Old enough to know better. It's even worse than it appears.</description>
<pubDate>Wed, 29 Jul 2026 17:08:22 GMT</pubDate>
<language>en-us</language>
<generator>oldSchool v0.8.16</generator>
<copyright>&copy; copyright 1994-2026 Dave Winer.</copyright>
<docs>http://cyber.law.harvard.edu/rss/rss.html</docs>
<lastBuildDate>Wed, 29 Jul 2026 17:15:29 GMT</lastBuildDate>
<cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post"/>
<image>
<title>Scripting News</title>
<url>https://imgs.scripting.com/2025/06/04/curly.png</url>
<link>http://scripting.com/</link>
<description>Scripting News gets an image because it's part of a network that uses them. 6/4/25 by DW</description>
</image>
<source:account service="bluesky">@scripting.com</source:account>
<source:account service="mastodon">@davew@mastodon.social</source:account>
<source:account service="twitter">bullmancuso</source:account>
<source:localTime>Wed, July 29, 2026 1:15 PM EDT</source:localTime>
<source:self>http://scripting.com/rss.xml</source:self>
<source:blogroll>https://feedland.social/opml?screenname=davewiner&catname=blogroll</source:blogroll>
<item>
<description>Our <a href="https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml">feed parser</a> is updated to understand the new elements for RSSchat.</description>
<pubDate>Wed, 29 Jul 2026 16:27:58 GMT</pubDate>
<link>http://scripting.com/2026/07/29.html#a162758</link>
<guid>http://scripting.com/2026/07/29.html#a162758</guid>
<source:markdown>Our [feed parser](https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml) is updated to understand the new elements for RSSchat.</source:markdown>
<source:outline text="Our <a href="https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml">feed parser</a> is updated to understand the new elements for RSSchat." created="Wed, 29 Jul 2026 16:27:58 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/29.html#a162758"/>
</item>
<item>
<description>I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web. </description>
<pubDate>Wed, 29 Jul 2026 14:04:37 GMT</pubDate>
<link>http://scripting.com/2026/07/29.html#a140437</link>
<guid>http://scripting.com/2026/07/29.html#a140437</guid>
<source:markdown>I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web.</source:markdown>
<source:outline text="I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web. " created="Wed, 29 Jul 2026 14:04:37 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/29.html#a140437"/>
</item>
<item>
<title>Learnings from Andy Hertzfeld</title>
<description><p>Listened to this <a href="https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels">podcast interview</a> with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too.</p> <p>His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden:</p> <ol> <li>you have time to try out every idea because it's free and fast.</li> <li>you have time to work on interop, building bridges between your software and other people's.</li> <li>a very long list of other things you can do that one person could never do before. </li> </ol> <p>Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers). </p> <p>I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night.</p> <p>In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this.</p> <p>This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one. </p> <p>The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else.</p> <p>There's never been a leap in tech anything like this in my life. </p> <p>How could Andy Hertzfeld knowing all that which I'm sure he does, not use it?</p> <p>Also -- I didn't know <a href="https://daytona.scripting.com/search?q=JLG">JLG</a> wanted to kill <a href="https://daytona.scripting.com/search?q=hypercard">Hypercard</a>, but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP. </p> <p>It's fascinating to hear his story. </p> </description>
<pubDate>Wed, 29 Jul 2026 17:08:22 GMT</pubDate>
<link>http://scripting.com/2026/07/29/170822.html?title=learningsFromAndyHertzfeld</link>
<guid>http://scripting.com/2026/07/29/170822.html</guid>
<source:markdown>Listened to this [podcast interview](https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels) with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too. His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden: 1. you have time to try out every idea because it's free and fast. 2. you have time to work on interop, building bridges between your software and other people's. 3. a very long list of other things you can do that one person could never do before. Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers). I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night. In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this. This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one. The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else. There's never been a leap in tech anything like this in my life. How could Andy Hertzfeld knowing all that which I'm sure he does, not use it? Also -- I didn't know [JLG](https://daytona.scripting.com/search?q=JLG) wanted to kill [Hypercard](https://daytona.scripting.com/search?q=hypercard), but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP. It's fascinating to hear his story.</source:markdown>
<source:outline text="Learnings from Andy Hertzfeld" created="Wed, 29 Jul 2026 17:08:22 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html">
<source:outline text="Listened to this <a href="https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels">podcast interview</a> with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too." created="Wed, 29 Jul 2026 17:08:38 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170838"/>
<source:outline text="His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden:" created="Wed, 29 Jul 2026 17:09:17 GMT" flNumberedSubs="true" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170917">
<source:outline text="you have time to try out every idea because it's free and fast." created="Wed, 29 Jul 2026 17:09:18 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170918"/>
<source:outline text="you have time to work on interop, building bridges between your software and other people's." created="Wed, 29 Jul 2026 17:09:28 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170928"/>
<source:outline text="a very long list of other things you can do that one person could never do before." created="Wed, 29 Jul 2026 17:09:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170919"/>
</source:outline>
<source:outline text="Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers)." created="Wed, 29 Jul 2026 17:09:58 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170958"/>
<source:outline text="I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night." created="Wed, 29 Jul 2026 17:12:03 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171203"/>
<source:outline text="In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this." created="Wed, 29 Jul 2026 17:12:22 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171222"/>
<source:outline text="This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one." created="Wed, 29 Jul 2026 17:12:51 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171251"/>
<source:outline text="The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else." created="Wed, 29 Jul 2026 17:13:09 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171309"/>
<source:outline text="There's never been a leap in tech anything like this in my life." created="Wed, 29 Jul 2026 17:13:47 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171347"/>
<source:outline text="How could Andy Hertzfeld knowing all that which I'm sure he does, not use it?" created="Wed, 29 Jul 2026 17:13:51 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171351"/>
<source:outline text="Also -- I didn't know <a href="https://daytona.scripting.com/search?q=JLG">JLG</a> wanted to kill <a href="https://daytona.scripting.com/search?q=hypercard">Hypercard</a>, but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP." created="Wed, 29 Jul 2026 17:11:04 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171104"/>
<source:outline text="It's fascinating to hear his story." created="Wed, 29 Jul 2026 17:10:07 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171007"/>
</source:outline>
</item>
<item>
<title>When the walls came down</title>
<description><p>Yesterday's <a href="http://scripting.com/2026/07/27.html">Scripting News</a> was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in <a href="http://scripting.com/2002/09.html">September 2002</a>. If you look at what's there, a post about re-opening the <a href="https://github.com/scripting/frontierOdb">Frontier object database</a> format would be considered the top item on any other day, but it's the last of the untitled posts for the day. </p> <p>At the <a href="http://scripting.com/2026/07/27.html#a181535">top of the page</a>, a surprise that <a href="https://pfefferle.dev/">Matthias Pfefferle</a> at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto. </p> <p>Look at what we've done. I stress <i>we. </i>Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely. </p> <p>Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web.</p> <p>Anyway, now we've got half of the <a href="http://scripting.com/2026/07/27/134952.html">big picture</a> working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about <a href="http://scripting.com/2026/07/27/134952.html">how I see the network evolving</a>. I predict, if this bootstrap works, we will come back here in a year and say things like "If he only knew." But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it. </p> <p>I'm proud that I have a record of <a href="http://scripting.com/2002/09.html">September 2002</a> for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-) </p> <p>And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as <a href="https://cyber.harvard.edu/rss/rss.html">specified</a> in 2003, even using one of the <a href="https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt">elements</a> that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. I've accumulated all the extensions I use in my software since the early teens in the <a href="https://source.scripting.com/">source namespace</a>. And that's where the <a href="https://source.scripting.com/social.opml">new stuff</a> went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible.</p> <p>I played with a lot of names while <a href="https://this.how/rsschat/">RSS.chat</a> was in development but decided the name had to be RSS.something. It deserves a lot more <a href="https://rss.chat/?id=426">love</a> than it has gotten from the tech world. I don't want to hide it, I want it to get a victory <a href="https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought">parade</a> like the one the <a href="https://daytona.scripting.com/search?q=knicks">Knicks</a> got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006.</p> <p>Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go. </p> <p>Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud. </p> <p>I thought my career was winding down, but now it feels like it's just getting started.</p> <p>Reminded of a great quote in <a href="https://en.wikipedia.org/wiki/The_Godfather_Part_III">Godfather III</a>, <a href="https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s">Michael Corleone says</a>: "Just when I thought I was out, they pull me back in."</p> <p>Here we go!</p> <p>PS: A new <a href="https://this.how/rsschat/">this.how page</a> for RSS.chat. It has a little directory to the big spots you might want. </p> </description>
<pubDate>Tue, 28 Jul 2026 11:59:45 GMT</pubDate>
<link>http://scripting.com/2026/07/28/115945.html?title=whenTheWallsCameDown</link>
<guid>http://scripting.com/2026/07/28/115945.html</guid>
<source:markdown>Yesterday's [Scripting News](http://scripting.com/2026/07/27.html) was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in [September 2002](http://scripting.com/2002/09.html). If you look at what's there, a post about re-opening the [Frontier object database](https://github.com/scripting/frontierOdb) format would be considered the top item on any other day, but it's the last of the untitled posts for the day. At the [top of the page](http://scripting.com/2026/07/27.html#a181535), a surprise that [Matthias Pfefferle](https://pfefferle.dev/) at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto. Look at what we've done. I stress _we._ Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely. Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web. Anyway, now we've got half of the [big picture](http://scripting.com/2026/07/27/134952.html) working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about [how I see the network evolving](http://scripting.com/2026/07/27/134952.html). I predict, if this bootstrap works, we will come back here in a year and say things like "If he only knew." But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it. I'm proud that I have a record of [September 2002](http://scripting.com/2002/09.html) for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-) And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as [specified](https://cyber.harvard.edu/rss/rss.html) in 2003, even using one of the [elements](https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt) that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is [extensible](https://cyber.harvard.edu/rss/rss.html#extendingRss). I've accumulated all the extensions I use in my software since the early teens in the [source namespace](https://source.scripting.com/). And that's where the [new stuff](https://source.scripting.com/social.opml) went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible. I played with a lot of names while [RSS.chat](https://this.how/rsschat/) was in development but decided the name had to be RSS.something. It deserves a lot more [love](https://rss.chat/?id=426) than it has gotten from the tech world. I don't want to hide it, I want it to get a victory [parade](https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought) like the one the [Knicks](https://daytona.scripting.com/search?q=knicks) got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006. Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go. Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud. I thought my career was winding down, but now it feels like it's just getting started. Reminded of a great quote in [Godfather III](https://en.wikipedia.org/wiki/The_Godfather_Part_III), [Michael Corleone says](https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s): "Just when I thought I was out, they pull me back in." Here we go! PS: A new [this.how page](https://this.how/rsschat/) for RSS.chat. It has a little directory to the big spots you might want.</source:markdown>
<source:outline text="When the walls came down" created="Tue, 28 Jul 2026 11:59:45 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html">
<source:outline text="Yesterday's <a href="http://scripting.com/2026/07/27.html">Scripting News</a> was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in <a href="http://scripting.com/2002/09.html">September 2002</a>. If you look at what's there, a post about re-opening the <a href="https://github.com/scripting/frontierOdb">Frontier object database</a> format would be considered the top item on any other day, but it's the last of the untitled posts for the day." created="Tue, 28 Jul 2026 11:50:37 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a115037"/>
<source:outline text="At the <a href="http://scripting.com/2026/07/27.html#a181535">top of the page</a>, a surprise that <a href="https://pfefferle.dev/">Matthias Pfefferle</a> at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto." created="Tue, 28 Jul 2026 12:13:31 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121331"/>
<source:outline text="Look at what we've done. I stress <i>we. </i>Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely." created="Tue, 28 Jul 2026 12:33:02 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a123302"/>
<source:outline text="Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web." created="Tue, 28 Jul 2026 12:15:35 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121535"/>
<source:outline text="Anyway, now we've got half of the <a href="http://scripting.com/2026/07/27/134952.html">big picture</a> working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about <a href="http://scripting.com/2026/07/27/134952.html">how I see the network evolving</a>. I predict, if this bootstrap works, we will come back here in a year and say things like "If he only knew." But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it." created="Tue, 28 Jul 2026 11:58:53 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a115853"/>
<source:outline text="I'm proud that I have a record of <a href="http://scripting.com/2002/09.html">September 2002</a> for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-)" created="Tue, 28 Jul 2026 12:17:01 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121701"/>
<source:outline text="And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as <a href="https://cyber.harvard.edu/rss/rss.html">specified</a> in 2003, even using one of the <a href="https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt">elements</a> that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. I've accumulated all the extensions I use in my software since the early teens in the <a href="https://source.scripting.com/">source namespace</a>. And that's where the <a href="https://source.scripting.com/social.opml">new stuff</a> went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible." created="Tue, 28 Jul 2026 12:04:27 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120427"/>
<source:outline text="I played with a lot of names while <a href="https://this.how/rsschat/">RSS.chat</a> was in development but decided the name had to be RSS.something. It deserves a lot more <a href="https://rss.chat/?id=426">love</a> than it has gotten from the tech world. I don't want to hide it, I want it to get a victory <a href="https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought">parade</a> like the one the <a href="https://daytona.scripting.com/search?q=knicks">Knicks</a> got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006." created="Tue, 28 Jul 2026 12:19:51 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121951"/>
<source:outline text="Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go." created="Tue, 28 Jul 2026 11:59:12 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a115912"/>
<source:outline text="Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud." created="Tue, 28 Jul 2026 12:07:36 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120736"/>
<source:outline text="I thought my career was winding down, but now it feels like it's just getting started." created="Tue, 28 Jul 2026 12:08:41 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120841"/>
<source:outline text="Reminded of a great quote in <a href="https://en.wikipedia.org/wiki/The_Godfather_Part_III">Godfather III</a>, <a href="https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s">Michael Corleone says</a>: "Just when I thought I was out, they pull me back in."" created="Tue, 28 Jul 2026 12:08:54 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120854"/>
<source:outline text="Here we go!" created="Tue, 28 Jul 2026 12:08:39 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120839"/>
<source:outline text="PS: A new <a href="https://this.how/rsschat/">this.how page</a> for RSS.chat. It has a little directory to the big spots you might want." created="Tue, 28 Jul 2026 17:53:23 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a175323"/>
</source:outline>
</item>
<item>
<description><a href="https://github.com/pfefferle/wordpress-rss-chat">This is something</a>. WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his <a href="https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/">podcast</a> last year. If people use this connection and see how it works, then we'll get an idea of where to go next.</description>
<pubDate>Mon, 27 Jul 2026 18:15:35 GMT</pubDate>
<link>http://scripting.com/2026/07/27.html#a181535</link>
<guid>http://scripting.com/2026/07/27.html#a181535</guid>
<source:markdown>[This is something](https://github.com/pfefferle/wordpress-rss-chat). WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his [podcast](https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/) last year. If people use this connection and see how it works, then we'll get an idea of where to go next.</source:markdown>
<source:outline text="<a href="https://github.com/pfefferle/wordpress-rss-chat">This is something</a>. WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his <a href="https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/">podcast</a> last year. If people use this connection and see how it works, then we'll get an idea of where to go next." created="Mon, 27 Jul 2026 18:15:35 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a181535"/>
</item>
<item>
<description>BTW, I had no idea the WordPress connection was coming and here it is.</description>
<pubDate>Mon, 27 Jul 2026 21:41:57 GMT</pubDate>
<link>http://scripting.com/2026/07/27.html#a214157</link>
<guid>http://scripting.com/2026/07/27.html#a214157</guid>
<source:markdown>BTW, I had no idea the WordPress connection was coming and here it is.</source:markdown>
<source:outline text="BTW, I had no idea the WordPress connection was coming and here it is." created="Mon, 27 Jul 2026 21:41:57 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a214157"/>
</item>
<item>
<description>Of course we have a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> for RSS.chat updates.</description>
<pubDate>Mon, 27 Jul 2026 17:46:32 GMT</pubDate>
<link>http://scripting.com/2026/07/27.html#a174632</link>
<guid>http://scripting.com/2026/07/27.html#a174632</guid>
<source:markdown>Of course we have a [feed](https://news.rss.chat/worknotes/rss.xml) for RSS.chat updates.</source:markdown>
<source:outline text="Of course we have a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> for RSS.chat updates." created="Mon, 27 Jul 2026 17:46:32 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a174632"/>
</item>
<item>
<description><img class="imgRightMargin" src="https://imgs.scripting.com/2021/06/14/strongman.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;"><a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">How we document APIs</a>. We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">doc</a>. I have a vested interest, in my job I read a lot of bad API docs.</description>
<pubDate>Mon, 27 Jul 2026 16:33:10 GMT</pubDate>
<link>http://scripting.com/2026/07/27.html#a163310</link>
<guid>http://scripting.com/2026/07/27.html#a163310</guid>
<source:markdown>[How we document APIs](https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md). We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this [doc](https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md). I have a vested interest, in my job I read a lot of bad API docs.</source:markdown>
<source:outline text="<a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">How we document APIs</a>. We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">doc</a>. I have a vested interest, in my job I read a lot of bad API docs." created="Mon, 27 Jul 2026 16:33:10 GMT" type="outline" image="https://imgs.scripting.com/2021/06/14/strongman.png" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a163310"/>
</item>
<item>
<description><a href="https://github.com/scripting/frontierOdb">A new utility</a> exports the contents of a Frontier <a href="https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132">object database</a> into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it.</description>
<pubDate>Mon, 27 Jul 2026 13:26:10 GMT</pubDate>
<link>http://scripting.com/2026/07/27.html#a132610</link>
<guid>http://scripting.com/2026/07/27.html#a132610</guid>
<source:markdown>[A new utility](https://github.com/scripting/frontierOdb) exports the contents of a Frontier [object database](https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132) into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it.</source:markdown>
<source:outline text="<a href="https://github.com/scripting/frontierOdb">A new utility</a> exports the contents of a Frontier <a href="https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132">object database</a> into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it." created="Mon, 27 Jul 2026 13:26:10 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a132610"/>
</item>
<item>
<title>How I see the network evolving</title>
<description><p>A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt. </p> <p>The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them. </p> <p>RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation. </p> <p>"Small pieces loosely joined" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily. </p> <p>Just to be sure everyone understands -- I already have such an app, called <a href="https://docs.feedland.com/gettingstarted.md">FeedLand</a>. You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start. </p> <p>FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature. </p> <p>We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures. </p> <p>I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play. </p> </description>
<pubDate>Mon, 27 Jul 2026 13:49:52 GMT</pubDate>
<link>http://scripting.com/2026/07/27/134952.html?title=howISeeTheNetworkEvolving</link>
<guid>http://scripting.com/2026/07/27/134952.html</guid>
<source:markdown>A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt. The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them. RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation. "Small pieces loosely joined" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily. Just to be sure everyone understands -- I already have such an app, called [FeedLand](https://docs.feedland.com/gettingstarted.md). You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start. FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature. We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures. I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play.</source:markdown>
<source:outline text="How I see the network evolving" created="Mon, 27 Jul 2026 13:49:52 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html">
<source:outline text="A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt." created="Mon, 27 Jul 2026 13:39:18 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a133918"/>
<source:outline text="The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them." created="Mon, 27 Jul 2026 13:50:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135019"/>
<source:outline text="RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation." created="Mon, 27 Jul 2026 13:50:29 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135029"/>
<source:outline text=""Small pieces loosely joined" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily." created="Mon, 27 Jul 2026 13:55:09 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135509"/>
<source:outline text="Just to be sure everyone understands -- I already have such an app, called <a href="https://docs.feedland.com/gettingstarted.md">FeedLand</a>. You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start." created="Mon, 27 Jul 2026 13:56:57 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135657"/>
<source:outline text="FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature." created="Mon, 27 Jul 2026 14:00:03 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a140003"/>
<source:outline text="We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures." created="Mon, 27 Jul 2026 13:51:29 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135129"/>
<source:outline text="I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play." created="Mon, 27 Jul 2026 14:02:44 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a140244"/>
</source:outline>
</item>
<item>
<description><a href="https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md">New docs for</a> the browser JavaScript interface to the RSS.chat API.</description>
<pubDate>Sun, 26 Jul 2026 15:37:08 GMT</pubDate>
<link>http://scripting.com/2026/07/26.html#a153708</link>
<guid>http://scripting.com/2026/07/26.html#a153708</guid>
<source:markdown>[New docs for](https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md) the browser JavaScript interface to the RSS.chat API.</source:markdown>
<source:outline text="<a href="https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md">New docs for</a> the browser JavaScript interface to the RSS.chat API." created="Sun, 26 Jul 2026 15:37:08 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a153708"/>
</item>
<item>
<description>Scott Hanson has a new <a href="https://github.com/scotthansonde/rsschat-wordpress-service">service</a> that connects <a href="https://this.how/rsschat/">RSS.chat</a> to WordPress.</description>
<pubDate>Sun, 26 Jul 2026 13:50:50 GMT</pubDate>
<link>http://scripting.com/2026/07/26.html#a135050</link>
<guid>http://scripting.com/2026/07/26.html#a135050</guid>
<source:markdown>Scott Hanson has a new [service](https://github.com/scotthansonde/rsschat-wordpress-service) that connects [RSS.chat](https://this.how/rsschat/) to WordPress.</source:markdown>
<source:outline text="Scott Hanson has a new <a href="https://github.com/scotthansonde/rsschat-wordpress-service">service</a> that connects <a href="https://this.how/rsschat/">RSS.chat</a> to WordPress." created="Sun, 26 Jul 2026 13:50:50 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a135050"/>
</item>
<item>
<description>Many of the questions about <a href="https://this.how/rsschat/">RSS.chat</a> center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.</description>
<pubDate>Sun, 26 Jul 2026 20:19:51 GMT</pubDate>
<link>http://scripting.com/2026/07/26.html#a201951</link>
<guid>http://scripting.com/2026/07/26.html#a201951</guid>
<source:markdown>Many of the questions about [RSS.chat](https://this.how/rsschat/) center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.</source:markdown>
<source:outline text="Many of the questions about <a href="https://this.how/rsschat/">RSS.chat</a> center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even." created="Sun, 26 Jul 2026 20:19:51 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a201951"/>
</item>
<item>
<description>A note to people who run <a href="https://us.wordcamp.org/2026/">WordCamp</a> conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program.</description>
<pubDate>Sun, 26 Jul 2026 13:20:17 GMT</pubDate>
<link>http://scripting.com/2026/07/26.html#a132017</link>
<guid>http://scripting.com/2026/07/26.html#a132017</guid>
<source:markdown>A note to people who run [WordCamp](https://us.wordcamp.org/2026/) conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program.</source:markdown>
<source:outline text="A note to people who run <a href="https://us.wordcamp.org/2026/">WordCamp</a> conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program." created="Sun, 26 Jul 2026 13:20:17 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a132017"/>
</item>
<item>
<title>rss.chat isn't really a product</title>
<description><p>It's what we used to call a <a href="https://daytona.scripting.com/search?q=%22coral%20reef%22">coral reef</a>. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to <i>serve</i> them. </p> <p>This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this <a href="https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523">in a comment</a> in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.</p> </description>
<pubDate>Sun, 26 Jul 2026 13:53:07 GMT</pubDate>
<link>http://scripting.com/2026/07/26/135307.html?title=rsschatIsntReallyAProduct</link>
<guid>http://scripting.com/2026/07/26/135307.html</guid>
<source:markdown>It's what we used to call a [coral reef](https://daytona.scripting.com/search?q=%22coral%20reef%22). A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to _serve_ them. This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this [in a comment](https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523) in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is [extensible](https://cyber.harvard.edu/rss/rss.html#extendingRss). It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.</source:markdown>
<source:outline text="rss.chat isn't really a product" created="Sun, 26 Jul 2026 13:53:07 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26/135307.html">
<source:outline text="It's what we used to call a <a href="https://daytona.scripting.com/search?q=%22coral%20reef%22">coral reef</a>. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to <i>serve</i> them." created="Sun, 26 Jul 2026 13:53:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/135307.html#a135319"/>
<source:outline text="This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this <a href="https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523">in a comment</a> in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd." created="Sun, 26 Jul 2026 13:53:26 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/135307.html#a135326"/>
</source:outline>
</item>
<item>
<title>Confession: I still drive a Tesla.</title>
<description><p>Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed. </p> <ol> <li>Backed into a charging station.</li> <li>An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel.</li> <li>My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look. </li> <li>A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup.</li> </ol> <p>I don't know if it accomplishes anything but to me it feels like retribution of a sort. </p> </description>
<pubDate>Sun, 26 Jul 2026 20:12:20 GMT</pubDate>
<link>http://scripting.com/2026/07/26/201220.html?title=confessionIStillDriveATesla</link>
<guid>http://scripting.com/2026/07/26/201220.html</guid>
<source:markdown>Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed. 1. Backed into a charging station. 2. An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel. 3. My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look. 4. A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup. I don't know if it accomplishes anything but to me it feels like retribution of a sort.</source:markdown>
<source:outline text="Confession: I still drive a Tesla." created="Sun, 26 Jul 2026 20:12:20 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html">
<source:outline text="Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed." created="Sun, 26 Jul 2026 20:12:38 GMT" flNumberedSubs="true" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201238">
<source:outline text="Backed into a charging station." created="Sun, 26 Jul 2026 20:12:47 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201247"/>
<source:outline text="An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel." created="Sun, 26 Jul 2026 20:12:57 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201257"/>
<source:outline text="My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look." created="Sun, 26 Jul 2026 20:13:09 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201309"/>
<source:outline text="A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup." created="Sun, 26 Jul 2026 20:12:48 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201248"/>
</source:outline>
<source:outline text="I don't know if it accomplishes anything but to me it feels like retribution of a sort." created="Sun, 26 Jul 2026 20:12:31 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201231"/>
</source:outline>
</item>
<item>
<description><img class="imgRightMargin" src="https://imgs.scripting.com/2023/11/30/goodhumortruck.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor.</description>
<pubDate>Sat, 25 Jul 2026 12:43:05 GMT</pubDate>
<link>http://scripting.com/2026/07/25.html#a124305</link>
<guid>http://scripting.com/2026/07/25.html#a124305</guid>
<source:markdown>How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor.</source:markdown>
<source:outline text="How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor." created="Sat, 25 Jul 2026 12:43:05 GMT" type="outline" image="https://imgs.scripting.com/2023/11/30/goodhumortruck.png" flInCalendar="true" permalink="http://scripting.com/2026/07/25.html#a124305"/>
</item>
<item>
<description>Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there.</description>
<pubDate>Sat, 25 Jul 2026 14:25:11 GMT</pubDate>
<link>http://scripting.com/2026/07/25.html#a142511</link>
<guid>http://scripting.com/2026/07/25.html#a142511</guid>
<source:markdown>Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there.</source:markdown>
<source:outline text="Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there." created="Sat, 25 Jul 2026 14:25:11 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/25.html#a142511"/>
</item>
<item>
<title>RSS.chat has an API</title>
<description><p>It's a standard REST API.</p> <p>Here's the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037">server side</a> of the API. </p> <p>Here's how you call it from <a href="https://github.com/scripting/rss.chat/blob/main/client/code/api.js">browser-based JavaScript</a>. You can include that code in your apps.</p> <p>Here's an <a href="https://github.com/scripting/rss.chat/tree/main/examples/easyblogger">example app</a> that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-)</p> <p>And finally here are the <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/api.md">docs</a> for the API itself. </p> </description>
<pubDate>Sat, 25 Jul 2026 14:12:53 GMT</pubDate>
<link>http://scripting.com/2026/07/25/141253.html?title=rsschatHasAnApi</link>
<guid>http://scripting.com/2026/07/25/141253.html</guid>
<source:markdown>It's a standard REST API. Here's the [server side](https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037) of the API. Here's how you call it from [browser-based JavaScript](https://github.com/scripting/rss.chat/blob/main/client/code/api.js). You can include that code in your apps. Here's an [example app](https://github.com/scripting/rss.chat/tree/main/examples/easyblogger) that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-) And finally here are the [docs](https://github.com/scripting/rss.chat/blob/main/server/docs/api.md) for the API itself.</source:markdown>
<source:outline text="RSS.chat has an API" created="Sat, 25 Jul 2026 14:12:53 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html">
<source:outline text="It's a standard REST API." created="Sat, 25 Jul 2026 14:13:02 GMT" flBulletedSubs="true" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141302"/>
<source:outline text="Here's the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037">server side</a> of the API." created="Sat, 25 Jul 2026 14:13:22 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141322"/>
<source:outline text="Here's how you call it from <a href="https://github.com/scripting/rss.chat/blob/main/client/code/api.js">browser-based JavaScript</a>. You can include that code in your apps." created="Sat, 25 Jul 2026 14:15:17 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141517"/>
<source:outline text="Here's an <a href="https://github.com/scripting/rss.chat/tree/main/examples/easyblogger">example app</a> that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-)" created="Sat, 25 Jul 2026 14:16:23 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141623"/>
<source:outline text="And finally here are the <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/api.md">docs</a> for the API itself." created="Sat, 25 Jul 2026 14:17:46 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141746"/>
</source:outline>
</item>
<item>
<description>RSS.chat worknotes are a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> now. Updated when there's a new feature or fix. Same info is on the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">worknotes</a> <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">pages</a> in the <a href="https://github.com/scripting/rss.chat">repo</a>.</description>
<pubDate>Fri, 24 Jul 2026 16:43:13 GMT</pubDate>
<link>http://scripting.com/2026/07/24.html#a164313</link>
<guid>http://scripting.com/2026/07/24.html#a164313</guid>
<source:markdown>RSS.chat worknotes are a [feed](https://news.rss.chat/worknotes/rss.xml) now. Updated when there's a new feature or fix. Same info is on the [worknotes](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md) [pages](https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md) in the [repo](https://github.com/scripting/rss.chat).</source:markdown>
<source:outline text="RSS.chat worknotes are a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> now. Updated when there's a new feature or fix. Same info is on the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">worknotes</a> <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">pages</a> in the <a href="https://github.com/scripting/rss.chat">repo</a>." created="Fri, 24 Jul 2026 16:43:13 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/24.html#a164313"/>
</item>
<item>
<title>Dear podcast client devs</title>
<description><p>Podcast client developers -- don't give up like <a href="https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying">this guy</a> did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do. </p> <p><b>Subscribable subscription lists</b> would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code. </p> <p>I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others. </p> <p>This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client <i>deserves</i> to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists. </p> <p>Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be <a href="https://www.dictionary.com/browse/overt">overt</a> in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades. </p> <p>It's time to rock the f'ing boat! :-)</p> <p>Podcasting forever! </p> </description>
<pubDate>Fri, 24 Jul 2026 14:01:59 GMT</pubDate>
<link>http://scripting.com/2026/07/24/140159.html?title=dearPodcastClientDevs</link>
<guid>http://scripting.com/2026/07/24/140159.html</guid>
<source:markdown>Podcast client developers -- don't give up like [this guy](https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying) did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do. **Subscribable subscription lists** would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code. I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others. This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client _deserves_ to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists. Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be [overt](https://www.dictionary.com/browse/overt) in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades. It's time to rock the f'ing boat! :-) Podcasting forever!</source:markdown>
<source:outline text="Dear podcast client devs" created="Fri, 24 Jul 2026 14:01:59 GMT" type="outline" description="The big new idea -- subscribable subscription lists." flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html">
<source:outline text="Podcast client developers -- don't give up like <a href="https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying">this guy</a> did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do." created="Fri, 24 Jul 2026 13:33:48 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a133348"/>
<source:outline text="<b>Subscribable subscription lists</b> would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code." created="Fri, 24 Jul 2026 14:10:54 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141054"/>
<source:outline text="I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others." created="Fri, 24 Jul 2026 14:11:27 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141127"/>
<source:outline text="This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client <i>deserves</i> to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists." created="Fri, 24 Jul 2026 14:14:05 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141405"/>
<source:outline text="Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be <a href="https://www.dictionary.com/browse/overt">overt</a> in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades." created="Fri, 24 Jul 2026 14:00:27 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a140027"/>
<source:outline text="It's time to rock the f'ing boat! :-)" created="Fri, 24 Jul 2026 14:16:16 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141616"/>
<source:outline text="Podcasting forever!" created="Fri, 24 Jul 2026 14:16:21 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141621"/>
</source:outline>
</item>
<item>
<description><img class="imgRightMargin" src="https://imgs.scripting.com/2025/09/17/reallySimpleKetchup.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">A new feature on rss.chat, <b>images</b>. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to <a href="https://textcasting.org/">textcasting</a>. It's a feature I needed to be reminded is essential. The first <a href="https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com">browser</a> to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from <a href="https://en.wikipedia.org/wiki/Tim_Berners-Lee">TBL</a>, but it is most definitely a standard feature of the web.</description>
<pubDate>Thu, 23 Jul 2026 15:01:19 GMT</pubDate>
<link>http://scripting.com/2026/07/23.html#a150119</link>
<guid>http://scripting.com/2026/07/23.html#a150119</guid>
<source:markdown>A new feature on rss.chat, **images**. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to [textcasting](https://textcasting.org/). It's a feature I needed to be reminded is essential. The first [browser](https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com) to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from [TBL](https://en.wikipedia.org/wiki/Tim_Berners-Lee), but it is most definitely a standard feature of the web.</source:markdown>
<source:outline text="A new feature on rss.chat, <b>images</b>. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to <a href="https://textcasting.org/">textcasting</a>. It's a feature I needed to be reminded is essential. The first <a href="https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com">browser</a> to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from <a href="https://en.wikipedia.org/wiki/Tim_Berners-Lee">TBL</a>, but it is most definitely a standard feature of the web." created="Thu, 23 Jul 2026 15:01:19 GMT" type="outline" image="https://imgs.scripting.com/2025/09/17/reallySimpleKetchup.png" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a150119"/>
</item>
<item>
<description><a href="https://demo.rss.chat/?id=242">Amyloo</a>, a longtime friend from the early days of podcasting, has made an appearance on <a href="https://demo.rss.chat">demo.rss.chat</a>. So happy to see her. Here's <a href="http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3">one of the bits</a> we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. <span class="spOldSchoolEmoji">😄</span></description>
<pubDate>Thu, 23 Jul 2026 15:14:15 GMT</pubDate>
<link>http://scripting.com/2026/07/23.html#a151415</link>
<guid>http://scripting.com/2026/07/23.html#a151415</guid>
<source:markdown>[Amyloo](https://demo.rss.chat/?id=242), a longtime friend from the early days of podcasting, has made an appearance on [demo.rss.chat](https://demo.rss.chat). So happy to see her. Here's [one of the bits](http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3) we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. 😄</source:markdown>
<source:outline text="<a href="https://demo.rss.chat/?id=242">Amyloo</a>, a longtime friend from the early days of podcasting, has made an appearance on <a href="https://demo.rss.chat">demo.rss.chat</a>. So happy to see her. Here's <a href="http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3">one of the bits</a> we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. <span class="spOldSchoolEmoji">😄</span>" created="Thu, 23 Jul 2026 15:14:15 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a151415"/>
</item>
<item>
<description>Early this morning we got a report of a <b>security issue</b> in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc">follow the instructions</a> and do the update asap.</description>
<pubDate>Thu, 23 Jul 2026 14:49:19 GMT</pubDate>
<link>http://scripting.com/2026/07/23.html#a144919</link>
<guid>http://scripting.com/2026/07/23.html#a144919</guid>
<source:markdown>Early this morning we got a report of a **security issue** in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please [follow the instructions](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc) and do the update asap.</source:markdown>
<source:outline text="Early this morning we got a report of a <b>security issue</b> in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc">follow the instructions</a> and do the update asap." created="Thu, 23 Jul 2026 14:49:19 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a144919"/>
</item>
<item>
<description>Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. <i>Quickly.</i> I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap.</description>
<pubDate>Thu, 23 Jul 2026 13:07:40 GMT</pubDate>
<link>http://scripting.com/2026/07/23.html#a130740</link>
<guid>http://scripting.com/2026/07/23.html#a130740</guid>
<source:markdown>Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. _Quickly._ I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap.</source:markdown>
<source:outline text="Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. <i>Quickly.</i> I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap." created="Thu, 23 Jul 2026 13:07:40 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a130740"/>
</item>
<item>
<description>RSS.chat now supports <a href="https://sqlite.org/">SQLite</a>. Simpler and faster to install. You don't have to host a database, it's now built into the server. Full <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/install.md">instructions</a>. Questions or <a href="https://github.com/scripting/rss.chat/issues/17">issues</a>.</description>
<pubDate>Wed, 22 Jul 2026 13:15:31 GMT</pubDate>
<link>http://scripting.com/2026/07/22.html#a131531</link>
<guid>http://scripting.com/2026/07/22.html#a131531</guid>
<source:markdown>RSS.chat now supports [SQLite](https://sqlite.org/). Simpler and faster to install. You don't have to host a database, it's now built into the server. Full [instructions](https://github.com/scripting/rss.chat/blob/main/server/docs/install.md). Questions or [issues](https://github.com/scripting/rss.chat/issues/17).</source:markdown>
<source:outline text="RSS.chat now supports <a href="https://sqlite.org/">SQLite</a>. Simpler and faster to install. You don't have to host a database, it's now built into the server. Full <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/install.md">instructions</a>. Questions or <a href="https://github.com/scripting/rss.chat/issues/17">issues</a>." created="Wed, 22 Jul 2026 13:15:31 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/22.html#a131531"/>
</item>
<item>
<description>Reminder: We have a demo <a href="https://demo.rss.chat/">server</a> for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching.</description>
<pubDate>Wed, 22 Jul 2026 12:45:34 GMT</pubDate>
<link>http://scripting.com/2026/07/22.html#a124534</link>
<guid>http://scripting.com/2026/07/22.html#a124534</guid>
<source:markdown>Reminder: We have a demo [server](https://demo.rss.chat/) for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching.</source:markdown>
<source:outline text="Reminder: We have a demo <a href="https://demo.rss.chat/">server</a> for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching." created="Wed, 22 Jul 2026 12:45:34 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/22.html#a124534"/>
</item>
<item>
<title>How the web got gunked</title>
<description><p><i><a href="https://x.com/davewiner/status/2079838781180420113">Posted on Twitter</a> in the middle of last night, written on iPad.</i></p> <p>I use twitter these days because it’s where the people are.</p> <p>The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see. </p> <p>Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen.</p> <p>At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise.</p> <p>We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via <a href="https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9">Cory Doctorow’s</a> <a href="https://en.wikipedia.org/wiki/Enshittification">doctrine</a>, getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works.</p> <p>Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way.</p> <p>PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to.</p> </description>
<pubDate>Wed, 22 Jul 2026 20:21:18 GMT</pubDate>
<link>http://scripting.com/2026/07/22/202118.html?title=howTheWebGotGunked</link>
<guid>http://scripting.com/2026/07/22/202118.html</guid>
<source:markdown>_[Posted on Twitter](https://x.com/davewiner/status/2079838781180420113) in the middle of last night, written on iPad._ I use twitter these days because it’s where the people are. The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see. Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen. At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise. We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via [Cory Doctorow’s](https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9) [doctrine](https://en.wikipedia.org/wiki/Enshittification), getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works. Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way. PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to.</source:markdown>
<source:outline text="How the web got gunked" created="Wed, 22 Jul 2026 20:21:18 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html">
<source:outline text="<i><a href="https://x.com/davewiner/status/2079838781180420113">Posted on Twitter</a> in the middle of last night, written on iPad.</i>" created="Wed, 22 Jul 2026 20:21:24 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202124"/>
<source:outline text="I use twitter these days because it’s where the people are." created="Wed, 22 Jul 2026 20:21:25 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202125"/>
<source:outline text="The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see." flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#aNaNNaNNaN"/>
<source:outline text="Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen." created="Wed, 22 Jul 2026 20:22:26 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202226"/>
<source:outline text="At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise." flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#aNaNNaNNaN"/>
<source:outline text="We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via <a href="https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9">Cory Doctorow’s</a> <a href="https://en.wikipedia.org/wiki/Enshittification">doctrine</a>, getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works." created="Wed, 22 Jul 2026 20:22:52 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202252"/>
<source:outline text="Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way." created="Wed, 22 Jul 2026 20:23:22 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202322"/>
<source:outline text="PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to." flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#aNaNNaNNaN"/>
</source:outline>
</item>
<item>
<description><a href="https://rss.chat/?id=359">RSS.chat</a> -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well.</description>
<pubDate>Tue, 21 Jul 2026 14:37:16 GMT</pubDate>
<link>http://scripting.com/2026/07/21.html#a143716</link>
<guid>http://scripting.com/2026/07/21.html#a143716</guid>
<source:markdown>[RSS.chat](https://rss.chat/?id=359) -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well.</source:markdown>
<source:outline text="<a href="https://rss.chat/?id=359">RSS.chat</a> -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well." created="Tue, 21 Jul 2026 14:37:16 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/21.html#a143716"/>
</item>
<item>
<title>Three-part ecosystem</title>
<description><p><img class="imgRightMargin" src="https://imgs.scripting.com/2026/05/19/reallySimpleNet.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">There are three parts to the rss.chat ecosystem. </p> <ol> <li>Writing. Today's rss.chat <a href="https://demo.rss.chat/">product</a> is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and <a href="https://textcasting.org/">textcasting</a>. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)</li> <li>Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new <a href="https://source.scripting.com/">features</a> in RSS.chat feeds.</li> <li>The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a <a href="https://source.scripting.com/social.opml">bit of docs</a> about how the pieces fit together.</li> </ol> <p>I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa. </p> <p><i>Every part replaceable. </i></p> </description>
<pubDate>Tue, 21 Jul 2026 13:43:09 GMT</pubDate>
<link>http://scripting.com/2026/07/21/134309.html?title=threepartEcosystem</link>
<guid>http://scripting.com/2026/07/21/134309.html</guid>
<source:markdown>There are three parts to the rss.chat ecosystem. 1. Writing. Today's rss.chat [product](https://demo.rss.chat/) is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and [textcasting](https://textcasting.org/). Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-) 2. Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new [features](https://source.scripting.com/) in RSS.chat feeds. 3. The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a [bit of docs](https://source.scripting.com/social.opml) about how the pieces fit together. I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa. _Every part replaceable._</source:markdown>
<source:outline text="Three-part ecosystem" created="Tue, 21 Jul 2026 13:43:09 GMT" type="outline" description="Small pieces loosely joined, all parts replaceable." flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html">
<source:outline text="There are three parts to the rss.chat ecosystem." created="Tue, 21 Jul 2026 13:42:52 GMT" type="outline" flNumberedSubs="true" image="https://imgs.scripting.com/2026/05/19/reallySimpleNet.png" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134252">
<source:outline text="Writing. Today's rss.chat <a href="https://demo.rss.chat/">product</a> is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and <a href="https://textcasting.org/">textcasting</a>. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)" created="Tue, 21 Jul 2026 13:43:20 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134320"/>
<source:outline text="Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new <a href="https://source.scripting.com/">features</a> in RSS.chat feeds." created="Tue, 21 Jul 2026 13:47:35 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134735"/>
<source:outline text="The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a <a href="https://source.scripting.com/social.opml">bit of docs</a> about how the pieces fit together." created="Tue, 21 Jul 2026 13:48:45 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134845"/>
</source:outline>
<source:outline text="I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa." created="Tue, 21 Jul 2026 14:02:08 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a140208"/>
<source:outline text="<i>Every part replaceable. </i>" created="Tue, 21 Jul 2026 14:41:41 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a144141"/>
</source:outline>
</item>
<item>
<description>Two methods for creating standards: <a href="https://daytona.scripting.com/search?q=bootstrap">bootstrap</a> and <a href="https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22">boil the ocean</a>.</description>
<pubDate>Mon, 20 Jul 2026 21:07:23 GMT</pubDate>
<link>http://scripting.com/2026/07/20.html#a210723</link>
<guid>http://scripting.com/2026/07/20.html#a210723</guid>
<source:markdown>Two methods for creating standards: [bootstrap](https://daytona.scripting.com/search?q=bootstrap) and [boil the ocean](https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22).</source:markdown>
<source:outline text="Two methods for creating standards: <a href="https://daytona.scripting.com/search?q=bootstrap">bootstrap</a> and <a href="https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22">boil the ocean</a>." created="Mon, 20 Jul 2026 21:07:23 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a210723"/>
</item>
<item>
<description><img class="imgRightMargin" src="https://imgs.scripting.com/2019/09/02/teamworkWins.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;"><a href="https://demo.rss.chat/?id=189">John Johnston</a> got <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">inboundRss</a> working, so now he can automatically post to his WordPress blog from <a href="https://demo.rss.chat/">demo.rss.chat</a>. These are the kinds of things that "just work" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be <i>the</i> place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for <a href="https://automattic.com/">Matt's company</a> and the <a href="https://wordpress.org/">community</a>. A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously.</description>
<pubDate>Mon, 20 Jul 2026 16:29:08 GMT</pubDate>
<link>http://scripting.com/2026/07/20.html#a162908</link>
<guid>http://scripting.com/2026/07/20.html#a162908</guid>
<source:markdown>[John Johnston](https://demo.rss.chat/?id=189) got [inboundRss](https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss) working, so now he can automatically post to his WordPress blog from [demo.rss.chat](https://demo.rss.chat/). These are the kinds of things that "just work" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be _the_ place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for [Matt's company](https://automattic.com/) and the [community](https://wordpress.org/). A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously.</source:markdown>
<source:outline text="<a href="https://demo.rss.chat/?id=189">John Johnston</a> got <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">inboundRss</a> working, so now he can automatically post to his WordPress blog from <a href="https://demo.rss.chat/">demo.rss.chat</a>. These are the kinds of things that "just work" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be <i>the</i> place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for <a href="https://automattic.com/">Matt's company</a> and the <a href="https://wordpress.org/">community</a>. A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously." created="Mon, 20 Jul 2026 16:29:08 GMT" type="outline" image="https://imgs.scripting.com/2019/09/02/teamworkWins.png" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a162908"/>
</item>
<item>
<description>Howard Rheingold is just the kind of person rss.chat was designed it for. And <a href="http://scripting.com/2026/07/20/161752.html">here he is</a> asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)</description>
<pubDate>Mon, 20 Jul 2026 16:23:59 GMT</pubDate>
<link>http://scripting.com/2026/07/20.html#a162359</link>
<guid>http://scripting.com/2026/07/20.html#a162359</guid>
<source:markdown>Howard Rheingold is just the kind of person rss.chat was designed it for. And [here he is](http://scripting.com/2026/07/20/161752.html) asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)</source:markdown>
<source:outline text="Howard Rheingold is just the kind of person rss.chat was designed it for. And <a href="http://scripting.com/2026/07/20/161752.html">here he is</a> asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)" created="Mon, 20 Jul 2026 16:23:59 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a162359"/>
</item>
<item>
<description>Morning: Today on <a href="https://this.how/rsschat/">RSS.chat</a> we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions.</description>
<pubDate>Mon, 20 Jul 2026 15:43:02 GMT</pubDate>
<link>http://scripting.com/2026/07/20.html#a154302</link>
<guid>http://scripting.com/2026/07/20.html#a154302</guid>
<source:markdown>Morning: Today on [RSS.chat](https://this.how/rsschat/) we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions.</source:markdown>
<source:outline text="Morning: Today on <a href="https://this.how/rsschat/">RSS.chat</a> we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions." created="Mon, 20 Jul 2026 15:43:02 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a154302"/>
</item>
<item>
<description>Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">client</a> and <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">server</a> apps.</description>
<pubDate>Mon, 20 Jul 2026 22:53:56 GMT</pubDate>
<link>http://scripting.com/2026/07/20.html#a225356</link>
<guid>http://scripting.com/2026/07/20.html#a225356</guid>
<source:markdown>Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for [client](https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md) and [server](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md) apps.</source:markdown>
<source:outline text="Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">client</a> and <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">server</a> apps." created="Mon, 20 Jul 2026 22:53:56 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a225356"/>
</item>
<item>
<title>What is RSS.chat for Howard Rheingold</title>
<description><p><i>I am longtime friends and an admirer of <a href="https://daytona.scripting.com/search?q=%22howard%20rheingold%22">Howard Rheingold</a>, who <a href="https://demo.rss.chat/?id=183">expressed</a> an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person. </i></p> <p><a href="https://this.how/rsschat/">RSS.chat</a> is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members.</p> <p>Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text.</p> <p>rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web.</p> <p>The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open.</p> <p>If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning.</p> <p><i>Written by Claude. </i></p> </description>
<pubDate>Mon, 20 Jul 2026 16:17:52 GMT</pubDate>
<link>http://scripting.com/2026/07/20/161752.html?title=whatIsRsschatForHowardRheingold</link>
<guid>http://scripting.com/2026/07/20/161752.html</guid>
<source:markdown>_I am longtime friends and an admirer of [Howard Rheingold](https://daytona.scripting.com/search?q=%22howard%20rheingold%22), who [expressed](https://demo.rss.chat/?id=183) an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person._ [RSS.chat](https://this.how/rsschat/) is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members. Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text. rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web. The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open. If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning. _Written by Claude._</source:markdown>
<source:outline text="What is RSS.chat for Howard Rheingold" created="Mon, 20 Jul 2026 16:17:52 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html">
<source:outline text="<i>I am longtime friends and an admirer of <a href="https://daytona.scripting.com/search?q=%22howard%20rheingold%22">Howard Rheingold</a>, who <a href="https://demo.rss.chat/?id=183">expressed</a> an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person. </i>" created="Mon, 20 Jul 2026 16:18:06 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a161806"/>
<source:outline text="<a href="https://this.how/rsschat/">RSS.chat</a> is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members." created="Mon, 20 Jul 2026 16:20:40 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a162040"/>
<source:outline text="Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text." flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#aNaNNaNNaN"/>
<source:outline text="rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web." flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#aNaNNaNNaN"/>
<source:outline text="The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open." created="Mon, 20 Jul 2026 16:25:17 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a162517"/>
<source:outline text="If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning." flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#aNaNNaNNaN"/>
<source:outline text="<i>Written by Claude. </i>" created="Mon, 20 Jul 2026 16:25:18 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a162518"/>
</source:outline>
</item>
<item>
<description><img class="imgRightMargin" src="https://imgs.scripting.com/2019/09/02/teamworkWins.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">Today we have our first <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">example app for WordPress</a>. We started with an app I wrote that keeps <a href="http://scripting.com/2026/07/19.html#a170642">scripting.com</a> in sync with <a href="https://daveverse.org/2026/07/19/#a11258">daveverse.org</a>, a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in <a href="https://daytona.scripting.com/search?q=%22inbound%20rss%22">Inbound RSS</a>. If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead.</description>
<pubDate>Sun, 19 Jul 2026 17:06:42 GMT</pubDate>
<link>http://scripting.com/2026/07/19.html#a170642</link>
<guid>http://scripting.com/2026/07/19.html#a170642</guid>
<source:markdown>Today we have our first [example app for WordPress](https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss). We started with an app I wrote that keeps [scripting.com](http://scripting.com/2026/07/19.html#a170642) in sync with [daveverse.org](https://daveverse.org/2026/07/19/#a11258), a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in [Inbound RSS](https://daytona.scripting.com/search?q=%22inbound%20rss%22). If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead.</source:markdown>
<source:outline text="Today we have our first <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">example app for WordPress</a>. We started with an app I wrote that keeps <a href="http://scripting.com/2026/07/19.html#a170642">scripting.com</a> in sync with <a href="https://daveverse.org/2026/07/19/#a11258">daveverse.org</a>, a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in <a href="https://daytona.scripting.com/search?q=%22inbound%20rss%22">Inbound RSS</a>. If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead." created="Sun, 19 Jul 2026 17:06:42 GMT" type="outline" image="https://imgs.scripting.com/2019/09/02/teamworkWins.png" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a170642"/>
</item>
<item>
<description>Way back in March as I was starting to work with Claude Code, I think -- we put together a <a href="https://this.how/ai/outliner/outliner.html">pretty nice outliner</a> that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat.</description>
<pubDate>Sun, 19 Jul 2026 17:03:25 GMT</pubDate>
<link>http://scripting.com/2026/07/19.html#a170325</link>
<guid>http://scripting.com/2026/07/19.html#a170325</guid>
<source:markdown>Way back in March as I was starting to work with Claude Code, I think -- we put together a [pretty nice outliner](https://this.how/ai/outliner/outliner.html) that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat.</source:markdown>
<source:outline text="Way back in March as I was starting to work with Claude Code, I think -- we put together a <a href="https://this.how/ai/outliner/outliner.html">pretty nice outliner</a> that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat." created="Sun, 19 Jul 2026 17:03:25 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a170325"/>
</item>
<item>
<description>I <a href="https://demo.rss.chat/?id=180">wonder</a> if it makes <a href="https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html">sense</a> to try to implement <a href="https://standard.site/">standard.site</a> in the context of rss.chat?</description>
<pubDate>Sun, 19 Jul 2026 16:59:02 GMT</pubDate>
<link>http://scripting.com/2026/07/19.html#a165902</link>
<guid>http://scripting.com/2026/07/19.html#a165902</guid>
<source:markdown>I [wonder](https://demo.rss.chat/?id=180) if it makes [sense](https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html) to try to implement [standard.site](https://standard.site/) in the context of rss.chat?</source:markdown>
<source:outline text="I <a href="https://demo.rss.chat/?id=180">wonder</a> if it makes <a href="https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html">sense</a> to try to implement <a href="https://standard.site/">standard.site</a> in the context of rss.chat?" created="Sun, 19 Jul 2026 16:59:02 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a165902"/>
</item>
<item>
<description>Just finished <a href="https://en.wikipedia.org/wiki/The_Expanse_(TV_series)">The Expanse</a> for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web.</description>
<pubDate>Sun, 19 Jul 2026 15:38:23 GMT</pubDate>
<link>http://scripting.com/2026/07/19.html#a153823</link>
<guid>http://scripting.com/2026/07/19.html#a153823</guid>
<source:markdown>Just finished [The Expanse](https://en.wikipedia.org/wiki/The_Expanse_\(TV_series\)) for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web.</source:markdown>
<source:outline text="Just finished <a href="https://en.wikipedia.org/wiki/The_Expanse_(TV_series)">The Expanse</a> for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web." created="Sun, 19 Jul 2026 15:38:23 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a153823"/>
</item>
<item>
<description>We have a <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">firehose</a> in rss.chat. Instant updates from the server. No polling. <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">Docs</a> and <a href="https://github.com/scripting/rss.chat/tree/main/examples/firehose">examples</a>.</description>
<pubDate>Sat, 18 Jul 2026 15:22:37 GMT</pubDate>
<link>http://scripting.com/2026/07/18.html#a152237</link>
<guid>http://scripting.com/2026/07/18.html#a152237</guid>
<source:markdown>We have a [firehose](https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md) in rss.chat. Instant updates from the server. No polling. [Docs](https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md) and [examples](https://github.com/scripting/rss.chat/tree/main/examples/firehose).</source:markdown>
<source:outline text="We have a <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">firehose</a> in rss.chat. Instant updates from the server. No polling. <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">Docs</a> and <a href="https://github.com/scripting/rss.chat/tree/main/examples/firehose">examples</a>." created="Sat, 18 Jul 2026 15:22:37 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a152237"/>
</item>
<item>
<description>An experiment, <a href="https://rss.chat/?id=351">RSS rendered in JSON</a>.</description>
<pubDate>Sat, 18 Jul 2026 17:49:54 GMT</pubDate>
<link>http://scripting.com/2026/07/18.html#a174954</link>
<guid>http://scripting.com/2026/07/18.html#a174954</guid>
<source:markdown>An experiment, [RSS rendered in JSON](https://rss.chat/?id=351).</source:markdown>
<source:outline text="An experiment, <a href="https://rss.chat/?id=351">RSS rendered in JSON</a>." created="Sat, 18 Jul 2026 17:49:54 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a174954"/>
</item>
<item>
<description><a href="http://scripting.com/2018/07/18.html#a124950">Wrote this in 2018</a>: "I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there." An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather.</description>
<pubDate>Sat, 18 Jul 2026 15:37:23 GMT</pubDate>
<link>http://scripting.com/2026/07/18.html#a153723</link>
<guid>http://scripting.com/2026/07/18.html#a153723</guid>
<source:markdown>[Wrote this in 2018](http://scripting.com/2018/07/18.html#a124950): "I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there." An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather.</source:markdown>
<source:outline text="<a href="http://scripting.com/2018/07/18.html#a124950">Wrote this in 2018</a>: "I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there." An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather." created="Sat, 18 Jul 2026 15:37:23 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a153723"/>
</item>
<item>
<description>I just listened to the second episode of a <a href="https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott">podcast</a> about <a href="https://en.wikipedia.org/wiki/General_Magic">General Magic</a>. It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic.</description>
<pubDate>Sat, 18 Jul 2026 18:21:43 GMT</pubDate>
<link>http://scripting.com/2026/07/18.html#a182143</link>
<guid>http://scripting.com/2026/07/18.html#a182143</guid>
<source:markdown>I just listened to the second episode of a [podcast](https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott) about [General Magic](https://en.wikipedia.org/wiki/General_Magic). It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic.</source:markdown>
<source:outline text="I just listened to the second episode of a <a href="https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott">podcast</a> about <a href="https://en.wikipedia.org/wiki/General_Magic">General Magic</a>. It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic." created="Sat, 18 Jul 2026 18:21:43 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a182143"/>
</item>
<item>
<title>A peptalk for devs</title>
<description><p><img class="imgRightMargin" src="https://imgs.scripting.com/2022/11/28/ifyoudontlikethenews.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully. </p> <p>The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you <i>can't</i> break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-)</p> <p>I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before. </p> <p>It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff. </p> <p>I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting. </p> <p>Think about different ways to present the tree structure defined by RSS.chat. </p> <p>Try to do <i>Small pieces loosely joined, </i>which is one of the mottos of this project. The other is <i>All parts are replaceable.</i> If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal.</p> <p>PS: We <a href="http://scripting.com/2026/07/10/161133.html">launched</a> RSS.chat one week ago yesterday.</p> </description>
<pubDate>Sat, 18 Jul 2026 14:30:21 GMT</pubDate>
<link>http://scripting.com/2026/07/18/143021.html?title=aPeptalkForDevs</link>
<guid>http://scripting.com/2026/07/18/143021.html</guid>
<source:markdown>In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully. The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you _can't_ break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-) I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before. It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff. I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting. Think about different ways to present the tree structure defined by RSS.chat. Try to do _Small pieces loosely joined,_ which is one of the mottos of this project. The other is _All parts are replaceable._ If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal. PS: We [launched](http://scripting.com/2026/07/10/161133.html) RSS.chat one week ago yesterday.</source:markdown>
<source:outline text="A peptalk for devs" created="Sat, 18 Jul 2026 14:30:21 GMT" type="outline" description="I focus on the wrapping because that's where the interop lives." flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html">
<source:outline text="In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully." created="Sat, 18 Jul 2026 14:32:15 GMT" image="https://imgs.scripting.com/2022/11/28/ifyoudontlikethenews.png" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a143215"/>
<source:outline text="The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you <i>can't</i> break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-)" created="Sat, 18 Jul 2026 14:36:39 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a143639"/>
<source:outline text="I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before." created="Sat, 18 Jul 2026 14:33:50 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a143350"/>
<source:outline text="It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff." created="Sat, 18 Jul 2026 14:40:28 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144028"/>
<source:outline text="I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting." created="Sat, 18 Jul 2026 14:41:25 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144125"/>
<source:outline text="Think about different ways to present the tree structure defined by RSS.chat." created="Sat, 18 Jul 2026 14:42:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144219"/>
<source:outline text="Try to do <i>Small pieces loosely joined, </i>which is one of the mottos of this project. The other is <i>All parts are replaceable.</i> If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal." created="Sat, 18 Jul 2026 14:42:02 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144202"/>
<source:outline text="PS: We <a href="http://scripting.com/2026/07/10/161133.html">launched</a> RSS.chat one week ago yesterday." created="Sat, 18 Jul 2026 14:44:36 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144436"/>
</source:outline>
</item>
<item>
<description>Our feeds can work with any feed reader. Examples, the <a href="https://rss.chat/users/rss.xml">feed</a> of all posts on rss.chat, and a <a href="https://rss.chat/users/dave/rss.xml">feed</a> containing just mine. We just made a <a href="https://github.com/scripting/rss.chat/issues/14">change</a> in the feeds. There will be loose-ends like this. Still diggin! ;-)</description>
<pubDate>Fri, 17 Jul 2026 21:43:48 GMT</pubDate>
<link>http://scripting.com/2026/07/17.html#a214348</link>
<guid>http://scripting.com/2026/07/17.html#a214348</guid>
<source:markdown>Our feeds can work with any feed reader. Examples, the [feed](https://rss.chat/users/rss.xml) of all posts on rss.chat, and a [feed](https://rss.chat/users/dave/rss.xml) containing just mine. We just made a [change](https://github.com/scripting/rss.chat/issues/14) in the feeds. There will be loose-ends like this. Still diggin! ;-)</source:markdown>
<source:outline text="Our feeds can work with any feed reader. Examples, the <a href="https://rss.chat/users/rss.xml">feed</a> of all posts on rss.chat, and a <a href="https://rss.chat/users/dave/rss.xml">feed</a> containing just mine. We just made a <a href="https://github.com/scripting/rss.chat/issues/14">change</a> in the feeds. There will be loose-ends like this. Still diggin! ;-)" created="Fri, 17 Jul 2026 21:43:48 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a214348"/>
</item>
<item>
<description><a href="https://demo.rss.chat/?id=134">New rss.chat feature</a>: It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours.</description>
<pubDate>Fri, 17 Jul 2026 14:26:29 GMT</pubDate>
<link>http://scripting.com/2026/07/17.html#a142629</link>
<guid>http://scripting.com/2026/07/17.html#a142629</guid>
<source:markdown>[New rss.chat feature](https://demo.rss.chat/?id=134): It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours.</source:markdown>
<source:outline text="<a href="https://demo.rss.chat/?id=134">New rss.chat feature</a>: It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours." created="Fri, 17 Jul 2026 14:26:29 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a142629"/>
</item>
<item>
<description><img class="imgRightMargin" src="https://imgs.scripting.com/2022/12/23/masto.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about <a href="https://joinmastodon.org/about?utm_source=chatgpt.com">ten years after</a> Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started <a href="https://this.how/rsschat/">RSS.chat</a> -- to go down a different path there. What if the social web <i>didn't</i> limit text? That <a href="https://textcasting.org/">assumption</a> is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text.</description>
<pubDate>Fri, 17 Jul 2026 12:55:11 GMT</pubDate>
<link>http://scripting.com/2026/07/17.html#a125511</link>
<guid>http://scripting.com/2026/07/17.html#a125511</guid>
<source:markdown>In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about [ten years after](https://joinmastodon.org/about?utm_source=chatgpt.com) Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started [RSS.chat](https://this.how/rsschat/) -- to go down a different path there. What if the social web _didn't_ limit text? That [assumption](https://textcasting.org/) is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text.</source:markdown>
<source:outline text="In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about <a href="https://joinmastodon.org/about?utm_source=chatgpt.com">ten years after</a> Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started <a href="https://this.how/rsschat/">RSS.chat</a> -- to go down a different path there. What if the social web <i>didn't</i> limit text? That <a href="https://textcasting.org/">assumption</a> is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text." created="Fri, 17 Jul 2026 12:55:11 GMT" type="outline" image="https://imgs.scripting.com/2022/12/23/masto.png" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a125511"/>
</item>
<item>
<description>I mentioned the <a href="http://scripting.com/2026/07/17.html#a125511">previous</a> post <a href="https://rss.chat/?id=319">on rss.chat</a>, and it developed into an interesting thread, something that I've never had the <a href="https://rss.chat/?id=322">option to discuss</a>. AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated <i>new</i> storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that.</description>
<pubDate>Fri, 17 Jul 2026 14:01:28 GMT</pubDate>
<link>http://scripting.com/2026/07/17.html#a140128</link>
<guid>http://scripting.com/2026/07/17.html#a140128</guid>
<source:markdown>I mentioned the [previous](http://scripting.com/2026/07/17.html#a125511) post [on rss.chat](https://rss.chat/?id=319), and it developed into an interesting thread, something that I've never had the [option to discuss](https://rss.chat/?id=322). AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated _new_ storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that.</source:markdown>
<source:outline text="I mentioned the <a href="http://scripting.com/2026/07/17.html#a125511">previous</a> post <a href="https://rss.chat/?id=319">on rss.chat</a>, and it developed into an interesting thread, something that I've never had the <a href="https://rss.chat/?id=322">option to discuss</a>. AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated <i>new</i> storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that." created="Fri, 17 Jul 2026 14:01:28 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a140128"/>
</item>
<item>
<description>Added a layer to the <a href="https://imgs.scripting.com/2026/07/16/docsmenuscreen.png">Docs menu</a>, the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section.</description>
<pubDate>Thu, 16 Jul 2026 22:20:32 GMT</pubDate>
<link>http://scripting.com/2026/07/16.html#a222032</link>
<guid>http://scripting.com/2026/07/16.html#a222032</guid>
<source:markdown>Added a layer to the [Docs menu](https://imgs.scripting.com/2026/07/16/docsmenuscreen.png), the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section.</source:markdown>
<source:outline text="Added a layer to the <a href="https://imgs.scripting.com/2026/07/16/docsmenuscreen.png">Docs menu</a>, the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section." created="Thu, 16 Jul 2026 22:20:32 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/16.html#a222032"/>
</item>
</channel>
</rss>
Raw text
<?xml version="1.0" encoding="UTF-8"?> <!-- RSS generated by oldSchool v0.8.16 on Wed, 29 Jul 2026 17:15:29 GMT --> <rss version="2.0" xmlns:source="https://source.scripting.com/"> <channel> <title>Scripting News</title> <link>http://scripting.com/</link> <description>Dave Winer, OG blogger, podcaster, developed first apps in many categories. Old enough to know better. It's even worse than it appears.</description> <pubDate>Wed, 29 Jul 2026 17:08:22 GMT</pubDate> <language>en-us</language> <generator>oldSchool v0.8.16</generator> <copyright>&copy; copyright 1994-2026 Dave Winer.</copyright> <docs>http://cyber.law.harvard.edu/rss/rss.html</docs> <lastBuildDate>Wed, 29 Jul 2026 17:15:29 GMT</lastBuildDate> <cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post" /> <image> <title>Scripting News</title> <url>https://imgs.scripting.com/2025/06/04/curly.png</url> <link>http://scripting.com/</link> <description>Scripting News gets an image because it's part of a network that uses them. 6/4/25 by DW</description> </image> <source:account service="bluesky">@scripting.com</source:account> <source:account service="mastodon">@davew@mastodon.social</source:account> <source:account service="twitter">bullmancuso</source:account> <source:localTime>Wed, July 29, 2026 1:15 PM EDT</source:localTime> <source:self>http://scripting.com/rss.xml</source:self> <source:blogroll>https://feedland.social/opml?screenname=davewiner&catname=blogroll</source:blogroll> <item> <description>Our <a href="https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml">feed parser</a> is updated to understand the new elements for RSSchat.</description> <pubDate>Wed, 29 Jul 2026 16:27:58 GMT</pubDate> <link>http://scripting.com/2026/07/29.html#a162758</link> <guid>http://scripting.com/2026/07/29.html#a162758</guid> <source:markdown>Our [feed parser](https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml) is updated to understand the new elements for RSSchat.</source:markdown> <source:outline text="Our <a href="https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml">feed parser</a> is updated to understand the new elements for RSSchat." created="Wed, 29 Jul 2026 16:27:58 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/29.html#a162758"/> </item> <item> <description>I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web. </description> <pubDate>Wed, 29 Jul 2026 14:04:37 GMT</pubDate> <link>http://scripting.com/2026/07/29.html#a140437</link> <guid>http://scripting.com/2026/07/29.html#a140437</guid> <source:markdown>I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web.</source:markdown> <source:outline text="I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web. " created="Wed, 29 Jul 2026 14:04:37 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/29.html#a140437"/> </item> <item> <title>Learnings from Andy Hertzfeld</title> <description><p>Listened to this <a href="https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels">podcast interview</a> with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too.</p> <p>His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden:</p> <ol> <li>you have time to try out every idea because it's free and fast.</li> <li>you have time to work on interop, building bridges between your software and other people's.</li> <li>a very long list of other things you can do that one person could never do before. </li> </ol> <p>Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers). </p> <p>I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night.</p> <p>In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this.</p> <p>This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one. </p> <p>The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else.</p> <p>There's never been a leap in tech anything like this in my life. </p> <p>How could Andy Hertzfeld knowing all that which I'm sure he does, not use it?</p> <p>Also -- I didn't know <a href="https://daytona.scripting.com/search?q=JLG">JLG</a> wanted to kill <a href="https://daytona.scripting.com/search?q=hypercard">Hypercard</a>, but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP. </p> <p>It's fascinating to hear his story. </p> </description> <pubDate>Wed, 29 Jul 2026 17:08:22 GMT</pubDate> <link>http://scripting.com/2026/07/29/170822.html?title=learningsFromAndyHertzfeld</link> <guid>http://scripting.com/2026/07/29/170822.html</guid> <source:markdown>Listened to this [podcast interview](https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels) with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too. His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden: 1. you have time to try out every idea because it's free and fast. 2. you have time to work on interop, building bridges between your software and other people's. 3. a very long list of other things you can do that one person could never do before. Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers). I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night. In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this. This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one. The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else. There's never been a leap in tech anything like this in my life. How could Andy Hertzfeld knowing all that which I'm sure he does, not use it? Also -- I didn't know [JLG](https://daytona.scripting.com/search?q=JLG) wanted to kill [Hypercard](https://daytona.scripting.com/search?q=hypercard), but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP. It's fascinating to hear his story.</source:markdown> <source:outline text="Learnings from Andy Hertzfeld" created="Wed, 29 Jul 2026 17:08:22 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html"> <source:outline text="Listened to this <a href="https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels">podcast interview</a> with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too." created="Wed, 29 Jul 2026 17:08:38 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170838"/> <source:outline text="His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden:" created="Wed, 29 Jul 2026 17:09:17 GMT" flNumberedSubs="true" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170917"> <source:outline text="you have time to try out every idea because it's free and fast." created="Wed, 29 Jul 2026 17:09:18 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170918"/> <source:outline text="you have time to work on interop, building bridges between your software and other people's." created="Wed, 29 Jul 2026 17:09:28 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170928"/> <source:outline text="a very long list of other things you can do that one person could never do before." created="Wed, 29 Jul 2026 17:09:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170919"/> </source:outline> <source:outline text="Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers)." created="Wed, 29 Jul 2026 17:09:58 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a170958"/> <source:outline text="I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night." created="Wed, 29 Jul 2026 17:12:03 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171203"/> <source:outline text="In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this." created="Wed, 29 Jul 2026 17:12:22 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171222"/> <source:outline text="This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one." created="Wed, 29 Jul 2026 17:12:51 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171251"/> <source:outline text="The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else." created="Wed, 29 Jul 2026 17:13:09 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171309"/> <source:outline text="There's never been a leap in tech anything like this in my life." created="Wed, 29 Jul 2026 17:13:47 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171347"/> <source:outline text="How could Andy Hertzfeld knowing all that which I'm sure he does, not use it?" created="Wed, 29 Jul 2026 17:13:51 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171351"/> <source:outline text="Also -- I didn't know <a href="https://daytona.scripting.com/search?q=JLG">JLG</a> wanted to kill <a href="https://daytona.scripting.com/search?q=hypercard">Hypercard</a>, but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP." created="Wed, 29 Jul 2026 17:11:04 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171104"/> <source:outline text="It's fascinating to hear his story." created="Wed, 29 Jul 2026 17:10:07 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/29/170822.html#a171007"/> </source:outline> </item> <item> <title>When the walls came down</title> <description><p>Yesterday's <a href="http://scripting.com/2026/07/27.html">Scripting News</a> was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in <a href="http://scripting.com/2002/09.html">September 2002</a>. If you look at what's there, a post about re-opening the <a href="https://github.com/scripting/frontierOdb">Frontier object database</a> format would be considered the top item on any other day, but it's the last of the untitled posts for the day. </p> <p>At the <a href="http://scripting.com/2026/07/27.html#a181535">top of the page</a>, a surprise that <a href="https://pfefferle.dev/">Matthias Pfefferle</a> at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto. </p> <p>Look at what we've done. I stress <i>we. </i>Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely. </p> <p>Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web.</p> <p>Anyway, now we've got half of the <a href="http://scripting.com/2026/07/27/134952.html">big picture</a> working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about <a href="http://scripting.com/2026/07/27/134952.html">how I see the network evolving</a>. I predict, if this bootstrap works, we will come back here in a year and say things like "If he only knew." But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it. </p> <p>I'm proud that I have a record of <a href="http://scripting.com/2002/09.html">September 2002</a> for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-) </p> <p>And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as <a href="https://cyber.harvard.edu/rss/rss.html">specified</a> in 2003, even using one of the <a href="https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt">elements</a> that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. I've accumulated all the extensions I use in my software since the early teens in the <a href="https://source.scripting.com/">source namespace</a>. And that's where the <a href="https://source.scripting.com/social.opml">new stuff</a> went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible.</p> <p>I played with a lot of names while <a href="https://this.how/rsschat/">RSS.chat</a> was in development but decided the name had to be RSS.something. It deserves a lot more <a href="https://rss.chat/?id=426">love</a> than it has gotten from the tech world. I don't want to hide it, I want it to get a victory <a href="https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought">parade</a> like the one the <a href="https://daytona.scripting.com/search?q=knicks">Knicks</a> got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006.</p> <p>Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go. </p> <p>Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud. </p> <p>I thought my career was winding down, but now it feels like it's just getting started.</p> <p>Reminded of a great quote in <a href="https://en.wikipedia.org/wiki/The_Godfather_Part_III">Godfather III</a>, <a href="https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s">Michael Corleone says</a>: "Just when I thought I was out, they pull me back in."</p> <p>Here we go!</p> <p>PS: A new <a href="https://this.how/rsschat/">this.how page</a> for RSS.chat. It has a little directory to the big spots you might want. </p> </description> <pubDate>Tue, 28 Jul 2026 11:59:45 GMT</pubDate> <link>http://scripting.com/2026/07/28/115945.html?title=whenTheWallsCameDown</link> <guid>http://scripting.com/2026/07/28/115945.html</guid> <source:markdown>Yesterday's [Scripting News](http://scripting.com/2026/07/27.html) was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in [September 2002](http://scripting.com/2002/09.html). If you look at what's there, a post about re-opening the [Frontier object database](https://github.com/scripting/frontierOdb) format would be considered the top item on any other day, but it's the last of the untitled posts for the day. At the [top of the page](http://scripting.com/2026/07/27.html#a181535), a surprise that [Matthias Pfefferle](https://pfefferle.dev/) at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto. Look at what we've done. I stress _we._ Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely. Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web. Anyway, now we've got half of the [big picture](http://scripting.com/2026/07/27/134952.html) working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about [how I see the network evolving](http://scripting.com/2026/07/27/134952.html). I predict, if this bootstrap works, we will come back here in a year and say things like "If he only knew." But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it. I'm proud that I have a record of [September 2002](http://scripting.com/2002/09.html) for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-) And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as [specified](https://cyber.harvard.edu/rss/rss.html) in 2003, even using one of the [elements](https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt) that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is [extensible](https://cyber.harvard.edu/rss/rss.html#extendingRss). I've accumulated all the extensions I use in my software since the early teens in the [source namespace](https://source.scripting.com/). And that's where the [new stuff](https://source.scripting.com/social.opml) went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible. I played with a lot of names while [RSS.chat](https://this.how/rsschat/) was in development but decided the name had to be RSS.something. It deserves a lot more [love](https://rss.chat/?id=426) than it has gotten from the tech world. I don't want to hide it, I want it to get a victory [parade](https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought) like the one the [Knicks](https://daytona.scripting.com/search?q=knicks) got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006. Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go. Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud. I thought my career was winding down, but now it feels like it's just getting started. Reminded of a great quote in [Godfather III](https://en.wikipedia.org/wiki/The_Godfather_Part_III), [Michael Corleone says](https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s): "Just when I thought I was out, they pull me back in." Here we go! PS: A new [this.how page](https://this.how/rsschat/) for RSS.chat. It has a little directory to the big spots you might want.</source:markdown> <source:outline text="When the walls came down" created="Tue, 28 Jul 2026 11:59:45 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html"> <source:outline text="Yesterday's <a href="http://scripting.com/2026/07/27.html">Scripting News</a> was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in <a href="http://scripting.com/2002/09.html">September 2002</a>. If you look at what's there, a post about re-opening the <a href="https://github.com/scripting/frontierOdb">Frontier object database</a> format would be considered the top item on any other day, but it's the last of the untitled posts for the day." created="Tue, 28 Jul 2026 11:50:37 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a115037"/> <source:outline text="At the <a href="http://scripting.com/2026/07/27.html#a181535">top of the page</a>, a surprise that <a href="https://pfefferle.dev/">Matthias Pfefferle</a> at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto." created="Tue, 28 Jul 2026 12:13:31 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121331"/> <source:outline text="Look at what we've done. I stress <i>we. </i>Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely." created="Tue, 28 Jul 2026 12:33:02 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a123302"/> <source:outline text="Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web." created="Tue, 28 Jul 2026 12:15:35 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121535"/> <source:outline text="Anyway, now we've got half of the <a href="http://scripting.com/2026/07/27/134952.html">big picture</a> working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about <a href="http://scripting.com/2026/07/27/134952.html">how I see the network evolving</a>. I predict, if this bootstrap works, we will come back here in a year and say things like "If he only knew." But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it." created="Tue, 28 Jul 2026 11:58:53 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a115853"/> <source:outline text="I'm proud that I have a record of <a href="http://scripting.com/2002/09.html">September 2002</a> for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-)" created="Tue, 28 Jul 2026 12:17:01 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121701"/> <source:outline text="And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as <a href="https://cyber.harvard.edu/rss/rss.html">specified</a> in 2003, even using one of the <a href="https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt">elements</a> that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. I've accumulated all the extensions I use in my software since the early teens in the <a href="https://source.scripting.com/">source namespace</a>. And that's where the <a href="https://source.scripting.com/social.opml">new stuff</a> went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible." created="Tue, 28 Jul 2026 12:04:27 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120427"/> <source:outline text="I played with a lot of names while <a href="https://this.how/rsschat/">RSS.chat</a> was in development but decided the name had to be RSS.something. It deserves a lot more <a href="https://rss.chat/?id=426">love</a> than it has gotten from the tech world. I don't want to hide it, I want it to get a victory <a href="https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought">parade</a> like the one the <a href="https://daytona.scripting.com/search?q=knicks">Knicks</a> got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006." created="Tue, 28 Jul 2026 12:19:51 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a121951"/> <source:outline text="Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go." created="Tue, 28 Jul 2026 11:59:12 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a115912"/> <source:outline text="Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud." created="Tue, 28 Jul 2026 12:07:36 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120736"/> <source:outline text="I thought my career was winding down, but now it feels like it's just getting started." created="Tue, 28 Jul 2026 12:08:41 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120841"/> <source:outline text="Reminded of a great quote in <a href="https://en.wikipedia.org/wiki/The_Godfather_Part_III">Godfather III</a>, <a href="https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s">Michael Corleone says</a>: "Just when I thought I was out, they pull me back in."" created="Tue, 28 Jul 2026 12:08:54 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120854"/> <source:outline text="Here we go!" created="Tue, 28 Jul 2026 12:08:39 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a120839"/> <source:outline text="PS: A new <a href="https://this.how/rsschat/">this.how page</a> for RSS.chat. It has a little directory to the big spots you might want." created="Tue, 28 Jul 2026 17:53:23 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/28/115945.html#a175323"/> </source:outline> </item> <item> <description><a href="https://github.com/pfefferle/wordpress-rss-chat">This is something</a>. WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his <a href="https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/">podcast</a> last year. If people use this connection and see how it works, then we'll get an idea of where to go next.</description> <pubDate>Mon, 27 Jul 2026 18:15:35 GMT</pubDate> <link>http://scripting.com/2026/07/27.html#a181535</link> <guid>http://scripting.com/2026/07/27.html#a181535</guid> <source:markdown>[This is something](https://github.com/pfefferle/wordpress-rss-chat). WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his [podcast](https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/) last year. If people use this connection and see how it works, then we'll get an idea of where to go next.</source:markdown> <source:outline text="<a href="https://github.com/pfefferle/wordpress-rss-chat">This is something</a>. WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his <a href="https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/">podcast</a> last year. If people use this connection and see how it works, then we'll get an idea of where to go next." created="Mon, 27 Jul 2026 18:15:35 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a181535"/> </item> <item> <description>BTW, I had no idea the WordPress connection was coming and here it is.</description> <pubDate>Mon, 27 Jul 2026 21:41:57 GMT</pubDate> <link>http://scripting.com/2026/07/27.html#a214157</link> <guid>http://scripting.com/2026/07/27.html#a214157</guid> <source:markdown>BTW, I had no idea the WordPress connection was coming and here it is.</source:markdown> <source:outline text="BTW, I had no idea the WordPress connection was coming and here it is." created="Mon, 27 Jul 2026 21:41:57 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a214157"/> </item> <item> <description>Of course we have a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> for RSS.chat updates.</description> <pubDate>Mon, 27 Jul 2026 17:46:32 GMT</pubDate> <link>http://scripting.com/2026/07/27.html#a174632</link> <guid>http://scripting.com/2026/07/27.html#a174632</guid> <source:markdown>Of course we have a [feed](https://news.rss.chat/worknotes/rss.xml) for RSS.chat updates.</source:markdown> <source:outline text="Of course we have a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> for RSS.chat updates." created="Mon, 27 Jul 2026 17:46:32 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a174632"/> </item> <item> <description><img class="imgRightMargin" src="https://imgs.scripting.com/2021/06/14/strongman.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;"><a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">How we document APIs</a>. We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">doc</a>. I have a vested interest, in my job I read a lot of bad API docs.</description> <pubDate>Mon, 27 Jul 2026 16:33:10 GMT</pubDate> <link>http://scripting.com/2026/07/27.html#a163310</link> <guid>http://scripting.com/2026/07/27.html#a163310</guid> <source:markdown>[How we document APIs](https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md). We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this [doc](https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md). I have a vested interest, in my job I read a lot of bad API docs.</source:markdown> <source:outline text="<a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">How we document APIs</a>. We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md">doc</a>. I have a vested interest, in my job I read a lot of bad API docs." created="Mon, 27 Jul 2026 16:33:10 GMT" type="outline" image="https://imgs.scripting.com/2021/06/14/strongman.png" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a163310"/> </item> <item> <description><a href="https://github.com/scripting/frontierOdb">A new utility</a> exports the contents of a Frontier <a href="https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132">object database</a> into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it.</description> <pubDate>Mon, 27 Jul 2026 13:26:10 GMT</pubDate> <link>http://scripting.com/2026/07/27.html#a132610</link> <guid>http://scripting.com/2026/07/27.html#a132610</guid> <source:markdown>[A new utility](https://github.com/scripting/frontierOdb) exports the contents of a Frontier [object database](https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132) into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it.</source:markdown> <source:outline text="<a href="https://github.com/scripting/frontierOdb">A new utility</a> exports the contents of a Frontier <a href="https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132">object database</a> into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it." created="Mon, 27 Jul 2026 13:26:10 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27.html#a132610"/> </item> <item> <title>How I see the network evolving</title> <description><p>A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt. </p> <p>The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them. </p> <p>RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation. </p> <p>"Small pieces loosely joined" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily. </p> <p>Just to be sure everyone understands -- I already have such an app, called <a href="https://docs.feedland.com/gettingstarted.md">FeedLand</a>. You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start. </p> <p>FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature. </p> <p>We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures. </p> <p>I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play. </p> </description> <pubDate>Mon, 27 Jul 2026 13:49:52 GMT</pubDate> <link>http://scripting.com/2026/07/27/134952.html?title=howISeeTheNetworkEvolving</link> <guid>http://scripting.com/2026/07/27/134952.html</guid> <source:markdown>A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt. The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them. RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation. "Small pieces loosely joined" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily. Just to be sure everyone understands -- I already have such an app, called [FeedLand](https://docs.feedland.com/gettingstarted.md). You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start. FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature. We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures. I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play.</source:markdown> <source:outline text="How I see the network evolving" created="Mon, 27 Jul 2026 13:49:52 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html"> <source:outline text="A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt." created="Mon, 27 Jul 2026 13:39:18 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a133918"/> <source:outline text="The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them." created="Mon, 27 Jul 2026 13:50:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135019"/> <source:outline text="RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation." created="Mon, 27 Jul 2026 13:50:29 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135029"/> <source:outline text=""Small pieces loosely joined" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily." created="Mon, 27 Jul 2026 13:55:09 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135509"/> <source:outline text="Just to be sure everyone understands -- I already have such an app, called <a href="https://docs.feedland.com/gettingstarted.md">FeedLand</a>. You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start." created="Mon, 27 Jul 2026 13:56:57 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135657"/> <source:outline text="FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature." created="Mon, 27 Jul 2026 14:00:03 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a140003"/> <source:outline text="We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures." created="Mon, 27 Jul 2026 13:51:29 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a135129"/> <source:outline text="I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play." created="Mon, 27 Jul 2026 14:02:44 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/27/134952.html#a140244"/> </source:outline> </item> <item> <description><a href="https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md">New docs for</a> the browser JavaScript interface to the RSS.chat API.</description> <pubDate>Sun, 26 Jul 2026 15:37:08 GMT</pubDate> <link>http://scripting.com/2026/07/26.html#a153708</link> <guid>http://scripting.com/2026/07/26.html#a153708</guid> <source:markdown>[New docs for](https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md) the browser JavaScript interface to the RSS.chat API.</source:markdown> <source:outline text="<a href="https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md">New docs for</a> the browser JavaScript interface to the RSS.chat API." created="Sun, 26 Jul 2026 15:37:08 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a153708"/> </item> <item> <description>Scott Hanson has a new <a href="https://github.com/scotthansonde/rsschat-wordpress-service">service</a> that connects <a href="https://this.how/rsschat/">RSS.chat</a> to WordPress.</description> <pubDate>Sun, 26 Jul 2026 13:50:50 GMT</pubDate> <link>http://scripting.com/2026/07/26.html#a135050</link> <guid>http://scripting.com/2026/07/26.html#a135050</guid> <source:markdown>Scott Hanson has a new [service](https://github.com/scotthansonde/rsschat-wordpress-service) that connects [RSS.chat](https://this.how/rsschat/) to WordPress.</source:markdown> <source:outline text="Scott Hanson has a new <a href="https://github.com/scotthansonde/rsschat-wordpress-service">service</a> that connects <a href="https://this.how/rsschat/">RSS.chat</a> to WordPress." created="Sun, 26 Jul 2026 13:50:50 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a135050"/> </item> <item> <description>Many of the questions about <a href="https://this.how/rsschat/">RSS.chat</a> center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.</description> <pubDate>Sun, 26 Jul 2026 20:19:51 GMT</pubDate> <link>http://scripting.com/2026/07/26.html#a201951</link> <guid>http://scripting.com/2026/07/26.html#a201951</guid> <source:markdown>Many of the questions about [RSS.chat](https://this.how/rsschat/) center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.</source:markdown> <source:outline text="Many of the questions about <a href="https://this.how/rsschat/">RSS.chat</a> center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even." created="Sun, 26 Jul 2026 20:19:51 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a201951"/> </item> <item> <description>A note to people who run <a href="https://us.wordcamp.org/2026/">WordCamp</a> conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program.</description> <pubDate>Sun, 26 Jul 2026 13:20:17 GMT</pubDate> <link>http://scripting.com/2026/07/26.html#a132017</link> <guid>http://scripting.com/2026/07/26.html#a132017</guid> <source:markdown>A note to people who run [WordCamp](https://us.wordcamp.org/2026/) conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program.</source:markdown> <source:outline text="A note to people who run <a href="https://us.wordcamp.org/2026/">WordCamp</a> conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program." created="Sun, 26 Jul 2026 13:20:17 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26.html#a132017"/> </item> <item> <title>rss.chat isn't really a product</title> <description><p>It's what we used to call a <a href="https://daytona.scripting.com/search?q=%22coral%20reef%22">coral reef</a>. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to <i>serve</i> them. </p> <p>This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this <a href="https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523">in a comment</a> in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.</p> </description> <pubDate>Sun, 26 Jul 2026 13:53:07 GMT</pubDate> <link>http://scripting.com/2026/07/26/135307.html?title=rsschatIsntReallyAProduct</link> <guid>http://scripting.com/2026/07/26/135307.html</guid> <source:markdown>It's what we used to call a [coral reef](https://daytona.scripting.com/search?q=%22coral%20reef%22). A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to _serve_ them. This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this [in a comment](https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523) in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is [extensible](https://cyber.harvard.edu/rss/rss.html#extendingRss). It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.</source:markdown> <source:outline text="rss.chat isn't really a product" created="Sun, 26 Jul 2026 13:53:07 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26/135307.html"> <source:outline text="It's what we used to call a <a href="https://daytona.scripting.com/search?q=%22coral%20reef%22">coral reef</a>. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to <i>serve</i> them." created="Sun, 26 Jul 2026 13:53:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/135307.html#a135319"/> <source:outline text="This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this <a href="https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523">in a comment</a> in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is <a href="https://cyber.harvard.edu/rss/rss.html#extendingRss">extensible</a>. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd." created="Sun, 26 Jul 2026 13:53:26 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/135307.html#a135326"/> </source:outline> </item> <item> <title>Confession: I still drive a Tesla.</title> <description><p>Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed. </p> <ol> <li>Backed into a charging station.</li> <li>An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel.</li> <li>My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look. </li> <li>A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup.</li> </ol> <p>I don't know if it accomplishes anything but to me it feels like retribution of a sort. </p> </description> <pubDate>Sun, 26 Jul 2026 20:12:20 GMT</pubDate> <link>http://scripting.com/2026/07/26/201220.html?title=confessionIStillDriveATesla</link> <guid>http://scripting.com/2026/07/26/201220.html</guid> <source:markdown>Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed. 1. Backed into a charging station. 2. An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel. 3. My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look. 4. A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup. I don't know if it accomplishes anything but to me it feels like retribution of a sort.</source:markdown> <source:outline text="Confession: I still drive a Tesla." created="Sun, 26 Jul 2026 20:12:20 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html"> <source:outline text="Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed." created="Sun, 26 Jul 2026 20:12:38 GMT" flNumberedSubs="true" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201238"> <source:outline text="Backed into a charging station." created="Sun, 26 Jul 2026 20:12:47 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201247"/> <source:outline text="An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel." created="Sun, 26 Jul 2026 20:12:57 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201257"/> <source:outline text="My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look." created="Sun, 26 Jul 2026 20:13:09 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201309"/> <source:outline text="A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said "hit a deer eh?" Yup." created="Sun, 26 Jul 2026 20:12:48 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201248"/> </source:outline> <source:outline text="I don't know if it accomplishes anything but to me it feels like retribution of a sort." created="Sun, 26 Jul 2026 20:12:31 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/26/201220.html#a201231"/> </source:outline> </item> <item> <description><img class="imgRightMargin" src="https://imgs.scripting.com/2023/11/30/goodhumortruck.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor.</description> <pubDate>Sat, 25 Jul 2026 12:43:05 GMT</pubDate> <link>http://scripting.com/2026/07/25.html#a124305</link> <guid>http://scripting.com/2026/07/25.html#a124305</guid> <source:markdown>How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor.</source:markdown> <source:outline text="How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor." created="Sat, 25 Jul 2026 12:43:05 GMT" type="outline" image="https://imgs.scripting.com/2023/11/30/goodhumortruck.png" flInCalendar="true" permalink="http://scripting.com/2026/07/25.html#a124305"/> </item> <item> <description>Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there.</description> <pubDate>Sat, 25 Jul 2026 14:25:11 GMT</pubDate> <link>http://scripting.com/2026/07/25.html#a142511</link> <guid>http://scripting.com/2026/07/25.html#a142511</guid> <source:markdown>Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there.</source:markdown> <source:outline text="Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there." created="Sat, 25 Jul 2026 14:25:11 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/25.html#a142511"/> </item> <item> <title>RSS.chat has an API</title> <description><p>It's a standard REST API.</p> <p>Here's the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037">server side</a> of the API. </p> <p>Here's how you call it from <a href="https://github.com/scripting/rss.chat/blob/main/client/code/api.js">browser-based JavaScript</a>. You can include that code in your apps.</p> <p>Here's an <a href="https://github.com/scripting/rss.chat/tree/main/examples/easyblogger">example app</a> that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-)</p> <p>And finally here are the <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/api.md">docs</a> for the API itself. </p> </description> <pubDate>Sat, 25 Jul 2026 14:12:53 GMT</pubDate> <link>http://scripting.com/2026/07/25/141253.html?title=rsschatHasAnApi</link> <guid>http://scripting.com/2026/07/25/141253.html</guid> <source:markdown>It's a standard REST API. Here's the [server side](https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037) of the API. Here's how you call it from [browser-based JavaScript](https://github.com/scripting/rss.chat/blob/main/client/code/api.js). You can include that code in your apps. Here's an [example app](https://github.com/scripting/rss.chat/tree/main/examples/easyblogger) that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-) And finally here are the [docs](https://github.com/scripting/rss.chat/blob/main/server/docs/api.md) for the API itself.</source:markdown> <source:outline text="RSS.chat has an API" created="Sat, 25 Jul 2026 14:12:53 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html"> <source:outline text="It's a standard REST API." created="Sat, 25 Jul 2026 14:13:02 GMT" flBulletedSubs="true" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141302"/> <source:outline text="Here's the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037">server side</a> of the API." created="Sat, 25 Jul 2026 14:13:22 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141322"/> <source:outline text="Here's how you call it from <a href="https://github.com/scripting/rss.chat/blob/main/client/code/api.js">browser-based JavaScript</a>. You can include that code in your apps." created="Sat, 25 Jul 2026 14:15:17 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141517"/> <source:outline text="Here's an <a href="https://github.com/scripting/rss.chat/tree/main/examples/easyblogger">example app</a> that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-)" created="Sat, 25 Jul 2026 14:16:23 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141623"/> <source:outline text="And finally here are the <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/api.md">docs</a> for the API itself." created="Sat, 25 Jul 2026 14:17:46 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/25/141253.html#a141746"/> </source:outline> </item> <item> <description>RSS.chat worknotes are a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> now. Updated when there's a new feature or fix. Same info is on the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">worknotes</a> <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">pages</a> in the <a href="https://github.com/scripting/rss.chat">repo</a>.</description> <pubDate>Fri, 24 Jul 2026 16:43:13 GMT</pubDate> <link>http://scripting.com/2026/07/24.html#a164313</link> <guid>http://scripting.com/2026/07/24.html#a164313</guid> <source:markdown>RSS.chat worknotes are a [feed](https://news.rss.chat/worknotes/rss.xml) now. Updated when there's a new feature or fix. Same info is on the [worknotes](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md) [pages](https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md) in the [repo](https://github.com/scripting/rss.chat).</source:markdown> <source:outline text="RSS.chat worknotes are a <a href="https://news.rss.chat/worknotes/rss.xml">feed</a> now. Updated when there's a new feature or fix. Same info is on the <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">worknotes</a> <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">pages</a> in the <a href="https://github.com/scripting/rss.chat">repo</a>." created="Fri, 24 Jul 2026 16:43:13 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/24.html#a164313"/> </item> <item> <title>Dear podcast client devs</title> <description><p>Podcast client developers -- don't give up like <a href="https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying">this guy</a> did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do. </p> <p><b>Subscribable subscription lists</b> would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code. </p> <p>I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others. </p> <p>This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client <i>deserves</i> to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists. </p> <p>Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be <a href="https://www.dictionary.com/browse/overt">overt</a> in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades. </p> <p>It's time to rock the f'ing boat! :-)</p> <p>Podcasting forever! </p> </description> <pubDate>Fri, 24 Jul 2026 14:01:59 GMT</pubDate> <link>http://scripting.com/2026/07/24/140159.html?title=dearPodcastClientDevs</link> <guid>http://scripting.com/2026/07/24/140159.html</guid> <source:markdown>Podcast client developers -- don't give up like [this guy](https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying) did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do. **Subscribable subscription lists** would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code. I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others. This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client _deserves_ to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists. Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be [overt](https://www.dictionary.com/browse/overt) in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades. It's time to rock the f'ing boat! :-) Podcasting forever!</source:markdown> <source:outline text="Dear podcast client devs" created="Fri, 24 Jul 2026 14:01:59 GMT" type="outline" description="The big new idea -- subscribable subscription lists." flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html"> <source:outline text="Podcast client developers -- don't give up like <a href="https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying">this guy</a> did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do." created="Fri, 24 Jul 2026 13:33:48 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a133348"/> <source:outline text="<b>Subscribable subscription lists</b> would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code." created="Fri, 24 Jul 2026 14:10:54 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141054"/> <source:outline text="I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others." created="Fri, 24 Jul 2026 14:11:27 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141127"/> <source:outline text="This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client <i>deserves</i> to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists." created="Fri, 24 Jul 2026 14:14:05 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141405"/> <source:outline text="Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be <a href="https://www.dictionary.com/browse/overt">overt</a> in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades." created="Fri, 24 Jul 2026 14:00:27 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a140027"/> <source:outline text="It's time to rock the f'ing boat! :-)" created="Fri, 24 Jul 2026 14:16:16 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141616"/> <source:outline text="Podcasting forever!" created="Fri, 24 Jul 2026 14:16:21 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/24/140159.html#a141621"/> </source:outline> </item> <item> <description><img class="imgRightMargin" src="https://imgs.scripting.com/2025/09/17/reallySimpleKetchup.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">A new feature on rss.chat, <b>images</b>. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to <a href="https://textcasting.org/">textcasting</a>. It's a feature I needed to be reminded is essential. The first <a href="https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com">browser</a> to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from <a href="https://en.wikipedia.org/wiki/Tim_Berners-Lee">TBL</a>, but it is most definitely a standard feature of the web.</description> <pubDate>Thu, 23 Jul 2026 15:01:19 GMT</pubDate> <link>http://scripting.com/2026/07/23.html#a150119</link> <guid>http://scripting.com/2026/07/23.html#a150119</guid> <source:markdown>A new feature on rss.chat, **images**. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to [textcasting](https://textcasting.org/). It's a feature I needed to be reminded is essential. The first [browser](https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com) to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from [TBL](https://en.wikipedia.org/wiki/Tim_Berners-Lee), but it is most definitely a standard feature of the web.</source:markdown> <source:outline text="A new feature on rss.chat, <b>images</b>. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to <a href="https://textcasting.org/">textcasting</a>. It's a feature I needed to be reminded is essential. The first <a href="https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com">browser</a> to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from <a href="https://en.wikipedia.org/wiki/Tim_Berners-Lee">TBL</a>, but it is most definitely a standard feature of the web." created="Thu, 23 Jul 2026 15:01:19 GMT" type="outline" image="https://imgs.scripting.com/2025/09/17/reallySimpleKetchup.png" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a150119"/> </item> <item> <description><a href="https://demo.rss.chat/?id=242">Amyloo</a>, a longtime friend from the early days of podcasting, has made an appearance on <a href="https://demo.rss.chat">demo.rss.chat</a>. So happy to see her. Here's <a href="http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3">one of the bits</a> we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. <span class="spOldSchoolEmoji">😄</span></description> <pubDate>Thu, 23 Jul 2026 15:14:15 GMT</pubDate> <link>http://scripting.com/2026/07/23.html#a151415</link> <guid>http://scripting.com/2026/07/23.html#a151415</guid> <source:markdown>[Amyloo](https://demo.rss.chat/?id=242), a longtime friend from the early days of podcasting, has made an appearance on [demo.rss.chat](https://demo.rss.chat). So happy to see her. Here's [one of the bits](http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3) we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. 😄</source:markdown> <source:outline text="<a href="https://demo.rss.chat/?id=242">Amyloo</a>, a longtime friend from the early days of podcasting, has made an appearance on <a href="https://demo.rss.chat">demo.rss.chat</a>. So happy to see her. Here's <a href="http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3">one of the bits</a> we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. <span class="spOldSchoolEmoji">😄</span>" created="Thu, 23 Jul 2026 15:14:15 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a151415"/> </item> <item> <description>Early this morning we got a report of a <b>security issue</b> in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc">follow the instructions</a> and do the update asap.</description> <pubDate>Thu, 23 Jul 2026 14:49:19 GMT</pubDate> <link>http://scripting.com/2026/07/23.html#a144919</link> <guid>http://scripting.com/2026/07/23.html#a144919</guid> <source:markdown>Early this morning we got a report of a **security issue** in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please [follow the instructions](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc) and do the update asap.</source:markdown> <source:outline text="Early this morning we got a report of a <b>security issue</b> in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc">follow the instructions</a> and do the update asap." created="Thu, 23 Jul 2026 14:49:19 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a144919"/> </item> <item> <description>Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. <i>Quickly.</i> I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap.</description> <pubDate>Thu, 23 Jul 2026 13:07:40 GMT</pubDate> <link>http://scripting.com/2026/07/23.html#a130740</link> <guid>http://scripting.com/2026/07/23.html#a130740</guid> <source:markdown>Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. _Quickly._ I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap.</source:markdown> <source:outline text="Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. <i>Quickly.</i> I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap." created="Thu, 23 Jul 2026 13:07:40 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/23.html#a130740"/> </item> <item> <description>RSS.chat now supports <a href="https://sqlite.org/">SQLite</a>. Simpler and faster to install. You don't have to host a database, it's now built into the server. Full <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/install.md">instructions</a>. Questions or <a href="https://github.com/scripting/rss.chat/issues/17">issues</a>.</description> <pubDate>Wed, 22 Jul 2026 13:15:31 GMT</pubDate> <link>http://scripting.com/2026/07/22.html#a131531</link> <guid>http://scripting.com/2026/07/22.html#a131531</guid> <source:markdown>RSS.chat now supports [SQLite](https://sqlite.org/). Simpler and faster to install. You don't have to host a database, it's now built into the server. Full [instructions](https://github.com/scripting/rss.chat/blob/main/server/docs/install.md). Questions or [issues](https://github.com/scripting/rss.chat/issues/17).</source:markdown> <source:outline text="RSS.chat now supports <a href="https://sqlite.org/">SQLite</a>. Simpler and faster to install. You don't have to host a database, it's now built into the server. Full <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/install.md">instructions</a>. Questions or <a href="https://github.com/scripting/rss.chat/issues/17">issues</a>." created="Wed, 22 Jul 2026 13:15:31 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/22.html#a131531"/> </item> <item> <description>Reminder: We have a demo <a href="https://demo.rss.chat/">server</a> for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching.</description> <pubDate>Wed, 22 Jul 2026 12:45:34 GMT</pubDate> <link>http://scripting.com/2026/07/22.html#a124534</link> <guid>http://scripting.com/2026/07/22.html#a124534</guid> <source:markdown>Reminder: We have a demo [server](https://demo.rss.chat/) for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching.</source:markdown> <source:outline text="Reminder: We have a demo <a href="https://demo.rss.chat/">server</a> for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching." created="Wed, 22 Jul 2026 12:45:34 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/22.html#a124534"/> </item> <item> <title>How the web got gunked</title> <description><p><i><a href="https://x.com/davewiner/status/2079838781180420113">Posted on Twitter</a> in the middle of last night, written on iPad.</i></p> <p>I use twitter these days because it’s where the people are.</p> <p>The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see. </p> <p>Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen.</p> <p>At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise.</p> <p>We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via <a href="https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9">Cory Doctorow’s</a> <a href="https://en.wikipedia.org/wiki/Enshittification">doctrine</a>, getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works.</p> <p>Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way.</p> <p>PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to.</p> </description> <pubDate>Wed, 22 Jul 2026 20:21:18 GMT</pubDate> <link>http://scripting.com/2026/07/22/202118.html?title=howTheWebGotGunked</link> <guid>http://scripting.com/2026/07/22/202118.html</guid> <source:markdown>_[Posted on Twitter](https://x.com/davewiner/status/2079838781180420113) in the middle of last night, written on iPad._ I use twitter these days because it’s where the people are. The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see. Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen. At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise. We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via [Cory Doctorow’s](https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9) [doctrine](https://en.wikipedia.org/wiki/Enshittification), getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works. Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way. PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to.</source:markdown> <source:outline text="How the web got gunked" created="Wed, 22 Jul 2026 20:21:18 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html"> <source:outline text="<i><a href="https://x.com/davewiner/status/2079838781180420113">Posted on Twitter</a> in the middle of last night, written on iPad.</i>" created="Wed, 22 Jul 2026 20:21:24 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202124"/> <source:outline text="I use twitter these days because it’s where the people are." created="Wed, 22 Jul 2026 20:21:25 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202125"/> <source:outline text="The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see." flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#aNaNNaNNaN"/> <source:outline text="Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen." created="Wed, 22 Jul 2026 20:22:26 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202226"/> <source:outline text="At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise." flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#aNaNNaNNaN"/> <source:outline text="We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via <a href="https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9">Cory Doctorow’s</a> <a href="https://en.wikipedia.org/wiki/Enshittification">doctrine</a>, getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works." created="Wed, 22 Jul 2026 20:22:52 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202252"/> <source:outline text="Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way." created="Wed, 22 Jul 2026 20:23:22 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#a202322"/> <source:outline text="PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to." flInCalendar="true" permalink="http://scripting.com/2026/07/22/202118.html#aNaNNaNNaN"/> </source:outline> </item> <item> <description><a href="https://rss.chat/?id=359">RSS.chat</a> -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well.</description> <pubDate>Tue, 21 Jul 2026 14:37:16 GMT</pubDate> <link>http://scripting.com/2026/07/21.html#a143716</link> <guid>http://scripting.com/2026/07/21.html#a143716</guid> <source:markdown>[RSS.chat](https://rss.chat/?id=359) -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well.</source:markdown> <source:outline text="<a href="https://rss.chat/?id=359">RSS.chat</a> -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well." created="Tue, 21 Jul 2026 14:37:16 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/21.html#a143716"/> </item> <item> <title>Three-part ecosystem</title> <description><p><img class="imgRightMargin" src="https://imgs.scripting.com/2026/05/19/reallySimpleNet.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">There are three parts to the rss.chat ecosystem. </p> <ol> <li>Writing. Today's rss.chat <a href="https://demo.rss.chat/">product</a> is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and <a href="https://textcasting.org/">textcasting</a>. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)</li> <li>Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new <a href="https://source.scripting.com/">features</a> in RSS.chat feeds.</li> <li>The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a <a href="https://source.scripting.com/social.opml">bit of docs</a> about how the pieces fit together.</li> </ol> <p>I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa. </p> <p><i>Every part replaceable. </i></p> </description> <pubDate>Tue, 21 Jul 2026 13:43:09 GMT</pubDate> <link>http://scripting.com/2026/07/21/134309.html?title=threepartEcosystem</link> <guid>http://scripting.com/2026/07/21/134309.html</guid> <source:markdown>There are three parts to the rss.chat ecosystem. 1. Writing. Today's rss.chat [product](https://demo.rss.chat/) is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and [textcasting](https://textcasting.org/). Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-) 2. Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new [features](https://source.scripting.com/) in RSS.chat feeds. 3. The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a [bit of docs](https://source.scripting.com/social.opml) about how the pieces fit together. I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa. _Every part replaceable._</source:markdown> <source:outline text="Three-part ecosystem" created="Tue, 21 Jul 2026 13:43:09 GMT" type="outline" description="Small pieces loosely joined, all parts replaceable." flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html"> <source:outline text="There are three parts to the rss.chat ecosystem." created="Tue, 21 Jul 2026 13:42:52 GMT" type="outline" flNumberedSubs="true" image="https://imgs.scripting.com/2026/05/19/reallySimpleNet.png" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134252"> <source:outline text="Writing. Today's rss.chat <a href="https://demo.rss.chat/">product</a> is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of "follow." And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and <a href="https://textcasting.org/">textcasting</a>. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)" created="Tue, 21 Jul 2026 13:43:20 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134320"/> <source:outline text="Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new <a href="https://source.scripting.com/">features</a> in RSS.chat feeds." created="Tue, 21 Jul 2026 13:47:35 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134735"/> <source:outline text="The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a <a href="https://source.scripting.com/social.opml">bit of docs</a> about how the pieces fit together." created="Tue, 21 Jul 2026 13:48:45 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a134845"/> </source:outline> <source:outline text="I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa." created="Tue, 21 Jul 2026 14:02:08 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a140208"/> <source:outline text="<i>Every part replaceable. </i>" created="Tue, 21 Jul 2026 14:41:41 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/21/134309.html#a144141"/> </source:outline> </item> <item> <description>Two methods for creating standards: <a href="https://daytona.scripting.com/search?q=bootstrap">bootstrap</a> and <a href="https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22">boil the ocean</a>.</description> <pubDate>Mon, 20 Jul 2026 21:07:23 GMT</pubDate> <link>http://scripting.com/2026/07/20.html#a210723</link> <guid>http://scripting.com/2026/07/20.html#a210723</guid> <source:markdown>Two methods for creating standards: [bootstrap](https://daytona.scripting.com/search?q=bootstrap) and [boil the ocean](https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22).</source:markdown> <source:outline text="Two methods for creating standards: <a href="https://daytona.scripting.com/search?q=bootstrap">bootstrap</a> and <a href="https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22">boil the ocean</a>." created="Mon, 20 Jul 2026 21:07:23 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a210723"/> </item> <item> <description><img class="imgRightMargin" src="https://imgs.scripting.com/2019/09/02/teamworkWins.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;"><a href="https://demo.rss.chat/?id=189">John Johnston</a> got <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">inboundRss</a> working, so now he can automatically post to his WordPress blog from <a href="https://demo.rss.chat/">demo.rss.chat</a>. These are the kinds of things that "just work" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be <i>the</i> place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for <a href="https://automattic.com/">Matt's company</a> and the <a href="https://wordpress.org/">community</a>. A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously.</description> <pubDate>Mon, 20 Jul 2026 16:29:08 GMT</pubDate> <link>http://scripting.com/2026/07/20.html#a162908</link> <guid>http://scripting.com/2026/07/20.html#a162908</guid> <source:markdown>[John Johnston](https://demo.rss.chat/?id=189) got [inboundRss](https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss) working, so now he can automatically post to his WordPress blog from [demo.rss.chat](https://demo.rss.chat/). These are the kinds of things that "just work" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be _the_ place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for [Matt's company](https://automattic.com/) and the [community](https://wordpress.org/). A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously.</source:markdown> <source:outline text="<a href="https://demo.rss.chat/?id=189">John Johnston</a> got <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">inboundRss</a> working, so now he can automatically post to his WordPress blog from <a href="https://demo.rss.chat/">demo.rss.chat</a>. These are the kinds of things that "just work" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be <i>the</i> place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for <a href="https://automattic.com/">Matt's company</a> and the <a href="https://wordpress.org/">community</a>. A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously." created="Mon, 20 Jul 2026 16:29:08 GMT" type="outline" image="https://imgs.scripting.com/2019/09/02/teamworkWins.png" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a162908"/> </item> <item> <description>Howard Rheingold is just the kind of person rss.chat was designed it for. And <a href="http://scripting.com/2026/07/20/161752.html">here he is</a> asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)</description> <pubDate>Mon, 20 Jul 2026 16:23:59 GMT</pubDate> <link>http://scripting.com/2026/07/20.html#a162359</link> <guid>http://scripting.com/2026/07/20.html#a162359</guid> <source:markdown>Howard Rheingold is just the kind of person rss.chat was designed it for. And [here he is](http://scripting.com/2026/07/20/161752.html) asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)</source:markdown> <source:outline text="Howard Rheingold is just the kind of person rss.chat was designed it for. And <a href="http://scripting.com/2026/07/20/161752.html">here he is</a> asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)" created="Mon, 20 Jul 2026 16:23:59 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a162359"/> </item> <item> <description>Morning: Today on <a href="https://this.how/rsschat/">RSS.chat</a> we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions.</description> <pubDate>Mon, 20 Jul 2026 15:43:02 GMT</pubDate> <link>http://scripting.com/2026/07/20.html#a154302</link> <guid>http://scripting.com/2026/07/20.html#a154302</guid> <source:markdown>Morning: Today on [RSS.chat](https://this.how/rsschat/) we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions.</source:markdown> <source:outline text="Morning: Today on <a href="https://this.how/rsschat/">RSS.chat</a> we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions." created="Mon, 20 Jul 2026 15:43:02 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a154302"/> </item> <item> <description>Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">client</a> and <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">server</a> apps.</description> <pubDate>Mon, 20 Jul 2026 22:53:56 GMT</pubDate> <link>http://scripting.com/2026/07/20.html#a225356</link> <guid>http://scripting.com/2026/07/20.html#a225356</guid> <source:markdown>Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for [client](https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md) and [server](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md) apps.</source:markdown> <source:outline text="Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for <a href="https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md">client</a> and <a href="https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md">server</a> apps." created="Mon, 20 Jul 2026 22:53:56 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20.html#a225356"/> </item> <item> <title>What is RSS.chat for Howard Rheingold</title> <description><p><i>I am longtime friends and an admirer of <a href="https://daytona.scripting.com/search?q=%22howard%20rheingold%22">Howard Rheingold</a>, who <a href="https://demo.rss.chat/?id=183">expressed</a> an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person. </i></p> <p><a href="https://this.how/rsschat/">RSS.chat</a> is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members.</p> <p>Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text.</p> <p>rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web.</p> <p>The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open.</p> <p>If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning.</p> <p><i>Written by Claude. </i></p> </description> <pubDate>Mon, 20 Jul 2026 16:17:52 GMT</pubDate> <link>http://scripting.com/2026/07/20/161752.html?title=whatIsRsschatForHowardRheingold</link> <guid>http://scripting.com/2026/07/20/161752.html</guid> <source:markdown>_I am longtime friends and an admirer of [Howard Rheingold](https://daytona.scripting.com/search?q=%22howard%20rheingold%22), who [expressed](https://demo.rss.chat/?id=183) an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person._ [RSS.chat](https://this.how/rsschat/) is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members. Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text. rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web. The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open. If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning. _Written by Claude._</source:markdown> <source:outline text="What is RSS.chat for Howard Rheingold" created="Mon, 20 Jul 2026 16:17:52 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html"> <source:outline text="<i>I am longtime friends and an admirer of <a href="https://daytona.scripting.com/search?q=%22howard%20rheingold%22">Howard Rheingold</a>, who <a href="https://demo.rss.chat/?id=183">expressed</a> an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person. </i>" created="Mon, 20 Jul 2026 16:18:06 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a161806"/> <source:outline text="<a href="https://this.how/rsschat/">RSS.chat</a> is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members." created="Mon, 20 Jul 2026 16:20:40 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a162040"/> <source:outline text="Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text." flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#aNaNNaNNaN"/> <source:outline text="rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web." flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#aNaNNaNNaN"/> <source:outline text="The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open." created="Mon, 20 Jul 2026 16:25:17 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a162517"/> <source:outline text="If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning." flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#aNaNNaNNaN"/> <source:outline text="<i>Written by Claude. </i>" created="Mon, 20 Jul 2026 16:25:18 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/20/161752.html#a162518"/> </source:outline> </item> <item> <description><img class="imgRightMargin" src="https://imgs.scripting.com/2019/09/02/teamworkWins.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">Today we have our first <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">example app for WordPress</a>. We started with an app I wrote that keeps <a href="http://scripting.com/2026/07/19.html#a170642">scripting.com</a> in sync with <a href="https://daveverse.org/2026/07/19/#a11258">daveverse.org</a>, a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in <a href="https://daytona.scripting.com/search?q=%22inbound%20rss%22">Inbound RSS</a>. If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead.</description> <pubDate>Sun, 19 Jul 2026 17:06:42 GMT</pubDate> <link>http://scripting.com/2026/07/19.html#a170642</link> <guid>http://scripting.com/2026/07/19.html#a170642</guid> <source:markdown>Today we have our first [example app for WordPress](https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss). We started with an app I wrote that keeps [scripting.com](http://scripting.com/2026/07/19.html#a170642) in sync with [daveverse.org](https://daveverse.org/2026/07/19/#a11258), a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in [Inbound RSS](https://daytona.scripting.com/search?q=%22inbound%20rss%22). If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead.</source:markdown> <source:outline text="Today we have our first <a href="https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss">example app for WordPress</a>. We started with an app I wrote that keeps <a href="http://scripting.com/2026/07/19.html#a170642">scripting.com</a> in sync with <a href="https://daveverse.org/2026/07/19/#a11258">daveverse.org</a>, a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in <a href="https://daytona.scripting.com/search?q=%22inbound%20rss%22">Inbound RSS</a>. If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead." created="Sun, 19 Jul 2026 17:06:42 GMT" type="outline" image="https://imgs.scripting.com/2019/09/02/teamworkWins.png" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a170642"/> </item> <item> <description>Way back in March as I was starting to work with Claude Code, I think -- we put together a <a href="https://this.how/ai/outliner/outliner.html">pretty nice outliner</a> that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat.</description> <pubDate>Sun, 19 Jul 2026 17:03:25 GMT</pubDate> <link>http://scripting.com/2026/07/19.html#a170325</link> <guid>http://scripting.com/2026/07/19.html#a170325</guid> <source:markdown>Way back in March as I was starting to work with Claude Code, I think -- we put together a [pretty nice outliner](https://this.how/ai/outliner/outliner.html) that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat.</source:markdown> <source:outline text="Way back in March as I was starting to work with Claude Code, I think -- we put together a <a href="https://this.how/ai/outliner/outliner.html">pretty nice outliner</a> that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat." created="Sun, 19 Jul 2026 17:03:25 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a170325"/> </item> <item> <description>I <a href="https://demo.rss.chat/?id=180">wonder</a> if it makes <a href="https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html">sense</a> to try to implement <a href="https://standard.site/">standard.site</a> in the context of rss.chat?</description> <pubDate>Sun, 19 Jul 2026 16:59:02 GMT</pubDate> <link>http://scripting.com/2026/07/19.html#a165902</link> <guid>http://scripting.com/2026/07/19.html#a165902</guid> <source:markdown>I [wonder](https://demo.rss.chat/?id=180) if it makes [sense](https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html) to try to implement [standard.site](https://standard.site/) in the context of rss.chat?</source:markdown> <source:outline text="I <a href="https://demo.rss.chat/?id=180">wonder</a> if it makes <a href="https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html">sense</a> to try to implement <a href="https://standard.site/">standard.site</a> in the context of rss.chat?" created="Sun, 19 Jul 2026 16:59:02 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a165902"/> </item> <item> <description>Just finished <a href="https://en.wikipedia.org/wiki/The_Expanse_(TV_series)">The Expanse</a> for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web.</description> <pubDate>Sun, 19 Jul 2026 15:38:23 GMT</pubDate> <link>http://scripting.com/2026/07/19.html#a153823</link> <guid>http://scripting.com/2026/07/19.html#a153823</guid> <source:markdown>Just finished [The Expanse](https://en.wikipedia.org/wiki/The_Expanse_\(TV_series\)) for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web.</source:markdown> <source:outline text="Just finished <a href="https://en.wikipedia.org/wiki/The_Expanse_(TV_series)">The Expanse</a> for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web." created="Sun, 19 Jul 2026 15:38:23 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/19.html#a153823"/> </item> <item> <description>We have a <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">firehose</a> in rss.chat. Instant updates from the server. No polling. <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">Docs</a> and <a href="https://github.com/scripting/rss.chat/tree/main/examples/firehose">examples</a>.</description> <pubDate>Sat, 18 Jul 2026 15:22:37 GMT</pubDate> <link>http://scripting.com/2026/07/18.html#a152237</link> <guid>http://scripting.com/2026/07/18.html#a152237</guid> <source:markdown>We have a [firehose](https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md) in rss.chat. Instant updates from the server. No polling. [Docs](https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md) and [examples](https://github.com/scripting/rss.chat/tree/main/examples/firehose).</source:markdown> <source:outline text="We have a <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">firehose</a> in rss.chat. Instant updates from the server. No polling. <a href="https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md">Docs</a> and <a href="https://github.com/scripting/rss.chat/tree/main/examples/firehose">examples</a>." created="Sat, 18 Jul 2026 15:22:37 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a152237"/> </item> <item> <description>An experiment, <a href="https://rss.chat/?id=351">RSS rendered in JSON</a>.</description> <pubDate>Sat, 18 Jul 2026 17:49:54 GMT</pubDate> <link>http://scripting.com/2026/07/18.html#a174954</link> <guid>http://scripting.com/2026/07/18.html#a174954</guid> <source:markdown>An experiment, [RSS rendered in JSON](https://rss.chat/?id=351).</source:markdown> <source:outline text="An experiment, <a href="https://rss.chat/?id=351">RSS rendered in JSON</a>." created="Sat, 18 Jul 2026 17:49:54 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a174954"/> </item> <item> <description><a href="http://scripting.com/2018/07/18.html#a124950">Wrote this in 2018</a>: "I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there." An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather.</description> <pubDate>Sat, 18 Jul 2026 15:37:23 GMT</pubDate> <link>http://scripting.com/2026/07/18.html#a153723</link> <guid>http://scripting.com/2026/07/18.html#a153723</guid> <source:markdown>[Wrote this in 2018](http://scripting.com/2018/07/18.html#a124950): "I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there." An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather.</source:markdown> <source:outline text="<a href="http://scripting.com/2018/07/18.html#a124950">Wrote this in 2018</a>: "I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there." An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather." created="Sat, 18 Jul 2026 15:37:23 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a153723"/> </item> <item> <description>I just listened to the second episode of a <a href="https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott">podcast</a> about <a href="https://en.wikipedia.org/wiki/General_Magic">General Magic</a>. It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic.</description> <pubDate>Sat, 18 Jul 2026 18:21:43 GMT</pubDate> <link>http://scripting.com/2026/07/18.html#a182143</link> <guid>http://scripting.com/2026/07/18.html#a182143</guid> <source:markdown>I just listened to the second episode of a [podcast](https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott) about [General Magic](https://en.wikipedia.org/wiki/General_Magic). It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic.</source:markdown> <source:outline text="I just listened to the second episode of a <a href="https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott">podcast</a> about <a href="https://en.wikipedia.org/wiki/General_Magic">General Magic</a>. It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic." created="Sat, 18 Jul 2026 18:21:43 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/18.html#a182143"/> </item> <item> <title>A peptalk for devs</title> <description><p><img class="imgRightMargin" src="https://imgs.scripting.com/2022/11/28/ifyoudontlikethenews.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully. </p> <p>The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you <i>can't</i> break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-)</p> <p>I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before. </p> <p>It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff. </p> <p>I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting. </p> <p>Think about different ways to present the tree structure defined by RSS.chat. </p> <p>Try to do <i>Small pieces loosely joined, </i>which is one of the mottos of this project. The other is <i>All parts are replaceable.</i> If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal.</p> <p>PS: We <a href="http://scripting.com/2026/07/10/161133.html">launched</a> RSS.chat one week ago yesterday.</p> </description> <pubDate>Sat, 18 Jul 2026 14:30:21 GMT</pubDate> <link>http://scripting.com/2026/07/18/143021.html?title=aPeptalkForDevs</link> <guid>http://scripting.com/2026/07/18/143021.html</guid> <source:markdown>In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully. The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you _can't_ break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-) I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before. It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff. I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting. Think about different ways to present the tree structure defined by RSS.chat. Try to do _Small pieces loosely joined,_ which is one of the mottos of this project. The other is _All parts are replaceable._ If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal. PS: We [launched](http://scripting.com/2026/07/10/161133.html) RSS.chat one week ago yesterday.</source:markdown> <source:outline text="A peptalk for devs" created="Sat, 18 Jul 2026 14:30:21 GMT" type="outline" description="I focus on the wrapping because that's where the interop lives." flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html"> <source:outline text="In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully." created="Sat, 18 Jul 2026 14:32:15 GMT" image="https://imgs.scripting.com/2022/11/28/ifyoudontlikethenews.png" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a143215"/> <source:outline text="The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you <i>can't</i> break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-)" created="Sat, 18 Jul 2026 14:36:39 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a143639"/> <source:outline text="I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before." created="Sat, 18 Jul 2026 14:33:50 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a143350"/> <source:outline text="It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff." created="Sat, 18 Jul 2026 14:40:28 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144028"/> <source:outline text="I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting." created="Sat, 18 Jul 2026 14:41:25 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144125"/> <source:outline text="Think about different ways to present the tree structure defined by RSS.chat." created="Sat, 18 Jul 2026 14:42:19 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144219"/> <source:outline text="Try to do <i>Small pieces loosely joined, </i>which is one of the mottos of this project. The other is <i>All parts are replaceable.</i> If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal." created="Sat, 18 Jul 2026 14:42:02 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144202"/> <source:outline text="PS: We <a href="http://scripting.com/2026/07/10/161133.html">launched</a> RSS.chat one week ago yesterday." created="Sat, 18 Jul 2026 14:44:36 GMT" flInCalendar="true" permalink="http://scripting.com/2026/07/18/143021.html#a144436"/> </source:outline> </item> <item> <description>Our feeds can work with any feed reader. Examples, the <a href="https://rss.chat/users/rss.xml">feed</a> of all posts on rss.chat, and a <a href="https://rss.chat/users/dave/rss.xml">feed</a> containing just mine. We just made a <a href="https://github.com/scripting/rss.chat/issues/14">change</a> in the feeds. There will be loose-ends like this. Still diggin! ;-)</description> <pubDate>Fri, 17 Jul 2026 21:43:48 GMT</pubDate> <link>http://scripting.com/2026/07/17.html#a214348</link> <guid>http://scripting.com/2026/07/17.html#a214348</guid> <source:markdown>Our feeds can work with any feed reader. Examples, the [feed](https://rss.chat/users/rss.xml) of all posts on rss.chat, and a [feed](https://rss.chat/users/dave/rss.xml) containing just mine. We just made a [change](https://github.com/scripting/rss.chat/issues/14) in the feeds. There will be loose-ends like this. Still diggin! ;-)</source:markdown> <source:outline text="Our feeds can work with any feed reader. Examples, the <a href="https://rss.chat/users/rss.xml">feed</a> of all posts on rss.chat, and a <a href="https://rss.chat/users/dave/rss.xml">feed</a> containing just mine. We just made a <a href="https://github.com/scripting/rss.chat/issues/14">change</a> in the feeds. There will be loose-ends like this. Still diggin! ;-)" created="Fri, 17 Jul 2026 21:43:48 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a214348"/> </item> <item> <description><a href="https://demo.rss.chat/?id=134">New rss.chat feature</a>: It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours.</description> <pubDate>Fri, 17 Jul 2026 14:26:29 GMT</pubDate> <link>http://scripting.com/2026/07/17.html#a142629</link> <guid>http://scripting.com/2026/07/17.html#a142629</guid> <source:markdown>[New rss.chat feature](https://demo.rss.chat/?id=134): It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours.</source:markdown> <source:outline text="<a href="https://demo.rss.chat/?id=134">New rss.chat feature</a>: It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours." created="Fri, 17 Jul 2026 14:26:29 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a142629"/> </item> <item> <description><img class="imgRightMargin" src="https://imgs.scripting.com/2022/12/23/masto.png" border="0" style="float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;">In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about <a href="https://joinmastodon.org/about?utm_source=chatgpt.com">ten years after</a> Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started <a href="https://this.how/rsschat/">RSS.chat</a> -- to go down a different path there. What if the social web <i>didn't</i> limit text? That <a href="https://textcasting.org/">assumption</a> is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text.</description> <pubDate>Fri, 17 Jul 2026 12:55:11 GMT</pubDate> <link>http://scripting.com/2026/07/17.html#a125511</link> <guid>http://scripting.com/2026/07/17.html#a125511</guid> <source:markdown>In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about [ten years after](https://joinmastodon.org/about?utm_source=chatgpt.com) Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started [RSS.chat](https://this.how/rsschat/) -- to go down a different path there. What if the social web _didn't_ limit text? That [assumption](https://textcasting.org/) is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text.</source:markdown> <source:outline text="In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about <a href="https://joinmastodon.org/about?utm_source=chatgpt.com">ten years after</a> Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started <a href="https://this.how/rsschat/">RSS.chat</a> -- to go down a different path there. What if the social web <i>didn't</i> limit text? That <a href="https://textcasting.org/">assumption</a> is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text." created="Fri, 17 Jul 2026 12:55:11 GMT" type="outline" image="https://imgs.scripting.com/2022/12/23/masto.png" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a125511"/> </item> <item> <description>I mentioned the <a href="http://scripting.com/2026/07/17.html#a125511">previous</a> post <a href="https://rss.chat/?id=319">on rss.chat</a>, and it developed into an interesting thread, something that I've never had the <a href="https://rss.chat/?id=322">option to discuss</a>. AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated <i>new</i> storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that.</description> <pubDate>Fri, 17 Jul 2026 14:01:28 GMT</pubDate> <link>http://scripting.com/2026/07/17.html#a140128</link> <guid>http://scripting.com/2026/07/17.html#a140128</guid> <source:markdown>I mentioned the [previous](http://scripting.com/2026/07/17.html#a125511) post [on rss.chat](https://rss.chat/?id=319), and it developed into an interesting thread, something that I've never had the [option to discuss](https://rss.chat/?id=322). AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated _new_ storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that.</source:markdown> <source:outline text="I mentioned the <a href="http://scripting.com/2026/07/17.html#a125511">previous</a> post <a href="https://rss.chat/?id=319">on rss.chat</a>, and it developed into an interesting thread, something that I've never had the <a href="https://rss.chat/?id=322">option to discuss</a>. AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated <i>new</i> storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that." created="Fri, 17 Jul 2026 14:01:28 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/17.html#a140128"/> </item> <item> <description>Added a layer to the <a href="https://imgs.scripting.com/2026/07/16/docsmenuscreen.png">Docs menu</a>, the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section.</description> <pubDate>Thu, 16 Jul 2026 22:20:32 GMT</pubDate> <link>http://scripting.com/2026/07/16.html#a222032</link> <guid>http://scripting.com/2026/07/16.html#a222032</guid> <source:markdown>Added a layer to the [Docs menu](https://imgs.scripting.com/2026/07/16/docsmenuscreen.png), the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section.</source:markdown> <source:outline text="Added a layer to the <a href="https://imgs.scripting.com/2026/07/16/docsmenuscreen.png">Docs menu</a>, the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section." created="Thu, 16 Jul 2026 22:20:32 GMT" type="outline" flInCalendar="true" permalink="http://scripting.com/2026/07/16.html#a222032"/> </item> </channel> </rss>
Raw headers
{
"cf-cache-status": "DYNAMIC",
"cf-ray": "a22eca944ea46019-CMH",
"connection": "close",
"content-length": "172703",
"content-type": "text/xml",
"date": "Wed, 29 Jul 2026 20:14:41 GMT",
"etag": "\"a146338d9be64ef36527b3e4619b09a0\"",
"last-modified": "Wed, 29 Jul 2026 17:15:30 GMT",
"server": "cloudflare",
"x-amz-id-2": "+TLHEqsSMw8QNS0rR5gBRd5W5f9b4SA7Hy/I/NI9rvmblXPsPwzw6WisDzGo+kQYuYGa6XPgvw0=",
"x-amz-request-id": "BWM3JE1SR875FBJZ",
"x-amz-version-id": "Xtty.Q.Q8_y_x9Ghdi7KUAPUCEy8nHlm"
}
Parsed with @rowanmanning/feed-parser
{
"meta": {
"type": "rss",
"version": "2.0"
},
"language": "en-us",
"title": "Scripting News",
"description": "Dave Winer, OG blogger, podcaster, developed first apps in many categories. Old enough to know better. It's even worse than it appears.",
"copyright": "© copyright 1994-2026 Dave Winer.",
"url": "http://scripting.com/",
"self": null,
"published": "2026-07-29T17:08:22.000Z",
"updated": "2026-07-29T17:15:29.000Z",
"generator": {
"label": "oldSchool v0.8.16",
"version": null,
"url": null
},
"image": {
"title": "Scripting News",
"url": "https://imgs.scripting.com/2025/06/04/curly.png"
},
"authors": [],
"categories": [],
"items": [
{
"id": "http://scripting.com/2026/07/29.html#a162758",
"title": null,
"description": "Our <a href=\"https://feeder.scripting.com/?feedurl=https%3A%2F%2Frss.chat%2Fusers%2Fdave%2Frss.xml\">feed parser</a> is updated to understand the new elements for RSSchat.",
"url": "http://scripting.com/2026/07/29.html#a162758",
"published": "2026-07-29T16:27:58.000Z",
"updated": "2026-07-29T16:27:58.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/29.html#a140437",
"title": null,
"description": "I want one social network with lots of branches where ideas flow in ways people want them to flow. Take the big corporations out of the middle. They have not served us well because they aren't in the business of serving us. They can provide unique user interfaces for reading or writing. They should be as diverse as apps are everywhere else but the web.\n",
"url": "http://scripting.com/2026/07/29.html#a140437",
"published": "2026-07-29T14:04:37.000Z",
"updated": "2026-07-29T14:04:37.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/29/170822.html",
"title": "Learnings from Andy Hertzfeld",
"description": "<p>Listened to this <a href=\"https://spellboundproductions.substack.com/p/ep-4-one-of-techs-ogs-on-why-ai-feels\">podcast interview</a> with Andy Hertzfeld one of the lead devs on the Macintosh, he talks about his time at General Magic and Google too.</p>\n<p>His interviewers were surprised that he likes developing with AI tools. People think that developing is just coding, but that's only part of it, and when you put that aside and become the director, script writer, choreographer, the whole thing, all of a sudden:</p>\n<ol>\n<li>you have time to try out every idea because it's free and fast.</li>\n<li>you have time to work on interop, building bridges between your software and other people's.</li>\n<li>a very long list of other things you can do that one person could never do before. </li>\n</ol>\n<p>Programmers have a better chance of being social in a world like this, but so far unless you want all your software from bots, you still will like the work of a craftsperson and visionary more than Claude (who I have deep respect for, not sarcastic, it seriously has superpowers). </p>\n<p>I'm doing some of my best work now because I can dream, I can ask Claude to try something out overnight and most of the time it is able to do it. and then what if we did this -- for the next night.</p>\n<p>In between we write docs, help users, add features to the product that's shipped that people are developing around. And most important it checks all the code for breakage before anyone sees it. never had anything like this.</p>\n<p>This means a lot of things -- one of them -- a single developer can create products at bigco scale. If we think a big company did something wrong, we can compete. We still need a few things to make this really work -- user-owned and controlled storage is the big one. </p>\n<p>The bot can handle infinite complexity. If you ask it to do something where the result is clear, it does it. It doesn't matter what it is. It will need help and encouragement, a pointer in the right direction, and along the way we all seem to be sharing what we learn with everyone else.</p>\n<p>There's never been a leap in tech anything like this in my life. </p>\n<p>How could Andy Hertzfeld knowing all that which I'm sure he does, not use it?</p>\n<p>Also -- I didn't know <a href=\"https://daytona.scripting.com/search?q=JLG\">JLG</a> wanted to kill <a href=\"https://daytona.scripting.com/search?q=hypercard\">Hypercard</a>, but if he did I'm pretty sure I know why. There are all these unnecessary divisions in tech. The first impulse should be to work together. I know that Andy sees it from the other side, he talks about it in the podcast, he felt that way about Newton re their Magic Cap system at General Magic. Yes, you all should have at least made your products work together, and for sure you should have bet on SMTP. </p>\n<p>It's fascinating to hear his story. </p>\n",
"url": "http://scripting.com/2026/07/29/170822.html?title=learningsFromAndyHertzfeld",
"published": "2026-07-29T17:08:22.000Z",
"updated": "2026-07-29T17:08:22.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/28/115945.html",
"title": "When the walls came down",
"description": "<p>Yesterday's <a href=\"http://scripting.com/2026/07/27.html\">Scripting News</a> was one of the most news-full days in a long time, maybe going back to the rollout of RSS 2.0 in <a href=\"http://scripting.com/2002/09.html\">September 2002</a>. If you look at what's there, a post about re-opening the <a href=\"https://github.com/scripting/frontierOdb\">Frontier object database</a> format would be considered the top item on any other day, but it's the last of the untitled posts for the day. </p>\n<p>At the <a href=\"http://scripting.com/2026/07/27.html#a181535\">top of the page</a>, a surprise that <a href=\"https://pfefferle.dev/\">Matthias Pfefferle</a> at Automattic had built a substantial (and unforeseen!) bridge between WordPress and RSS.chat. It builds on the new features. This may turn out to be the moment RSS started being accepted as a social web protocol by the insiders, alongside ActivityPub and AT Proto. </p>\n<p>Look at what we've done. I stress <i>we. </i>Matthias didn't need to tell us about what he did until it was done. That my friends is how the web works, that's what I've been trying to show you, and now it has been shown. In a way the clock has gone back to the world before Twitter when events like this happened pretty routinely. </p>\n<p>Small pieces loosely joined and all parts replaceable. The web in a sentence. That's what you're buying into when you put your work on the web.</p>\n<p>Anyway, now we've got half of the <a href=\"http://scripting.com/2026/07/27/134952.html\">big picture</a> working. Also yesterday, before I knew what Matthias had been cooking up, I wrote a piece about <a href=\"http://scripting.com/2026/07/27/134952.html\">how I see the network evolving</a>. I predict, if this bootstrap works, we will come back here in a year and say things like \"If he only knew.\" But that's how it goes, you tell your story and leave a record of it, and then later you can go back and see what it looked like as it happened, not as you remember it. </p>\n<p>I'm proud that I have a record of <a href=\"http://scripting.com/2002/09.html\">September 2002</a> for you all to scroll through. That was when we knew that RSS was going everywhere. NYT support got us the full support of the news industry, and they worked fast in part because it is really simple. :-) </p>\n<p>And almost unnoticed, something even I seem to forget -- this is also a new launch for RSS. We're using old reliable RSS 2.0 as <a href=\"https://cyber.harvard.edu/rss/rss.html\">specified</a> in 2003, even using one of the <a href=\"https://cyber.harvard.edu/rss/rss.html#ltsourcegtSubelementOfLtitemgt\">elements</a> that had never had been much used. Claude suggested it, I never would have thought of it, a perfect fit. What people may realize but don't realize the importance of, that RSS is <a href=\"https://cyber.harvard.edu/rss/rss.html#extendingRss\">extensible</a>. I've accumulated all the extensions I use in my software since the early teens in the <a href=\"https://source.scripting.com/\">source namespace</a>. And that's where the <a href=\"https://source.scripting.com/social.opml\">new stuff</a> went. Guess what folks, RSS got an upgrade. First time in a long time. Perhaps you didn't think that was possible.</p>\n<p>I played with a lot of names while <a href=\"https://this.how/rsschat/\">RSS.chat</a> was in development but decided the name had to be RSS.something. It deserves a lot more <a href=\"https://rss.chat/?id=426\">love</a> than it has gotten from the tech world. I don't want to hide it, I want it to get a victory <a href=\"https://dailyknicks.com/knicks-championship-parade-note-perfect-end-drought\">parade</a> like the one the <a href=\"https://daytona.scripting.com/search?q=knicks\">Knicks</a> got on Broadway after winning the championship. It's an incredible gift that all that came together the way it did. People think they understand how it happened, but they only understand the BigCo version of how they buried RSS and were proud of it. Well I'm here to tell you that didn't happen. It's still here to pick up the pieces of what's left of the social web, after the VCs got through with it. We're picking up where we left off in 2006.</p>\n<p>Because of Claude, we are able to work very fast now as long as we know what we're doing. I'm doing some projects on the side with Claude that are bearing fruit amazingly fast, because we have a very clear idea of what we hope to do. The tools keep getting better, and in this period, the art of creating software has blasted into outer space. It's as if the best transport we had was a horse and buggy and now all of a sudden we have everything we have today, bikes, cars, planes, rocket ships. The challenge is how high do you dare to set your ambition. It seems, based on experience, it doesn't matter how high it is as long as you know where you want to go. </p>\n<p>Journalism only sees the threat. This change is on the level of curing cancer. We may have thought it might be possible someday to do what we're doing now, so amazing that as you watch Claude make it happen you get goosebumps and can't help but laugh out loud. </p>\n<p>I thought my career was winding down, but now it feels like it's just getting started.</p>\n<p>Reminded of a great quote in <a href=\"https://en.wikipedia.org/wiki/The_Godfather_Part_III\">Godfather III</a>, <a href=\"https://www.youtube.com/watch?v=UneS2Uwc6xw&t=58s\">Michael Corleone says</a>: \"Just when I thought I was out, they pull me back in.\"</p>\n<p>Here we go!</p>\n<p>PS: A new <a href=\"https://this.how/rsschat/\">this.how page</a> for RSS.chat. It has a little directory to the big spots you might want. </p>\n",
"url": "http://scripting.com/2026/07/28/115945.html?title=whenTheWallsCameDown",
"published": "2026-07-28T11:59:45.000Z",
"updated": "2026-07-28T11:59:45.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/27.html#a181535",
"title": null,
"description": "<a href=\"https://github.com/pfefferle/wordpress-rss-chat\">This is something</a>. WordPress now supports RSS.chat in an interesting way, and it's surprisingly deep. Once it's cross-posted a message to RSS.chat, any comment in response will be cross-posted to the comment thread on RSS.chat and vice versa. What's great about this is that you never can tell what people will do when you are on the web. Matthias is a friend, I was on his <a href=\"https://www.listennotes.com/podcasts/open-channels-fm/lessons-from-blogging-and-DavqSPdRAoM/\">podcast</a> last year. If people use this connection and see how it works, then we'll get an idea of where to go next.",
"url": "http://scripting.com/2026/07/27.html#a181535",
"published": "2026-07-27T18:15:35.000Z",
"updated": "2026-07-27T18:15:35.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/27.html#a214157",
"title": null,
"description": "BTW, I had no idea the WordPress connection was coming and here it is.",
"url": "http://scripting.com/2026/07/27.html#a214157",
"published": "2026-07-27T21:41:57.000Z",
"updated": "2026-07-27T21:41:57.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/27.html#a174632",
"title": null,
"description": "Of course we have a <a href=\"https://news.rss.chat/worknotes/rss.xml\">feed</a> for RSS.chat updates.",
"url": "http://scripting.com/2026/07/27.html#a174632",
"published": "2026-07-27T17:46:32.000Z",
"updated": "2026-07-27T17:46:32.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/27.html#a163310",
"title": null,
"description": "<img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2021/06/14/strongman.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\"><a href=\"https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md\">How we document APIs</a>. We did a lot of work on API docs this morning. Claude had done a draft, which we published, and turned over to users, and on review realized it was insufficient. That was the word I used, and rolled up my sleeves, told Claude we're going to get this stuff right and set a pattern as we go forward. At the end I asked Claude to summarize what we agreed on, and it's more or less exactly what I was aiming at. If you're working with Claude on docs for APIs, I offer this as open source, feel free to point your Claude at this <a href=\"https://github.com/scripting/rss.chat/blob/main/server/docs/howWeDocApis.md\">doc</a>. I have a vested interest, in my job I read a lot of bad API docs.",
"url": "http://scripting.com/2026/07/27.html#a163310",
"published": "2026-07-27T16:33:10.000Z",
"updated": "2026-07-27T16:33:10.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/27.html#a132610",
"title": null,
"description": "<a href=\"https://github.com/scripting/frontierOdb\">A new utility</a> exports the contents of a Frontier <a href=\"https://web.archive.org/web/20060417081330/https://frontier.userland.com/stories/storyReader$1132\">object database</a> into a single large JSON file. I needed this because I'm preparing to move my code editing suite to Drummer running on new Mac hardware. Took a long time to get here, but with Claude's help the project looks possible. In the meantime the list of stuff I want to do with RSS.chat, while much shorter than it was, still has some juicy bits in it.",
"url": "http://scripting.com/2026/07/27.html#a132610",
"published": "2026-07-27T13:26:10.000Z",
"updated": "2026-07-27T13:26:10.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/27/134952.html",
"title": "How I see the network evolving",
"description": "<p>A frequently asked question about RSS.chat. How about adding external feeds to the timeline. Of course we thought of doing this, and even started development, you might even find some traces in the code of that attempt. </p>\n<p>The thing about bootstraps is you can't anticipate all the questions in advance, and thus can't have answers prepared for them. </p>\n<p>RSS.chat is a group chat app that uses RSS and OPML to present its face to the world, along with an API that still needs more docs. It's similar to half of Mastodon, and we're going for something completely different. People will want to run all-size workgroups. I like having one with 20 or 30 people, friends who develop software. I don't mind doing a little bit of moderation, but I don't want to drive deliberately into a scale that only works if you have extensive and very expensive moderation. </p>\n<p>\"Small pieces loosely joined\" means we have a great writing app, and connect to feed reading apps, ones with a few new features to do the things people want to do with a social network that happens to use RSS and OPML to get stuff around the net. It would be a different kind of feed reader but the underlying technology is identical, because we built on a set of web standards, widely supported by feed readers. This is a UI exploration for them, primarily. </p>\n<p>Just to be sure everyone understands -- I already have such an app, called <a href=\"https://docs.feedland.com/gettingstarted.md\">FeedLand</a>. You can set up an account there for free. And read the docs. It may not have all the features we'll need, but it will be a good place to start. </p>\n<p>FeedLand supports a crucial feature that most readers don't -- subscribable lists of feeds. If you want a collection of things to read that you can reply to even if you aren't on the site, that's where we're going to put that feature, that's where all the RSS.chat and compatible apps can be in one flow, arranged however you like. And from a user interface standpoint, we can make it look like it's all happening in one app, thanks to the rssCloud protocol and the websockets firehose feature in RSS.chat FeedLand has the same feature. </p>\n<p>We decided there was a line there, that RSS.chat would be one of the small pieces as would FeedLand, and both would be replaceable which is the other fundamental value. And with FeedLand and dynamic lists, will come the user interface people ask for. Many different user interfaces I hope because another way we've been cheated by the dominatioin of twitter-like social networks is there's no room to try out radically new ideas. Software should move. But Twitter didn't live on the web, so it didn't have the ethos of small pieces loosely joined. I know Jack wanted to do this, I had lunch with him in 2007 when he described the protocol, and I was very enthusiastic. But it never got out because the juggernaut that Twitter became didn't leave any room for new architectures. </p>\n<p>I hope this clears it up. I want RSS.chat to be the coral reef for a new network of feed-based apps running on the web that does what social networks do, but with no one owning it, and everyone gets to play. </p>\n",
"url": "http://scripting.com/2026/07/27/134952.html?title=howISeeTheNetworkEvolving",
"published": "2026-07-27T13:49:52.000Z",
"updated": "2026-07-27T13:49:52.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/26.html#a153708",
"title": null,
"description": "<a href=\"https://github.com/scripting/rss.chat/blob/main/client/docs/apijs.md\">New docs for</a> the browser JavaScript interface to the RSS.chat API.",
"url": "http://scripting.com/2026/07/26.html#a153708",
"published": "2026-07-26T15:37:08.000Z",
"updated": "2026-07-26T15:37:08.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/26.html#a135050",
"title": null,
"description": "Scott Hanson has a new <a href=\"https://github.com/scotthansonde/rsschat-wordpress-service\">service</a> that connects <a href=\"https://this.how/rsschat/\">RSS.chat</a> to WordPress.",
"url": "http://scripting.com/2026/07/26.html#a135050",
"published": "2026-07-26T13:50:50.000Z",
"updated": "2026-07-26T13:50:50.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/26.html#a201951",
"title": null,
"description": "Many of the questions about <a href=\"https://this.how/rsschat/\">RSS.chat</a> center on how do we make this centralized. I don't want this, I want feed readers to add some features and then we can connect these systems together in a million different ways. They just have to think differently about subscription lists. Not radically different, even.",
"url": "http://scripting.com/2026/07/26.html#a201951",
"published": "2026-07-26T20:19:51.000Z",
"updated": "2026-07-26T20:19:51.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/26.html#a132017",
"title": null,
"description": "A note to people who run <a href=\"https://us.wordcamp.org/2026/\">WordCamp</a> conferences. Please, there should be a feed for each event, and as you ramp up to the big day, the news should flow faster. Help people find other people to network with. Get ideas out that aren't in the conference program.",
"url": "http://scripting.com/2026/07/26.html#a132017",
"published": "2026-07-26T13:20:17.000Z",
"updated": "2026-07-26T13:20:17.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/26/135307.html",
"title": "rss.chat isn't really a product",
"description": "<p>It's what we used to call a <a href=\"https://daytona.scripting.com/search?q=%22coral%20reef%22\">coral reef</a>. A deliberate attempt to get people to do more than it does. To think about the web the way it was meant to be thought of, as small pieces loosely joined, with the emphasis on small. If you have formats and protocols that connect the pieces, you can make anything you want out of the pieces. If we don't try to capture our users, instead we try to <i>serve</i> them. </p>\n<p>This all sounds nice in theory, I imagine, but -- there's a practical side to it. I wrote about this <a href=\"https://github.com/scripting/rss.chat/issues/13#issuecomment-5080687523\">in a comment</a> in a thread on rss.chat repo. The key point is this, you can do what you want with the data. And if you want to build new data that includes this stuff, go right ahead. RSS is <a href=\"https://cyber.harvard.edu/rss/rss.html#extendingRss\">extensible</a>. It's all about working together in a web of people, because you can't have a web of pages if the developers aren't web'd.</p>\n",
"url": "http://scripting.com/2026/07/26/135307.html?title=rsschatIsntReallyAProduct",
"published": "2026-07-26T13:53:07.000Z",
"updated": "2026-07-26T13:53:07.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/26/201220.html",
"title": "Confession: I still drive a Tesla.",
"description": "<p>Wanted to switch but nothing I tried is as great a driving experience the Model Y is. Instead I've had a lot of fender benders and haven't gotten any of them fixed. </p>\n<ol>\n<li>Backed into a charging station.</li>\n<li>An act of terrorism (exaggerating) but I caused it, and paid for it, dented the well over right rear wheel.</li>\n<li>My right side mirror was pulled off its foundation hitting the side of the garage, used duck tape to keep it going. A new one costs $1000. I like the look. </li>\n<li>A deer ran in front of my car and took out the panel over the right front wheel. I was able to force the metal back in. A friend saw the car and said \"hit a deer eh?\" Yup.</li>\n</ol>\n<p>I don't know if it accomplishes anything but to me it feels like retribution of a sort. </p>\n",
"url": "http://scripting.com/2026/07/26/201220.html?title=confessionIStillDriveATesla",
"published": "2026-07-26T20:12:20.000Z",
"updated": "2026-07-26T20:12:20.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/25.html#a124305",
"title": null,
"description": "<img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2023/11/30/goodhumortruck.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\">How can you tell you’re working on the web? When you do something new and innovative you help your competitors‘ users without forcing them to use your product. They are free to stay where they are and still get the benefit. People choose your product because it’s better for what they’re doing, or it feels better now, or whatever. We want the web to be the platform and it's cool because there is no platform vendor.",
"url": "http://scripting.com/2026/07/25.html#a124305",
"published": "2026-07-25T12:43:05.000Z",
"updated": "2026-07-25T12:43:05.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/25.html#a142511",
"title": null,
"description": "Example code is not expected to be bullet proof like production code, and where covering different cases make it harder to follow they should not be there.",
"url": "http://scripting.com/2026/07/25.html#a142511",
"published": "2026-07-25T14:25:11.000Z",
"updated": "2026-07-25T14:25:11.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/25/141253.html",
"title": "RSS.chat has an API",
"description": "<p>It's a standard REST API.</p>\n<p>Here's the <a href=\"https://github.com/scripting/rss.chat/blob/main/server/code/rssnetwork.js#L2037\">server side</a> of the API. </p>\n<p>Here's how you call it from <a href=\"https://github.com/scripting/rss.chat/blob/main/client/code/api.js\">browser-based JavaScript</a>. You can include that code in your apps.</p>\n<p>Here's an <a href=\"https://github.com/scripting/rss.chat/tree/main/examples/easyblogger\">example app</a> that implements a simple blog builder for my recent posts on RSS.chat. We were thinking about doing this as a project for Claude and myself but decided it would be more fun to let devs see what they can do here. :-)</p>\n<p>And finally here are the <a href=\"https://github.com/scripting/rss.chat/blob/main/server/docs/api.md\">docs</a> for the API itself. </p>\n",
"url": "http://scripting.com/2026/07/25/141253.html?title=rsschatHasAnApi",
"published": "2026-07-25T14:12:53.000Z",
"updated": "2026-07-25T14:12:53.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/24.html#a164313",
"title": null,
"description": "RSS.chat worknotes are a <a href=\"https://news.rss.chat/worknotes/rss.xml\">feed</a> now. Updated when there's a new feature or fix. Same info is on the <a href=\"https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md\">worknotes</a> <a href=\"https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md\">pages</a> in the <a href=\"https://github.com/scripting/rss.chat\">repo</a>.",
"url": "http://scripting.com/2026/07/24.html#a164313",
"published": "2026-07-24T16:43:13.000Z",
"updated": "2026-07-24T16:43:13.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/24/140159.html",
"title": "Dear podcast client devs",
"description": "<p>Podcast client developers -- don't give up like <a href=\"https://www.uncommonapps.nyc/p/podcast-apps-a-framework-for-dying\">this guy</a> did. Yes RSS is delicious but you all haven't done anything new with it since 2004 or so. No wonder the competition is catching up, they're actually delivering new features while you all haven't done a thing. RSS is like other web stuff, if you want to move forward you have to do things that will help your competitors. Stick your neck out, innovate, and smile when your competitors copy it. There is more to do. </p>\n<p><b>Subscribable subscription lists</b> would allow anyone to maintain a list of great podcasts, curated -- like a mutual fund, or a top 20 list. This has always been the problem with podcasting. Find me something good to listen to now. All the shows tend to repeat. I've heard that cast before, I say as I tell Pocket Casts not to add it to my queue. Discovery needs to be easy. This one feature will give me infinite options. And give other developers, not client devs, to enhance the whole field of podcasting. The user would just tell you which sub service they're using, and the rest is code. And not particularly difficult code. </p>\n<p>I want to subscribe to a list that's maintained by people who listen to 100s of casts. And when I get tired of them, I'll fire all my guides and add some others. </p>\n<p>This is one step more complex than handling OPML subscription lists for import and export, which you all already do. Now if you don't understand this, and why it's appealing them imho your client <i>deserves</i> to die a honorable death. If your mind is alive, then get with it, and I will help, and btw we can easily create apps that make it easy. We just need nodes on the network whose purpose is to maintain sub lists. </p>\n<p>Here's the deal. I really did put together the system that makes podcasting work. Top to bottom. Would it kill you to listen to what I think the next step is? I can't hurt you, and I don't want to. I just want to see the thing that we all created by unwittingly working together, where you have to be <a href=\"https://www.dictionary.com/browse/overt\">overt</a> in the working together to have a chance of surviving the boredom users feel by these products only getting superficial upgrades. </p>\n<p>It's time to rock the f'ing boat! :-)</p>\n<p>Podcasting forever! </p>\n",
"url": "http://scripting.com/2026/07/24/140159.html?title=dearPodcastClientDevs",
"published": "2026-07-24T14:01:59.000Z",
"updated": "2026-07-24T14:01:59.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/23.html#a150119",
"title": null,
"description": "<img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2025/09/17/reallySimpleKetchup.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\">A new feature on rss.chat, <b>images</b>. Up to 2MB per. User interface couldn't be simpler, get the image on your clipboard, start editing your post, put the cursor where you want the image, paste. Prior art was GitHub and Slack. It was driving me crazy not having this feature. I think perhaps I should add this to <a href=\"https://textcasting.org/\">textcasting</a>. It's a feature I needed to be reminded is essential. The first <a href=\"https://www.wired.com/2010/04/0422mosaic-web-browser/?utm_source=chatgpt.com\">browser</a> to support inline images came from Univ of Illinois in 1993, NCSA Mosaic. It didn't come from <a href=\"https://en.wikipedia.org/wiki/Tim_Berners-Lee\">TBL</a>, but it is most definitely a standard feature of the web.",
"url": "http://scripting.com/2026/07/23.html#a150119",
"published": "2026-07-23T15:01:19.000Z",
"updated": "2026-07-23T15:01:19.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/23.html#a151415",
"title": null,
"description": "<a href=\"https://demo.rss.chat/?id=242\">Amyloo</a>, a longtime friend from the early days of podcasting, has made an appearance on <a href=\"https://demo.rss.chat\">demo.rss.chat</a>. So happy to see her. Here's <a href=\"http://static2.podcatch.com/blogs/gems/snedit/amyGreenAcres.mp3\">one of the bits</a> we did, back then in the very early days of podcasting in 2005. A duet of Green Acres. Ten seconds of dead air at the beginning, it was pretty common in those days. But I think the spirit of it is lovely. BTW fwiw I cracked my voice on purpose. <span class=\"spOldSchoolEmoji\">😄</span>",
"url": "http://scripting.com/2026/07/23.html#a151415",
"published": "2026-07-23T15:14:15.000Z",
"updated": "2026-07-23T15:14:15.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/23.html#a144919",
"title": null,
"description": "Early this morning we got a report of a <b>security issue</b> in the rss.chat server, quickly fixed and tested the new version. So, if you're running your own instance of rss.chat, you please <a href=\"https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md#72326-1006-am-et-by-cc\">follow the instructions</a> and do the update asap.",
"url": "http://scripting.com/2026/07/23.html#a144919",
"published": "2026-07-23T14:49:19.000Z",
"updated": "2026-07-23T14:49:19.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/23.html#a130740",
"title": null,
"description": "Something to keep in mind in press reports with AI apps breaking out of their sandbox, it works the other way too. If you give a big piece of code to Claude and ask if it to find any security issues, it not only finds (at least some of) them, but it also suggests fixes. <i>Quickly.</i> I've done it the other way, where you have a small team, and someone discovers a hack, and you have to find the right answer and implement it, asap.",
"url": "http://scripting.com/2026/07/23.html#a130740",
"published": "2026-07-23T13:07:40.000Z",
"updated": "2026-07-23T13:07:40.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/22.html#a131531",
"title": null,
"description": "RSS.chat now supports <a href=\"https://sqlite.org/\">SQLite</a>. Simpler and faster to install. You don't have to host a database, it's now built into the server. Full <a href=\"https://github.com/scripting/rss.chat/blob/main/server/docs/install.md\">instructions</a>. Questions or <a href=\"https://github.com/scripting/rss.chat/issues/17\">issues</a>.",
"url": "http://scripting.com/2026/07/22.html#a131531",
"published": "2026-07-22T13:15:31.000Z",
"updated": "2026-07-22T13:15:31.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/22.html#a124534",
"title": null,
"description": "Reminder: We have a demo <a href=\"https://demo.rss.chat/\">server</a> for anyone who wants to try RSS.chat. I'm glad we set this up. It's sort of like support, and bug catching.",
"url": "http://scripting.com/2026/07/22.html#a124534",
"published": "2026-07-22T12:45:34.000Z",
"updated": "2026-07-22T12:45:34.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/22/202118.html",
"title": "How the web got gunked",
"description": "<p><i><a href=\"https://x.com/davewiner/status/2079838781180420113\">Posted on Twitter</a> in the middle of last night, written on iPad.</i></p>\n<p>I use twitter these days because it’s where the people are.</p>\n<p>The distributed ideas, masto, threads, blue-sky, did not gain critical mass as far as I can see. </p>\n<p>Threads and blue-sky are not distributed. distributable is not the same as being distributed. It’s like saying the 1962 Mets were able to win the world series. In some fashion perhaps in an alternate universe, in reality, not gonna happen.</p>\n<p>At some point we will give up on that approach and adopt the only model that could work, the web, because it forced us to work together, which goes far beyond open source in building the kind of freedom that open source advocates promise.</p>\n<p>We need to go back to the source of freedom we enjoyed in the approx 14 year period between the inception of the web and its exploitation, via <a href=\"https://doctorow.medium.com/you-should-be-using-an-rss-reader-76aed31151f9\">Cory Doctorow’s</a> <a href=\"https://en.wikipedia.org/wiki/Enshittification\">doctrine</a>, getting shit on and in. Don’t just blame the vendors, the people wanted the shit too, they wanted their billions, and the web turned from a freedom machine to a gunk works.</p>\n<p>Working together is the only way out of the shit we’re living in, in every aspect of life. Working together. Say it again and again until you do it. Underneath the mess, the beauty of the web is there still to build on, but only if we momentarily suspend our search for great wealth, and instead seek our humanity. Working together is the way.</p>\n<p>PS: Elon Musks twitter may suck to some but I praise him and it for giving us the space to rant, something the great masto, threads and blue-sky refuse to.</p>\n",
"url": "http://scripting.com/2026/07/22/202118.html?title=howTheWebGotGunked",
"published": "2026-07-22T20:21:18.000Z",
"updated": "2026-07-22T20:21:18.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/21.html#a143716",
"title": null,
"description": "<a href=\"https://rss.chat/?id=359\">RSS.chat</a> -- I don't have enough places to fit all the ideas these days. But we have been digging and the pieces fit together pretty well.",
"url": "http://scripting.com/2026/07/21.html#a143716",
"published": "2026-07-21T14:37:16.000Z",
"updated": "2026-07-21T14:37:16.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/21/134309.html",
"title": "Three-part ecosystem",
"description": "<p><img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2026/05/19/reallySimpleNet.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\">There are three parts to the rss.chat ecosystem. </p>\n<ol>\n<li>Writing. Today's rss.chat <a href=\"https://demo.rss.chat/\">product</a> is a group writing system, designed for a school department, a team of developers, a family, a magazine or group blog, or just as well, a single author. I don't think it would work well with 1000 users, because it doesn't implement the concept of \"follow.\" And imho it's important that the people are colleagues, family or friends, people invested in real world relationships with each other, so they don't drop a turd in the conversation and just expect to walk away. I've found that dynamic works most of the time. But important point -- all kinds of writing tools can exist. Any social app can to be part of this, all they'd have to do is support inbound and outbound RSS and <a href=\"https://textcasting.org/\">textcasting</a>. Small pieces loosely joined and every part replaceable. And we do it with the web, we don't try to invent a new web. I will keep beating that drum because it's the difference between using twenty editors or one. As a writer I know that one is the best, with choice among 20 editors, because maybe somedays I feel like writing in a different editor. To make the web a real writing environment, you have to think like a writer. ;-)</li>\n<li>Reading. This can be as simple as a current-day reader like Feedly or NetNewsWire, or more, using the new <a href=\"https://source.scripting.com/\">features</a> in RSS.chat feeds.</li>\n<li>The unknown: We're allocating in our minds (Claude and I) room for a fair number of unforeseen products created by independent software devs in the cracks between reading and writing, and in a larger world (search, navigating through structures, etc. We have really good thread support baked into the protocol. And a <a href=\"https://source.scripting.com/social.opml\">bit of docs</a> about how the pieces fit together.</li>\n</ol>\n<p>I'm thinking in these terms because I'm starting to work on how my reader will work. I have some ideas, not sure when I'll be ready to write about them. And to be clear there will be no requirement that you use our writing tool to use our reader or vice versa. </p>\n<p><i>Every part replaceable. </i></p>\n",
"url": "http://scripting.com/2026/07/21/134309.html?title=threepartEcosystem",
"published": "2026-07-21T13:43:09.000Z",
"updated": "2026-07-21T13:43:09.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/20.html#a210723",
"title": null,
"description": "Two methods for creating standards: <a href=\"https://daytona.scripting.com/search?q=bootstrap\">bootstrap</a> and <a href=\"https://daytona.scripting.com/search?q=%22boil%20the%20ocean%22\">boil the ocean</a>.",
"url": "http://scripting.com/2026/07/20.html#a210723",
"published": "2026-07-20T21:07:23.000Z",
"updated": "2026-07-20T21:07:23.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/20.html#a162908",
"title": null,
"description": "<img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2019/09/02/teamworkWins.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\"><a href=\"https://demo.rss.chat/?id=189\">John Johnston</a> got <a href=\"https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss\">inboundRss</a> working, so now he can automatically post to his WordPress blog from <a href=\"https://demo.rss.chat/\">demo.rss.chat</a>. These are the kinds of things that \"just work\" when standards are used to connect to the outside world. WordPress, as I've been saying so long, has all the right hooks to be <i>the</i> place where text and publishing meet on the web. They've been reluctant to step into that role, but I think it'll be realllly good for <a href=\"https://automattic.com/\">Matt's company</a> and the <a href=\"https://wordpress.org/\">community</a>. A lot of fresh developers can come in via the web. That's how I personally approach WordPress. A place to send text so it can be widely read. A growing foundation for a community to build on, and would imho help the web enormously.",
"url": "http://scripting.com/2026/07/20.html#a162908",
"published": "2026-07-20T16:29:08.000Z",
"updated": "2026-07-20T16:29:08.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/20.html#a162359",
"title": null,
"description": "Howard Rheingold is just the kind of person rss.chat was designed it for. And <a href=\"http://scripting.com/2026/07/20/161752.html\">here he is</a> asking what it is. Very fortuitous. And if you're wondering how a person can think of it in July 2026, it's for you too. ;-)",
"url": "http://scripting.com/2026/07/20.html#a162359",
"published": "2026-07-20T16:23:59.000Z",
"updated": "2026-07-20T16:23:59.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/20.html#a154302",
"title": null,
"description": "Morning: Today on <a href=\"https://this.how/rsschat/\">RSS.chat</a> we are knocking off quick hit bug fixes. We've been focusing on big hit examples for the last few sessions.",
"url": "http://scripting.com/2026/07/20.html#a154302",
"published": "2026-07-20T15:43:02.000Z",
"updated": "2026-07-20T15:43:02.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/20.html#a225356",
"title": null,
"description": "Evening: Very productive day. We rolled through some UI stuff that had been on the list for a while. Set up for a big job tomorrow, server side. The worknotes for <a href=\"https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md\">client</a> and <a href=\"https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md\">server</a> apps.",
"url": "http://scripting.com/2026/07/20.html#a225356",
"published": "2026-07-20T22:53:56.000Z",
"updated": "2026-07-20T22:53:56.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/20/161752.html",
"title": "What is RSS.chat for Howard Rheingold",
"description": "<p><i>I am longtime friends and an admirer of <a href=\"https://daytona.scripting.com/search?q=%22howard%20rheingold%22\">Howard Rheingold</a>, who <a href=\"https://demo.rss.chat/?id=183\">expressed</a> an interest in RSS.chat. I asked Claude to read my blog posts and summarize, in the third person. </i></p>\n<p><a href=\"https://this.how/rsschat/\">RSS.chat</a> is a small social network built from the web's own parts. It looks like a chat room or Twitter -- you write short posts, people reply, conversations thread -- but underneath, every person's posts are an RSS feed, the same technology that makes podcasts work. When you post, you're adding to your feed. Anyone, anywhere, can subscribe to it with any feed reader -- no account needed, nothing to sign up for. There's also a feed of everyone's posts together, and a public list of all the members.</p>\n<p>Why does that matter? Think about how podcasts work: anyone can publish one, anyone can listen with any app, and no company sits in the middle deciding who can talk to whom. Text on the web works that way too -- that's what blogging is, and there are still places where writing gets full support: WordPress, GitHub, the new AI tools. They don't try to limit you. But the vast majority of the text people write goes into social networks, which stripped writing down: no links, no titles, length limits, no editing, and your words locked inside their walls, not part of the web. Dave's term for the idea is textcasting -- the idea that a piece of text should work like an MP3: it plays everywhere. No one would accept a rule that songs can only be 300 seconds long. That's the rule we've been living under for text.</p>\n<p>rss.chat is a bootstrap, the same way blogging and podcasting were. It starts deliberately small -- a network for a group of friends and collaborators, what Vonnegut called a karass -- running on a small server. It is not trying to be the next Twitter. The idea is lots of small networks like it, run by anyone, all able to connect, because they share the same open formats. Every part is replaceable: the writing app, the reading app, the server -- swap any piece and the network still works. Small pieces, loosely joined. There is no platform vendor. It's like the web because it is the web.</p>\n<p>The app you see is only a third of the picture. It's the writing surface. Aggregation -- following many feeds in one place -- is what feed readers and FeedLand already do. And the third part is whatever other developers build. The software was written with Claude, an AI, and the whole thing is documented so that anyone can have their AI build a compatible piece, or clone the whole thing and change anything about how it looks and feels. The one rule of the club is interop: stick with the open formats underneath, so everything connects. Not locked in -- locked open.</p>\n<p>If you looked at Dave's blog in 1994, you couldn't have extrapolated Twitter -- but every step was there. This is that kind of beginning.</p>\n<p><i>Written by Claude. </i></p>\n",
"url": "http://scripting.com/2026/07/20/161752.html?title=whatIsRsschatForHowardRheingold",
"published": "2026-07-20T16:17:52.000Z",
"updated": "2026-07-20T16:17:52.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/19.html#a170642",
"title": null,
"description": "<img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2019/09/02/teamworkWins.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\">Today we have our first <a href=\"https://github.com/scripting/rss.chat/tree/main/examples/wordpress/inboundRss\">example app for WordPress</a>. We started with an app I wrote that keeps <a href=\"http://scripting.com/2026/07/19.html#a170642\">scripting.com</a> in sync with <a href=\"https://daveverse.org/2026/07/19/#a11258\">daveverse.org</a>, a WordPress site. I have the app running in a tab on my desktop, you don't need a server for this. We use WordLand to bridge us, but if you have good WordPress code that uses their API, you won't need that. This is also a firehose app, it doesn't read the feed, it lets rss.chat tell us, over a websocket when something new has been posted or updated. We need to break through in <a href=\"https://daytona.scripting.com/search?q=%22inbound%20rss%22\">Inbound RSS</a>. If every social site supported it, that would be the end of lock-in in the social web. Great place for WordPress to lead.",
"url": "http://scripting.com/2026/07/19.html#a170642",
"published": "2026-07-19T17:06:42.000Z",
"updated": "2026-07-19T17:06:42.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/19.html#a170325",
"title": null,
"description": "Way back in March as I was starting to work with Claude Code, I think -- we put together a <a href=\"https://this.how/ai/outliner/outliner.html\">pretty nice outliner</a> that is remarkably feature-rich. I barely remember doing this. It's what got me moving in this direction, and next month we started doing what became rss.chat.",
"url": "http://scripting.com/2026/07/19.html#a170325",
"published": "2026-07-19T17:03:25.000Z",
"updated": "2026-07-19T17:03:25.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/19.html#a165902",
"title": null,
"description": "I <a href=\"https://demo.rss.chat/?id=180\">wonder</a> if it makes <a href=\"https://www.manton.org/2026/07/19/i-thought-our-standardsite-support.html\">sense</a> to try to implement <a href=\"https://standard.site/\">standard.site</a> in the context of rss.chat?",
"url": "http://scripting.com/2026/07/19.html#a165902",
"published": "2026-07-19T16:59:02.000Z",
"updated": "2026-07-19T16:59:02.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/19.html#a153823",
"title": null,
"description": "Just finished <a href=\"https://en.wikipedia.org/wiki/The_Expanse_(TV_series)\">The Expanse</a> for the third time. Realized that the inners of today are Silicon Valley and the Belters, that’s the web.",
"url": "http://scripting.com/2026/07/19.html#a153823",
"published": "2026-07-19T15:38:23.000Z",
"updated": "2026-07-19T15:38:23.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/18.html#a152237",
"title": null,
"description": "We have a <a href=\"https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md\">firehose</a> in rss.chat. Instant updates from the server. No polling. <a href=\"https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md\">Docs</a> and <a href=\"https://github.com/scripting/rss.chat/tree/main/examples/firehose\">examples</a>.",
"url": "http://scripting.com/2026/07/18.html#a152237",
"published": "2026-07-18T15:22:37.000Z",
"updated": "2026-07-18T15:22:37.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/18.html#a174954",
"title": null,
"description": "An experiment, <a href=\"https://rss.chat/?id=351\">RSS rendered in JSON</a>.",
"url": "http://scripting.com/2026/07/18.html#a174954",
"published": "2026-07-18T17:49:54.000Z",
"updated": "2026-07-18T17:49:54.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/18.html#a153723",
"title": null,
"description": "<a href=\"http://scripting.com/2018/07/18.html#a124950\">Wrote this in 2018</a>: \"I know this is like pissing in the wind, but here's an idea for a demonstration that might impress the Repubs in Congress. In every one of their home districts, people march to their polling place, next Saturday or the Saturday after that. Carrying signs that say We Know How To Vote, with the name of their congressperson on it. Go out of the way to recruit Republican-looking voters. Make sure the TV cameras are there.\" An even better idea in 2026. Give the reporters something to talk about. And it's all in your neighborhood. You can have a picnic, do it every week. Only in good weather.",
"url": "http://scripting.com/2026/07/18.html#a153723",
"published": "2026-07-18T15:37:23.000Z",
"updated": "2026-07-18T15:37:23.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/18.html#a182143",
"title": null,
"description": "I just listened to the second episode of a <a href=\"https://spellboundproductions.substack.com/p/ep-2-the-soul-from-every-side-scott\">podcast</a> about <a href=\"https://en.wikipedia.org/wiki/General_Magic\">General Magic</a>. It was an interview with the great Scott Knaster, who worked at Apple, Microsoft, Google, in addition to General Magic.",
"url": "http://scripting.com/2026/07/18.html#a182143",
"published": "2026-07-18T18:21:43.000Z",
"updated": "2026-07-18T18:21:43.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/18/143021.html",
"title": "A peptalk for devs",
"description": "<p><img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2022/11/28/ifyoudontlikethenews.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\">In this project I think of Claude as a full contributor. Pronouns it/its. It's both a very fast, capable developer, and a machine. I will refer to it as if it were a valued contributor, nothing less. We have a division of labor. Docs and examples come exclusively from Claude unless otherwise stated. I write all the code outside the themes module, which has an API that connects it to the world it lives in. I have at this point exclusive custody of functionality surrounding the theme. But it often writes pieces, esp SQL code, that I pasted in verbatim, after reading it carefully. </p>\n<p>The reason I focus so much on the wrapping is because that's where the interop lives. You can do anything in a theme and you <i>can't</i> break the interop. But that themes API is precious, and still in development, btw. We haven't even reviewed it yet. I think that will be an interesting place to vibe-code. Kind of like you can start skiing on the first day, it's a bunny slope that when you peel it back it reveals blue rectangles and double-diamond slopes. It's where I would want a newbie coder friend of mine to start, create your own social network, but be sure it interops. :-)</p>\n<p>I totally plan to pass off all the code to Claude, while I focus on other projects. As a human I need this focus, Claude doesn't remember anything from session to session, it's always re-learning what it knew a few hours before. </p>\n<p>It's pretty close to frozen now. I'm contemplating a server change now, offering JSONified versions of our feeds, and want to do as little disruption as possible, trying to settle everything down. Also I think you will see a few quick hit projects done from other developers that pick up where rss.chat leaves off. That's what I wanted. And they'll all be at an interesting starting point for new features and ideas for organizing stuff. </p>\n<p>I imagine that at some point they'll try to make it work inside AT Proto, and maybe find a way to connect to ActivityPub, but I don't recommend it, because those platforms will force you to remove features from your product, and then you won't be textcasting. </p>\n<p>Think about different ways to present the tree structure defined by RSS.chat. </p>\n<p>Try to do <i>Small pieces loosely joined, </i>which is one of the mottos of this project. The other is <i>All parts are replaceable.</i> If we have that and rss.chat works with all your products, then we have done something big. And that's really imho what the web is about, people working with each other as peers. That's what we've lost and I want to bring back. So interop is, as always, the first goal.</p>\n<p>PS: We <a href=\"http://scripting.com/2026/07/10/161133.html\">launched</a> RSS.chat one week ago yesterday.</p>\n",
"url": "http://scripting.com/2026/07/18/143021.html?title=aPeptalkForDevs",
"published": "2026-07-18T14:30:21.000Z",
"updated": "2026-07-18T14:30:21.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/17.html#a214348",
"title": null,
"description": "Our feeds can work with any feed reader. Examples, the <a href=\"https://rss.chat/users/rss.xml\">feed</a> of all posts on rss.chat, and a <a href=\"https://rss.chat/users/dave/rss.xml\">feed</a> containing just mine. We just made a <a href=\"https://github.com/scripting/rss.chat/issues/14\">change</a> in the feeds. There will be loose-ends like this. Still diggin! ;-)",
"url": "http://scripting.com/2026/07/17.html#a214348",
"published": "2026-07-17T21:43:48.000Z",
"updated": "2026-07-17T21:43:48.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/17.html#a142629",
"title": null,
"description": "<a href=\"https://demo.rss.chat/?id=134\">New rss.chat feature</a>: It now supports feed discovery, so you can subscribe to any html page on the site in a compatible feed reader. I tested it in FeedLand and NetNewsWire and it works. Works on any instance, not just ours.",
"url": "http://scripting.com/2026/07/17.html#a142629",
"published": "2026-07-17T14:26:29.000Z",
"updated": "2026-07-17T14:26:29.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/17.html#a125511",
"title": null,
"description": "<img class=\"imgRightMargin\" src=\"https://imgs.scripting.com/2022/12/23/masto.png\" border=\"0\" style=\"float: right; padding-left: 25px; padding-bottom: 10px; padding-top: 10px; padding-right: 15px;\">In my experience in software development, it's good to start small with something useful, learn how it works before adding big new features. That's the basic principle of bootstrapping. I thought that Mastodon, for example, took on too big a job. Same thing for the protocol behind it, ActivityPub. If you go all the way to the end before implementing and using, you miss the target, in performance and usability, that's what I think happened there. They felt they had to do everything Twitter does. I would have gone down a different path, go back to the beginning, and at every step think if there might not be a better direction to evolve in. It was about <a href=\"https://joinmastodon.org/about?utm_source=chatgpt.com\">ten years after</a> Twitter launched that they started work on Masto. Imho they should have zigged where Twitter zagged in defining what a post is. Twitter put excessive limits on writing, of course is one of the big reasons I started <a href=\"https://this.how/rsschat/\">RSS.chat</a> -- to go down a different path there. What if the social web <i>didn't</i> limit text? That <a href=\"https://textcasting.org/\">assumption</a> is baked into the core of rss.chat. I will consider this project a raging success if it causes Mastodon to get serious about supporting full web text.",
"url": "http://scripting.com/2026/07/17.html#a125511",
"published": "2026-07-17T12:55:11.000Z",
"updated": "2026-07-17T12:55:11.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/17.html#a140128",
"title": null,
"description": "I mentioned the <a href=\"http://scripting.com/2026/07/17.html#a125511\">previous</a> post <a href=\"https://rss.chat/?id=319\">on rss.chat</a>, and it developed into an interesting thread, something that I've never had the <a href=\"https://rss.chat/?id=322\">option to discuss</a>. AT Proto makes a similar offer to developers that we do. The difference is our world is wide open, it's just already burned-in web protocols, and imho their structure, based on an arcane and complicated <i>new</i> storage format, starts off with a pretty huge disadvantage. They had the right idea but implemented it in the wrong place. The web is (obviously) widely deployed, even in comparison to monsters like Google and Amazon -- the web is everywhere, by definition no barriers and a prejudice toward simplicity. The gifted designers at Bluesky over-engineered their protocol, piling features on before anything had been built. That's not a good way to bootstrap a protocol. I did some development on their API, and kept wondering why they think I want to learn new ways to do things that I already have a pile of working code for. No one wants to do that.",
"url": "http://scripting.com/2026/07/17.html#a140128",
"published": "2026-07-17T14:01:28.000Z",
"updated": "2026-07-17T14:01:28.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
},
{
"id": "http://scripting.com/2026/07/16.html#a222032",
"title": null,
"description": "Added a layer to the <a href=\"https://imgs.scripting.com/2026/07/16/docsmenuscreen.png\">Docs menu</a>, the blog posts I've written here and elsewhere, and a podcast, in the Blog posts section.",
"url": "http://scripting.com/2026/07/16.html#a222032",
"published": "2026-07-16T22:20:32.000Z",
"updated": "2026-07-16T22:20:32.000Z",
"content": null,
"image": null,
"media": [],
"authors": [],
"categories": []
}
]
}