<?xml version="1.0" encoding="UTF-8"?>
<!-- RSS generated by rssnet v0.5.16 on Wed, 01 Jul 2026 16:07:55 GMT -->
<rss version="2.0" xmlns:source="https://source.scripting.com/">
	<channel>
		<title>Dave Winer</title>
		<link>http://scripting.com/</link>
		<description>I'm a believer I couldn't leave her if I tried. Bah do dah do.</description>
		<pubDate>Wed, 01 Jul 2026 16:06:56 GMT</pubDate>
		<language>en-us</language>
		<generator>rssnet v0.5.16</generator>
		<docs>http://cyber.law.harvard.edu/rss/rss.html</docs>
		<lastBuildDate>Wed, 01 Jul 2026 16:07:55 GMT</lastBuildDate>
		<cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post" />
		<image>
			<title>Dave Winer</title>
			<url>https://imgs.scripting.com/2026/06/13/reallySimpleBasketball.png</url>
			<link>http://scripting.com/</link>
			<description>I'm a believer I couldn't leave her if I tried. Bah do dah do.</description>
			</image>
		<source:localTime>Wed, July 1, 2026 12:07 PM EDT</source:localTime>
		<item>
			<title>A message for JY</title>
			<description>&lt;p&gt;A test post before I take a break. ;-)&lt;/p&gt;&lt;p&gt;See ya in a bit. It's freaking hot here JY for what it's worth.&lt;/p&gt;&lt;p&gt;Not as hot as it was for you in France, bonjour.&lt;/p&gt;&lt;p&gt;S'il vous plait.&lt;/p&gt;</description>
			<pubDate>Wed, 01 Jul 2026 16:06:56 GMT</pubDate>
			<guid>https://rss.chat/?id=152</guid>
			<source:markdown>A test post before I take a break. ;-)&#10;&#10;See ya in a bit. It's freaking hot here JY for what it's worth.&#10;&#10;Not as hot as it was for you in France, bonjour.&#10;&#10;S'il vous plait.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Testing some new code</title>
			<description>&lt;p&gt;I'm testing a new feature.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We're now tracking how many times a user's prefs change, overall and in the last day.&lt;/p&gt;&lt;p&gt;When you type in the editor, when you pause, we save a copy.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It gives us a rough idea of how much people are using it, if they are logged in.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Wed, 01 Jul 2026 15:21:12 GMT</pubDate>
			<guid>https://rss.chat/?id=151</guid>
			<source:markdown>I'm testing a new feature.&#10;&#10;We're now tracking how many times a user's prefs change, overall and in the last day.&#10;&#10;When you type in the editor, when you pause, we save a copy.&#10;&#10;It gives us a rough idea of how much people are using it, if they are logged in.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;We just started doing both those things, and then the requests seem to have stopped. ;-)&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Tue, 30 Jun 2026 18:04:59 GMT</pubDate>
			<guid>https://rss.chat/?id=149</guid>
			<source:markdown>We just started doing both those things, and then the requests seem to have stopped. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=148</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;We don't have docs for that yet.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We're still getting our docs act together.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Turns out there are versions of Claude that are better at writing code but suck at writing docs, and vice versa. You're supposed to be able to switch modes, but when I did that it turned into a coding idiot.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I want it to write perfect docs as soon as a feature is done and have it on the repo quickly.&lt;/p&gt;&lt;p&gt;Not there yet. Sorry -- but we do have the firehose, using it.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Tue, 30 Jun 2026 17:46:00 GMT</pubDate>
			<guid>https://rss.chat/?id=147</guid>
			<source:markdown>We don't have docs for that yet.&#10;&#10;We're still getting our docs act together.&#10;&#10;Turns out there are versions of Claude that are better at writing code but suck at writing docs, and vice versa. You're supposed to be able to switch modes, but when I did that it turned into a coding idiot.&#10;&#10;I want it to write perfect docs as soon as a feature is done and have it on the repo quickly.&#10;&#10;Not there yet. Sorry -- but we do have the firehose, using it.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=144</source:inReplyTo>
			</item>
		<item>
			<title>Help us find the server error</title>
			<description>&lt;p&gt;We're seeing an error in our server log here, but we can't figure out how it's happening.&amp;nbsp;&lt;/p&gt;&lt;p&gt;As we review all the code, and Claude is really good at that, there's no way we could be generating the call that is showing the error message.&lt;/p&gt;&lt;p&gt;It isn't happening often, and it could be someone with a script trying something out, and that's fine, but we'd like to know what's happening on the other end.&lt;/p&gt;&lt;p&gt;The call is /getitembyguid, which takes two params, a screenname, which is undefined if you're not signed in, and guid, which can't be undefined, but that's what we're seeing.&lt;/p&gt;&lt;p&gt;Since we don't know what software they're using, I can't say what the error will look like on your system.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I suppose there's a remote possibility that it was an error we fixed in an old version of the software, but to make that impossible I added a cache confuser to the code that includes each file, to be sure it isn't getting an old cached version of each file.&lt;/p&gt;&lt;p&gt;One thing we know is the person is not logged in but you can read everything on this site without being logged in. So there's a chance, if this is a human, that they will see this post. ;-)&lt;/p&gt;&lt;p&gt;If so, please let us know, send an email to dave.winer@gmail.com.&lt;/p&gt;</description>
			<pubDate>Tue, 30 Jun 2026 17:28:28 GMT</pubDate>
			<guid>https://rss.chat/?id=145</guid>
			<source:markdown>We're seeing an error in our server log here, but we can't figure out how it's happening.&#10;&#10;As we review all the code, and Claude is really good at that, there's no way we could be generating the call that is showing the error message.&#10;&#10;It isn't happening often, and it could be someone with a script trying something out, and that's fine, but we'd like to know what's happening on the other end.&#10;&#10;The call is /getitembyguid, which takes two params, a screenname, which is undefined if you're not signed in, and guid, which can't be undefined, but that's what we're seeing.&#10;&#10;Since we don't know what software they're using, I can't say what the error will look like on your system.&#10;&#10;I suppose there's a remote possibility that it was an error we fixed in an old version of the software, but to make that impossible I added a cache confuser to the code that includes each file, to be sure it isn't getting an old cached version of each file.&#10;&#10;One thing we know is the person is not logged in but you can read everything on this site without being logged in. So there's a chance, if this is a human, that they will see this post. ;-)&#10;&#10;If so, please let us know, send an email to dave.winer@gmail.com.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>How our docs publishing flows</title>
			<description>&lt;p&gt;Good morning sports fans!&lt;/p&gt;&lt;p&gt;Spent yesterday getting our docs production system working.&lt;/p&gt;&lt;p&gt;It's all going to be in one big outline that's shared between myself and Claude.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We can both make edits, I use Electric Drummer, and it uses its own magic, and when it's time to update the repo, I run a script in Frontier, which loads the outline in, and uses my publishing system to push it to GitHub.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I'm getting to the point where there isn't a whole lot left of the Frontier-based system that I'm still using.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Still have a long todo list, another outline, shared with Claude.&lt;/p&gt;&lt;p&gt;If you have any questions, or just want to say hi, reply to or like this post.&lt;/p&gt;</description>
			<pubDate>Tue, 30 Jun 2026 11:46:55 GMT</pubDate>
			<guid>https://rss.chat/?id=143</guid>
			<source:markdown>Good morning sports fans!&#10;&#10;Spent yesterday getting our docs production system working.&#10;&#10;It's all going to be in one big outline that's shared between myself and Claude.&#10;&#10;We can both make edits, I use Electric Drummer, and it uses its own magic, and when it's time to update the repo, I run a script in Frontier, which loads the outline in, and uses my publishing system to push it to GitHub.&#10;&#10;I'm getting to the point where there isn't a whole lot left of the Frontier-based system that I'm still using.&#10;&#10;Still have a long todo list, another outline, shared with Claude.&#10;&#10;If you have any questions, or just want to say hi, reply to or like this post.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Debugging a server issue</title>
			<description>&lt;p&gt;Building a new system for editing user and developer docs collaboratively in OPML.&lt;/p&gt;&lt;p&gt;And we have a bug somewhere in the software, sending a bad parameter to a server endpoint named&amp;nbsp;&lt;span style=&quot;color: var(--text-color, #0f1419); font-family: var(--font, &amp;quot;Ubuntu&amp;quot;, -apple-system, &amp;quot;Segoe UI&amp;quot;, sans-serif); font-size: var(--text-size, 16px);&quot;&gt;getItemByGuid. It takes two params, a screenname and a guid.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color: var(--text-color, #0f1419); font-family: var(--font, &amp;quot;Ubuntu&amp;quot;, -apple-system, &amp;quot;Segoe UI&amp;quot;, sans-serif); font-size: var(--text-size, 16px);&quot;&gt;I let Claude make a list of all the calls to this function in the client, and there are a few.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color: var(--text-color, #0f1419); font-family: var(--font, &amp;quot;Ubuntu&amp;quot;, -apple-system, &amp;quot;Segoe UI&amp;quot;, sans-serif); font-size: var(--text-size, 16px);&quot;&gt;But it doesn't seem possible that they would pass an undefined guid value.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color: var(--text-color, #0f1419); font-family: var(--font, &amp;quot;Ubuntu&amp;quot;, -apple-system, &amp;quot;Segoe UI&amp;quot;, sans-serif); font-size: var(--text-size, 16px);&quot;&gt;But the error message on the server keeps popping up. One theory is this is a not-logged-in person, which is totally legal, you can read the site without being logged in.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color: var(--text-color, #0f1419); font-family: var(--font, &amp;quot;Ubuntu&amp;quot;, -apple-system, &amp;quot;Segoe UI&amp;quot;, sans-serif); font-size: var(--text-size, 16px);&quot;&gt;But now with the debugging code we should be able to eliminate more possibilities.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;color: var(--text-color, #0f1419); font-family: var(--font, &amp;quot;Ubuntu&amp;quot;, -apple-system, &amp;quot;Segoe UI&amp;quot;, sans-serif); font-size: var(--text-size, 16px);&quot;&gt;This is something Claude usually excels at but we've been trying to find this one for 24 hours or so, but getting good work done anyway. ;-)&lt;/span&gt;&lt;/p&gt;</description>
			<pubDate>Mon, 29 Jun 2026 21:40:34 GMT</pubDate>
			<guid>https://rss.chat/?id=142</guid>
			<source:markdown>Building a new system for editing user and developer docs collaboratively in OPML.&#10;&#10;And we have a bug somewhere in the software, sending a bad parameter to a server endpoint named getItemByGuid. It takes two params, a screenname and a guid.&#10;&#10;I let Claude make a list of all the calls to this function in the client, and there are a few.&#10;&#10;But it doesn't seem possible that they would pass an undefined guid value.&#10;&#10;But the error message on the server keeps popping up. One theory is this is a not-logged-in person, which is totally legal, you can read the site without being logged in.&#10;&#10;But now with the debugging code we should be able to eliminate more possibilities.&#10;&#10;This is something Claude usually excels at but we've been trying to find this one for 24 hours or so, but getting good work done anyway. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Getting the line spacing right for lists</title>
			<description>&lt;p&gt;This is a test.&amp;nbsp;&lt;/p&gt;&lt;p&gt;A list of states.&lt;/p&gt;&lt;ol&gt;&lt;li&gt;Montana&lt;/li&gt;&lt;li&gt;Wisconsin&lt;/li&gt;&lt;li&gt;Iowa&lt;/li&gt;&lt;li&gt;Idaho&lt;/li&gt;&lt;li&gt;Mississippi&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;That was a list.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 29 Jun 2026 15:48:14 GMT</pubDate>
			<guid>https://rss.chat/?id=141</guid>
			<source:markdown>This is a test.&#10;&#10;A list of states.&#10;&#10;1.  Montana&#10;2.  Wisconsin&#10;3.  Iowa&#10;4.  Idaho&#10;5.  Mississippi&#10;&#10;That was a list.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Links cleanup</title>
			<description>&lt;p&gt;Just did a major cleanup of links in the user interface. Now they all use the browser's URL stack, so when you go somewhere, the Back button will take you back.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We also have a fully ergonomic Home button, the previous version did a window.open to create a new tab that had the top level timeline. But now it should work.&amp;nbsp;&lt;/p&gt;&lt;p&gt;The three places to look for changes.&amp;nbsp;&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&lt;strong&gt;Post title&lt;/strong&gt;&amp;nbsp;→ opens the story&amp;nbsp;&lt;strong&gt;in place&lt;/strong&gt;&amp;nbsp;instead of a new tab — but only when the title is the post's own permalink. A title the writer pointed at an external article still opens in a new tab.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Timestamp&lt;/strong&gt;&amp;nbsp;(&quot;6 hours&quot;) → opens the story&amp;nbsp;&lt;strong&gt;in place&lt;/strong&gt;&amp;nbsp;instead of a new tab.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Home icon&lt;/strong&gt;&amp;nbsp;→ jumps to the&amp;nbsp;&lt;strong&gt;top of the main timeline&lt;/strong&gt;&amp;nbsp;in place (clearing any hoist), instead of opening home in a new tab.&lt;/li&gt;&lt;/ol&gt;</description>
			<pubDate>Mon, 29 Jun 2026 14:34:20 GMT</pubDate>
			<guid>https://rss.chat/?id=140</guid>
			<source:markdown>Just did a major cleanup of links in the user interface. Now they all use the browser's URL stack, so when you go somewhere, the Back button will take you back.&#10;&#10;We also have a fully ergonomic Home button, the previous version did a window.open to create a new tab that had the top level timeline. But now it should work.&#10;&#10;The three places to look for changes.&#10;&#10;1.  **Post title** → opens the story **in place** instead of a new tab — but only when the title is the post's own permalink. A title the writer pointed at an external article still opens in a new tab.&#10;2.  **Timestamp** (&quot;6 hours&quot;) → opens the story **in place** instead of a new tab.&#10;3.  **Home icon** → jumps to the **top of the main timeline** in place (clearing any hoist), instead of opening home in a new tab.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>The rss.chat firehose</title>
			<description>&lt;p&gt;Observation, each instance of rss.chat has a firehose.&lt;/p&gt;&lt;p&gt;We built a new notification method from scratch. There was an issue with the one in FeedLand, we don't have it here.&amp;nbsp;&lt;/p&gt;&lt;p&gt;But the records that cross the wire are patterned after FeedLand's records. We've really embraced prior art as a design method.&lt;/p&gt;&lt;p&gt;When someone emulates our firehose, which I hope happens, I hope this time they don't gratuitously reinvent names for things. Makes interop so much harder. :-)&lt;/p&gt;</description>
			<pubDate>Mon, 29 Jun 2026 13:21:50 GMT</pubDate>
			<guid>https://rss.chat/?id=137</guid>
			<source:markdown>Observation, each instance of rss.chat has a firehose.&#10;&#10;We built a new notification method from scratch. There was an issue with the one in FeedLand, we don't have it here.&#10;&#10;But the records that cross the wire are patterned after FeedLand's records. We've really embraced prior art as a design method.&#10;&#10;When someone emulates our firehose, which I hope happens, I hope this time they don't gratuitously reinvent names for things. Makes interop so much harder. :-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Good morning sports fans!</title>
			<description>&lt;p&gt;Your buddy Dave is here welcoming you to another hot summer week in RSS.chat land.&lt;/p&gt;&lt;p&gt;There's a bug in the system it crashes the server in an easy way to protect against. (No longer crashes, added debugging code.)&lt;/p&gt;&lt;p&gt;But it should be easy to find.&lt;/p&gt;&lt;p&gt;Also we've got a process for Claude to write docs for features as soon as the feature is finished enough to have docs. This product is going to have excellent docs. I will post a link to where you can review the docs, here, when they're ready. (It's one of the next things I'm doing.)&lt;/p&gt;&lt;p&gt;The heat wave hasn't hit us here in the Catskills yet. &lt;i&gt;Still diggin!&lt;/i&gt;&lt;/p&gt;</description>
			<pubDate>Mon, 29 Jun 2026 12:20:22 GMT</pubDate>
			<guid>https://rss.chat/?id=136</guid>
			<source:markdown>Your buddy Dave is here welcoming you to another hot summer week in RSS.chat land.&#10;&#10;There's a bug in the system it crashes the server in an easy way to protect against. (No longer crashes, added debugging code.)&#10;&#10;But it should be easy to find.&#10;&#10;Also we've got a process for Claude to write docs for features as soon as the feature is finished enough to have docs. This product is going to have excellent docs. I will post a link to where you can review the docs, here, when they're ready. (It's one of the next things I'm doing.)&#10;&#10;The heat wave hasn't hit us here in the Catskills yet. _Still diggin!_</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>About command</title>
			<description>&lt;p&gt;There's a new &lt;em&gt;About rss.chat&lt;/em&gt; command in the System menu, at the right edge of the menubar.&lt;/p&gt;&#10;&#10;&lt;p&gt;It has the name of the app, its address, the current theme, and versions for the app and the theme. The latter is exclusively written by Claude, our deal is I take care of the container, that's where the interop is crucial, and I already have good client and server code for that. The theme is where the user interface lives. It's all connected by APIs, so the theme will be replaceable. Right now twitter is the only theme we offer.&amp;nbsp;&lt;/p&gt;&#10;&#10;&lt;p&gt;Here's a &lt;a href=&quot;https://imgs.scripting.com/2026/06/28/about.png&quot;&gt;screen shot&lt;/a&gt;.&lt;/p&gt;</description>
			<pubDate>Sun, 28 Jun 2026 14:16:33 GMT</pubDate>
			<guid>https://rss.chat/?id=135</guid>
			<source:markdown>There's a new _About rss.chat_ command in the System menu, at the right edge of the menubar.&#10;&#10;It has the name of the app, its address, the current theme, and versions for the app and the theme. The latter is exclusively written by Claude, our deal is I take care of the container, that's where the interop is crucial, and I already have good client and server code for that. The theme is where the user interface lives. It's all connected by APIs, so the theme will be replaceable. Right now twitter is the only theme we offer.&#10;&#10;Here's a [screen shot](https://imgs.scripting.com/2026/06/28/about.png).</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>What is rss.chat?</title>
			<description>&lt;p&gt;This is a new kind of social network. There's no lock-in here. Every user is represented by an RSS feed. You can subscribe to the feed in any feed reader, or even another social web app that understands RSS feeds. It should work really well with micro.blog for example.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It it is a textcasting app. It supports text as it was meant to work on the web. No character limits, you can edit your posts, they can have titles (or not). We want you to be able to share your writing with any service that's on the web. If they have a character limit, that's their problem. This app is a benchmark, if another app says they're on the web, see if you can follow my feed there. If not, they're not telling the truth.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Being &quot;on the web&quot; means more than you can read it in a web browser.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sun, 28 Jun 2026 12:03:14 GMT</pubDate>
			<guid>https://rss.chat/?id=134</guid>
			<source:markdown>This is a new kind of social network. There's no lock-in here. Every user is represented by an RSS feed. You can subscribe to the feed in any feed reader, or even another social web app that understands RSS feeds. It should work really well with micro.blog for example.&#10;&#10;It it is a textcasting app. It supports text as it was meant to work on the web. No character limits, you can edit your posts, they can have titles (or not). We want you to be able to share your writing with any service that's on the web. If they have a character limit, that's their problem. This app is a benchmark, if another app says they're on the web, see if you can follow my feed there. If not, they're not telling the truth.&#10;&#10;Being &quot;on the web&quot; means more than you can read it in a web browser.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>NBBs in politics</title>
			<description>Listening to a discussion on WBUR about how the Democrats don't do social media well. True! But they get every idea wrong. AOC is a NBB. That's why she's so good at it. What this means is for the foreseeable future our political leaders are going to be natural at this form of relating to people. A young Chuck Schumer or Elizabeth Warren wouldn't be any good at this, there are plenty of people AOC's age who have no idea what to say, they never get angry enough about something to try to make a difference. NBB's are a rare breed. You have to find them and recruit them.</description>
			<pubDate>Sun, 28 Jun 2026 11:59:10 GMT</pubDate>
			<guid>https://rss.chat/?id=133</guid>
			<source:markdown>Listening to a discussion on WBUR about how the Democrats don't do social media well. True! But they get every idea wrong. AOC is a NBB. That's why she's so good at it. What this means is for the foreseeable future our political leaders are going to be natural at this form of relating to people. A young Chuck Schumer or Elizabeth Warren wouldn't be any good at this, there are plenty of people AOC's age who have no idea what to say, they never get angry enough about something to try to make a difference. NBB's are a rare breed. You have to find them and recruit them.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;Gotta get some users here. But I don't want to make a big announcement, and I only want people in this group that I want to hang out with. The idea here is not following or following, rather it's groups of people gathered by the host, by invite, and at the pleasure of.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sun, 28 Jun 2026 11:52:54 GMT</pubDate>
			<guid>https://rss.chat/?id=132</guid>
			<source:markdown>Gotta get some users here. But I don't want to make a big announcement, and I only want people in this group that I want to hang out with. The idea here is not following or following, rather it's groups of people gathered by the host, by invite, and at the pleasure of.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>Lake Katrine</description>
			<pubDate>Sat, 27 Jun 2026 22:17:13 GMT</pubDate>
			<guid>https://rss.chat/?id=131</guid>
			<source:markdown>Lake Katrine</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=128</source:inReplyTo>
			</item>
		<item>
			<description>Saugerties</description>
			<pubDate>Sat, 27 Jun 2026 22:16:49 GMT</pubDate>
			<guid>https://rss.chat/?id=130</guid>
			<source:markdown>Saugerties</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=128</source:inReplyTo>
			</item>
		<item>
			<description>Kingston</description>
			<pubDate>Sat, 27 Jun 2026 22:16:01 GMT</pubDate>
			<guid>https://rss.chat/?id=129</guid>
			<source:markdown>Kingston</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=128</source:inReplyTo>
			</item>
		<item>
			<description>Ulster County</description>
			<pubDate>Sat, 27 Jun 2026 22:15:53 GMT</pubDate>
			<guid>https://rss.chat/?id=128</guid>
			<source:markdown>Ulster County</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=127</source:inReplyTo>
			</item>
		<item>
			<description>New York</description>
			<pubDate>Sat, 27 Jun 2026 22:12:21 GMT</pubDate>
			<guid>https://rss.chat/?id=127</guid>
			<source:markdown>New York</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=122</source:inReplyTo>
			</item>
		<item>
			<description>Chapel Hill</description>
			<pubDate>Sat, 27 Jun 2026 22:05:03 GMT</pubDate>
			<guid>https://rss.chat/?id=126</guid>
			<source:markdown>Chapel Hill</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=124</source:inReplyTo>
			</item>
		<item>
			<description>Maryland</description>
			<pubDate>Sat, 27 Jun 2026 22:04:49 GMT</pubDate>
			<guid>https://rss.chat/?id=125</guid>
			<source:markdown>Maryland</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=122</source:inReplyTo>
			</item>
		<item>
			<description>North Carolina</description>
			<pubDate>Sat, 27 Jun 2026 22:04:39 GMT</pubDate>
			<guid>https://rss.chat/?id=124</guid>
			<source:markdown>North Carolina</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=122</source:inReplyTo>
			</item>
		<item>
			<description>Alabama</description>
			<pubDate>Sat, 27 Jun 2026 22:04:28 GMT</pubDate>
			<guid>https://rss.chat/?id=123</guid>
			<source:markdown>Alabama</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=122</source:inReplyTo>
			</item>
		<item>
			<description>Eastern states</description>
			<pubDate>Sat, 27 Jun 2026 22:04:22 GMT</pubDate>
			<guid>https://rss.chat/?id=122</guid>
			<source:markdown>Eastern states</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=121</source:inReplyTo>
			</item>
		<item>
			<title>Testing ground for hoist</title>
			<description>I'm going to make a mini states outline here.</description>
			<pubDate>Sat, 27 Jun 2026 22:04:12 GMT</pubDate>
			<guid>https://rss.chat/?id=121</guid>
			<source:markdown>I'm going to make a mini states outline here.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Hoisting is in</title>
			<description>&lt;div&gt;Had an incredible day programming with Claude today.&lt;/div&gt;&lt;div&gt;Tried out all kinds of ways of reading the stuff in the timeline, and the one that worked best was hoist and dehoist.&lt;/div&gt;&lt;div&gt;When you want to focus on one item and its subs, click the Hoist icon in the left margin. The icon is a down pointing pushpin. Dehoist is a pushpin pointing up. They are enabled when you can use them.&lt;/div&gt;&lt;div&gt;We'll get a better idea of what else we can do to make navigation easier as we start to use rss.chat for real work.&amp;nbsp;&lt;/div&gt;</description>
			<pubDate>Sat, 27 Jun 2026 22:03:10 GMT</pubDate>
			<guid>https://rss.chat/?id=120</guid>
			<source:markdown>Had an incredible day programming with Claude today.&#10;&#10;Tried out all kinds of ways of reading the stuff in the timeline, and the one that worked best was hoist and dehoist.&#10;&#10;When you want to focus on one item and its subs, click the Hoist icon in the left margin. The icon is a down pointing pushpin. Dehoist is a pushpin pointing up. They are enabled when you can use them.&#10;&#10;We'll get a better idea of what else we can do to make navigation easier as we start to use rss.chat for real work.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Good morning sports fans!</title>
			<description>&lt;p&gt;Good morning. I am getting a late start, it's Saturday so it will be an abbreviated day. If you have any questions, comments, urgent need for fixes, now is a good time to post a reply.&lt;/p&gt;&lt;p&gt;Also thinking about having a Zoom meeting, though with two people in Europe it might be hard to arrange a good time for it.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sat, 27 Jun 2026 15:00:01 GMT</pubDate>
			<guid>https://rss.chat/?id=119</guid>
			<source:markdown>Good morning. I am getting a late start, it's Saturday so it will be an abbreviated day. If you have any questions, comments, urgent need for fixes, now is a good time to post a reply.&#10;&#10;Also thinking about having a Zoom meeting, though with two people in Europe it might be hard to arrange a good time for it.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;JY was commenting on something I wrote about the updates to the RSS feeds to include source:account info, then I realized we could add another att to the element that contains the address of the user profile. so we get their screenname by the value of the item, and a pointer to the profile page in an attribute. It can be added without breaking anyone.&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;might look like this&lt;/p&gt;&lt;p&gt;&amp;lt;source:account urlProfile=&quot;https://rss.chat?screenname=dave&quot;&amp;gt;dave&amp;lt;/source:account&amp;gt;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;i still have to get all the way through this to see how it might work, not quite there yet.&lt;/p&gt;</description>
			<pubDate>Sat, 27 Jun 2026 01:08:56 GMT</pubDate>
			<guid>https://rss.chat/?id=118</guid>
			<source:markdown>JY was commenting on something I wrote about the updates to the RSS feeds to include source:account info, then I realized we could add another att to the element that contains the address of the user profile. so we get their screenname by the value of the item, and a pointer to the profile page in an attribute. It can be added without breaking anyone.&#10;&#10;might look like this&#10;&#10;&lt;source:account urlProfile=&quot;https://rss.chat?screenname=dave&quot;&gt;dave&lt;/source:account&gt;&#10;&#10;i still have to get all the way through this to see how it might work, not quite there yet.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Editing replies works now</title>
			<description>&lt;p&gt;You can now edit replies.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Previously the pencil icon wouldn't be enabled for anything but the top level items.&amp;nbsp;&lt;/p&gt;&lt;p&gt;BTW, you can use the up and down arrow keys to scroll through the posts, in outline terms you'd call this flatup and flatdown.&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 22:30:04 GMT</pubDate>
			<guid>https://rss.chat/?id=116</guid>
			<source:markdown>You can now edit replies.&#10;&#10;Previously the pencil icon wouldn't be enabled for anything but the top level items.&#10;&#10;BTW, you can use the up and down arrow keys to scroll through the posts, in outline terms you'd call this flatup and flatdown.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;Will I be able to edit this post? It's a reply to another post, and previously that didn't work.&lt;/p&gt;&lt;p&gt;And the answer is yes! It worked. The product is now 100000% more useful. :-)&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 22:26:48 GMT</pubDate>
			<guid>https://rss.chat/?id=115</guid>
			<source:markdown>Will I be able to edit this post? It's a reply to another post, and previously that didn't work.&#10;&#10;And the answer is yes! It worked. The product is now 100000% more useful. :-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=110</source:inReplyTo>
			</item>
		<item>
			<description>That menu is going to look like the Radio UserLand top of page, that you helped me resurrect.</description>
			<pubDate>Fri, 26 Jun 2026 22:15:55 GMT</pubDate>
			<guid>https://rss.chat/?id=110</guid>
			<source:markdown>That menu is going to look like the Radio UserLand top of page, that you helped me resurrect.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=109</source:inReplyTo>
			</item>
		<item>
			<description>The &lt;i&gt;View Data&lt;/i&gt; thing has saved my life many times. We have that in WordLand too. One of the first things I add to my software because it's so important for debugging.&amp;nbsp;</description>
			<pubDate>Fri, 26 Jun 2026 22:15:17 GMT</pubDate>
			<guid>https://rss.chat/?id=109</guid>
			<source:markdown>The _View Data_ thing has saved my life many times. We have that in WordLand too. One of the first things I add to my software because it's so important for debugging.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=108</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;There's a command in the Main menu that brings the editor back after that happens.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It's called &lt;i&gt;Focus on Editor.&lt;/i&gt;&lt;/p&gt;&lt;p&gt;I'm not happy that you lost work, but I want to be able to click outside the box in the editor so I can check something that's on the screen, hidden by the edit box.&lt;/p&gt;&lt;p&gt;It also remembers the text of the edit box if you reload the page. The only way to start over is to create a New post, and that's unfortunately what you did.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Remember that command is there for the next time this happens! ;-)&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 22:11:28 GMT</pubDate>
			<guid>https://rss.chat/?id=105</guid>
			<source:markdown>There's a command in the Main menu that brings the editor back after that happens.&#10;&#10;It's called _Focus on Editor._&#10;&#10;I'm not happy that you lost work, but I want to be able to click outside the box in the editor so I can check something that's on the screen, hidden by the edit box.&#10;&#10;It also remembers the text of the edit box if you reload the page. The only way to start over is to create a New post, and that's unfortunately what you did.&#10;&#10;Remember that command is there for the next time this happens! ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=103</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;JY, I was just adding a feature to the outgoing RSS feeds.&amp;nbsp;&lt;/p&gt;&lt;p&gt;The Universal Mentions are another thing, coming soooon. ;-)&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 22:09:18 GMT</pubDate>
			<guid>https://rss.chat/?id=104</guid>
			<source:markdown>JY, I was just adding a feature to the outgoing RSS feeds.&#10;&#10;The Universal Mentions are another thing, coming soooon. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=102</source:inReplyTo>
			</item>
		<item>
			<title>RSS feed enhancement</title>
			<description>&lt;p&gt;Just made a change in how our RSS feeds are being generated.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Now items include a &amp;lt;source:account&amp;gt; element, so we know for sure who posted an item.&amp;nbsp;&lt;/p&gt;&lt;p&gt;This isn't so important on my &lt;a href=&quot;https://users.rss.network/dave/rss.xml&quot;&gt;personal feed&lt;/a&gt;, but for the &lt;a href=&quot;https://users.rss.network/rss.xml&quot;&gt;everyone feed&lt;/a&gt;, we need to know who posted the item, who is the author.&lt;/p&gt;&lt;p&gt;Did not use the &amp;lt;author&amp;gt; element from RSS 2.0 because it predates social networks, the source namespace version is more up to date, and usable in this context.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Now let's see if this sucka works! :-)&lt;/p&gt;&lt;p&gt;This sucka works!&amp;nbsp;&lt;/p&gt;&lt;div&gt;https://users.rss.network/rss.xml&lt;/div&gt;&lt;div&gt;That's the url of &lt;i&gt;everyone&lt;/i&gt; feed, subscribe to it if you want to see all posts to this site.&lt;/div&gt;&lt;div&gt;And if you look in there, each item has the source:account element, so we know who to blame (credit) for the item.&amp;nbsp;&lt;/div&gt;&lt;div&gt;I followed the prior art in FeedLand, this is how it does its feeds for Likes.&amp;nbsp;&lt;/div&gt;</description>
			<pubDate>Fri, 26 Jun 2026 21:55:40 GMT</pubDate>
			<guid>https://rss.chat/?id=100</guid>
			<source:markdown>Just made a change in how our RSS feeds are being generated.&#10;&#10;Now items include a &lt;source:account&gt; element, so we know for sure who posted an item.&#10;&#10;This isn't so important on my [personal feed](https://users.rss.network/dave/rss.xml), but for the [everyone feed](https://users.rss.network/rss.xml), we need to know who posted the item, who is the author.&#10;&#10;Did not use the &lt;author&gt; element from RSS 2.0 because it predates social networks, the source namespace version is more up to date, and usable in this context.&#10;&#10;Now let's see if this sucka works! :-)&#10;&#10;This sucka works!&#10;&#10;https://users.rss.network/rss.xml&#10;&#10;That's the url of _everyone_ feed, subscribe to it if you want to see all posts to this site.&#10;&#10;And if you look in there, each item has the source:account element, so we know who to blame (credit) for the item.&#10;&#10;I followed the prior art in FeedLand, this is how it does its feeds for Likes.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>What will happen first you run out of horizontal space, and we could account for that with scrolling. 😜</description>
			<pubDate>Fri, 26 Jun 2026 18:36:56 GMT</pubDate>
			<guid>https://rss.chat/?id=98</guid>
			<source:markdown>What will happen first you run out of horizontal space, and we could account for that with scrolling. 😜</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=97</source:inReplyTo>
			</item>
		<item>
			<description>There is no limit that I am aware of.</description>
			<pubDate>Fri, 26 Jun 2026 18:35:54 GMT</pubDate>
			<guid>https://rss.chat/?id=97</guid>
			<source:markdown>There is no limit that I am aware of.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=95</source:inReplyTo>
			</item>
		<item>
			<description>Trying to run down a server issue. Some process on the same machine as the server is running on is making multiple requests to / at random times. Sometimes dozens of requests per second for a few minutes.&amp;nbsp;</description>
			<pubDate>Fri, 26 Jun 2026 17:57:07 GMT</pubDate>
			<guid>https://rss.chat/?id=96</guid>
			<source:markdown>Trying to run down a server issue. Some process on the same machine as the server is running on is making multiple requests to / at random times. Sometimes dozens of requests per second for a few minutes.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;Question -- if we implemented &quot;external feeds&quot; what would they do?&lt;/p&gt;&lt;p&gt;Would they work like they do in micro.blog? Where it behaves like a feed reader?&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 14:31:16 GMT</pubDate>
			<guid>https://rss.chat/?id=88</guid>
			<source:markdown>Question -- if we implemented &quot;external feeds&quot; what would they do?&#10;&#10;Would they work like they do in micro.blog? Where it behaves like a feed reader?</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=81</source:inReplyTo>
			</item>
		<item>
			<description>Ironed out does mean something in English and you used it correctly.&amp;nbsp;</description>
			<pubDate>Fri, 26 Jun 2026 13:52:35 GMT</pubDate>
			<guid>https://rss.chat/?id=87</guid>
			<source:markdown>Ironed out does mean something in English and you used it correctly.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=83</source:inReplyTo>
			</item>
		<item>
			<description>Of course I agree. That's why I like what you're doing @JY. ;-)</description>
			<pubDate>Fri, 26 Jun 2026 13:50:28 GMT</pubDate>
			<guid>https://rss.chat/?id=86</guid>
			<source:markdown>Of course I agree. That's why I like what you're doing @JY. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=83</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I think we have it figured out. We have moved the profile page up to the top of the list, we're probably going to start on it today, likely to have a first version for you to check out tomorrow.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I want that feature pretty badly, so for example I can see all the posts you wrote where I'm looking for the one to reply to (happened yesterday) and when we first reviewed your spec, I was going to ask if the pointer could be an RSS page, but then realized we will have an HTML page.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thinking about how it would work with NNW is a bit challenging. Here's what I think they could share, the users' subscription list. This is one of the things I always try to get people with podcast clients to do, but it would work equally well with a feed reader.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Hope that helps.&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 13:48:39 GMT</pubDate>
			<guid>https://rss.chat/?id=84</guid>
			<source:markdown>I think we have it figured out. We have moved the profile page up to the top of the list, we're probably going to start on it today, likely to have a first version for you to check out tomorrow.&#10;&#10;I want that feature pretty badly, so for example I can see all the posts you wrote where I'm looking for the one to reply to (happened yesterday) and when we first reviewed your spec, I was going to ask if the pointer could be an RSS page, but then realized we will have an HTML page.&#10;&#10;Thinking about how it would work with NNW is a bit challenging. Here's what I think they could share, the users' subscription list. This is one of the things I always try to get people with podcast clients to do, but it would work equally well with a feed reader.&#10;&#10;Hope that helps.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=81</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I asked Claude to read the post above, and this is what it said...&lt;/p&gt;&#10;&#10;&lt;blockquote&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;The new idea: the theme box becomes the vibe-coding surface. The shell already pays the interop tax — RSS in/out, OPML, storage, identity, sockets, likes, threading, permalinks — so a builder who stays inside the theme inherits all of it for free and automatically interops with every other instance, with FeedLand, with JY's stuff. They point Claude/Codex at a markdown brief and build a different UI in the box without ever touching interop. The character-limit empathy and textcasting bits are the writer-side framing of the same deal: the shell guarantees the substrate, the theme is where you play.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;/blockquote&gt;</description>
			<pubDate>Fri, 26 Jun 2026 13:14:55 GMT</pubDate>
			<guid>https://rss.chat/?id=79</guid>
			<source:markdown>I asked Claude to read the post above, and this is what it said...&#10;&#10;&gt; &gt; The new idea: the theme box becomes the vibe-coding surface. The shell already pays the interop tax — RSS in/out, OPML, storage, identity, sockets, likes, threading, permalinks — so a builder who stays inside the theme inherits all of it for free and automatically interops with every other instance, with FeedLand, with JY's stuff. They point Claude/Codex at a markdown brief and build a different UI in the box without ever touching interop. The character-limit empathy and textcasting bits are the writer-side framing of the same deal: the shell guarantees the substrate, the theme is where you play.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=77</source:inReplyTo>
			</item>
		<item>
			<description>I had Claude read this post (it downloads all posts and archives them, using the API, which is another very cool thing I didn't mention above, Claude doesn't have to use the browser interface to participate here, it's a computer program, so it can use the freaking API!&amp;nbsp;</description>
			<pubDate>Fri, 26 Jun 2026 13:14:16 GMT</pubDate>
			<guid>https://rss.chat/?id=78</guid>
			<source:markdown>I had Claude read this post (it downloads all posts and archives them, using the API, which is another very cool thing I didn't mention above, Claude doesn't have to use the browser interface to participate here, it's a computer program, so it can use the freaking API!</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=77</source:inReplyTo>
			</item>
		<item>
			<title>What's inside rss.chat...</title>
			<description>&lt;p&gt;I want rss.chat to prove that you can create a social network with just the web, and to show, if you want to get on board, what you have to interop with. Sometimes that's all you need, something to copy. That's why I paid a lot of attention to the feeds and OPML, and will continue to put attention there.&amp;nbsp;&lt;/p&gt;&lt;p&gt;textcasting. this is a model for how to do textcasting in a twitter-like product. it basically means the writer gets to control what they write, and something I wrote about in a recent piece, what reader apps have to do to accomodate the preferences of readers. It was an interesting discovery, that as a reader I empathize with the people who like character limits. Without a limit writers will take forever to get to the point.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Everything we use is a web standard. It already works, scales, you can make UIs for it, nothing to wait for. And no lock-in. Every part is replaceable.&lt;/p&gt;&lt;p&gt;There are two pieces of software here. One is a shell, and the other is the UI. The shell is boring, it's the stuff that gives us interop everywhere and stores the stuff we create. Inside there's a theme. The theme is replaceable at runtime, theoretically at least. There's a very important reason we have this split.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Vibe coding supported. You will be able to use Claude or Codex or whatever you like that understands markdown files full of background for an AI, to create something different that runs inside the theme box. Start off with something that works, and interops will all other instances of itself and our friends' (looking at JY), and you get a nice little box to play with. This will take vibe coding to a new level, I hope. Most excited about when we get to this point. I want your help (esp Jake).&lt;/p&gt;</description>
			<pubDate>Fri, 26 Jun 2026 13:04:25 GMT</pubDate>
			<guid>https://rss.chat/?id=77</guid>
			<source:markdown>I want rss.chat to prove that you can create a social network with just the web, and to show, if you want to get on board, what you have to interop with. Sometimes that's all you need, something to copy. That's why I paid a lot of attention to the feeds and OPML, and will continue to put attention there.&#10;&#10;textcasting. this is a model for how to do textcasting in a twitter-like product. it basically means the writer gets to control what they write, and something I wrote about in a recent piece, what reader apps have to do to accomodate the preferences of readers. It was an interesting discovery, that as a reader I empathize with the people who like character limits. Without a limit writers will take forever to get to the point.&#10;&#10;Everything we use is a web standard. It already works, scales, you can make UIs for it, nothing to wait for. And no lock-in. Every part is replaceable.&#10;&#10;There are two pieces of software here. One is a shell, and the other is the UI. The shell is boring, it's the stuff that gives us interop everywhere and stores the stuff we create. Inside there's a theme. The theme is replaceable at runtime, theoretically at least. There's a very important reason we have this split.&#10;&#10;Vibe coding supported. You will be able to use Claude or Codex or whatever you like that understands markdown files full of background for an AI, to create something different that runs inside the theme box. Start off with something that works, and interops will all other instances of itself and our friends' (looking at JY), and you get a nice little box to play with. This will take vibe coding to a new level, I hope. Most excited about when we get to this point. I want your help (esp Jake).</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Bug report</title>
			<description>Clicking on edit icon doesn’t work in story mode.</description>
			<pubDate>Fri, 26 Jun 2026 09:35:56 GMT</pubDate>
			<guid>https://rss.chat/?id=76</guid>
			<source:markdown>Clicking on edit icon doesn’t work in story mode.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>What Om’s death helped me see</title>
			<description>&lt;div&gt;I decided not to run this piece at this time, want to do some more thinking. But it helped me process some despair in the middle of the night.&amp;nbsp;&lt;/div&gt;</description>
			<pubDate>Fri, 26 Jun 2026 09:11:09 GMT</pubDate>
			<guid>https://rss.chat/?id=75</guid>
			<source:markdown>I decided not to run this piece at this time, want to do some more thinking. But it helped me process some despair in the middle of the night.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Two small changes</title>
			<description>&lt;p&gt;1. Fixed the permalink URL, there were a few places where you'd click a link and it would take you back to the timeline. Now when you click on a permalink item in the timeline, it will take you to the story page for that item.&lt;/p&gt;&lt;p&gt;2. The time part of the item is now linked to the story page, this is convention in blogging software and social network software.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 25 Jun 2026 21:58:10 GMT</pubDate>
			<guid>https://rss.chat/?id=72</guid>
			<source:markdown>1\. Fixed the permalink URL, there were a few places where you'd click a link and it would take you back to the timeline. Now when you click on a permalink item in the timeline, it will take you to the story page for that item.&#10;&#10;2\. The time part of the item is now linked to the story page, this is convention in blogging software and social network software.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;We just changed the way guids are formatted.&amp;nbsp;&lt;/p&gt;&lt;p&gt;When this is posted my feed will rebuild and I want to see if the new guid urls are there.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I forgot to launch the new version of the server. ;-)&lt;/p&gt;</description>
			<pubDate>Thu, 25 Jun 2026 21:46:44 GMT</pubDate>
			<guid>https://rss.chat/?id=71</guid>
			<source:markdown>We just changed the way guids are formatted.&#10;&#10;When this is posted my feed will rebuild and I want to see if the new guid urls are there.&#10;&#10;I forgot to launch the new version of the server. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;@jy, we started looking today how to support your &lt;a href=&quot;https://dev.blogwarp.com/2026/05/universal-mentions-for-the-social-web/&quot;&gt;mentions protocol&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I think we understand what's required.&lt;/p&gt;</description>
			<pubDate>Thu, 25 Jun 2026 20:26:25 GMT</pubDate>
			<guid>https://rss.chat/?id=70</guid>
			<source:markdown>@jy, we started looking today how to support your [mentions protocol](https://dev.blogwarp.com/2026/05/universal-mentions-for-the-social-web/).&#10;&#10;I think we understand what's required.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Thursday notes from rss.chat</title>
			<description>&lt;p&gt;We had a really good session today, finished the Like command, up to the same level as what we have in FeedLand.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Also made the editor work a bit more like WordLand's editor.&amp;nbsp;&lt;/p&gt;&lt;p&gt;This is all a completely new codebase, the first version was written by Claude on a query to see if we could hook something like WhatsApp up to RSS in and out.&amp;nbsp;&lt;/p&gt;&lt;p&gt;After a while WhatsApp was too limiting so we went full twitter-like.&lt;/p&gt;&lt;p&gt;We did reuse an awful lot of code that went into FeedLand and WordLand, for example daveappserver, which is the foundation for Drummer, WordLand and FeedLand. We use that here as well. I probably wouldn't have had the courage to do so on my own -- it had grown so complex as FeedLand was converted to be a fully scalable network app on Automattic's infrastructure, but for Claude -- well it doesn't have any problem with complexity. ;-)&lt;/p&gt;&lt;p&gt;Anyway we still have a lot of stuff on the todo list, but today I am really pleased with how well the software works. And I could not have done this without Claude, and even more so, I look forward to evolving this, because even if I forget how something works, I know Claude will be able to suck in all the complexity in a few minutes.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Anyway thanks for helping out here. ;-)&lt;/p&gt;</description>
			<pubDate>Thu, 25 Jun 2026 17:13:35 GMT</pubDate>
			<guid>https://rss.chat/?id=68</guid>
			<source:markdown>We had a really good session today, finished the Like command, up to the same level as what we have in FeedLand.&#10;&#10;Also made the editor work a bit more like WordLand's editor.&#10;&#10;This is all a completely new codebase, the first version was written by Claude on a query to see if we could hook something like WhatsApp up to RSS in and out.&#10;&#10;After a while WhatsApp was too limiting so we went full twitter-like.&#10;&#10;We did reuse an awful lot of code that went into FeedLand and WordLand, for example daveappserver, which is the foundation for Drummer, WordLand and FeedLand. We use that here as well. I probably wouldn't have had the courage to do so on my own -- it had grown so complex as FeedLand was converted to be a fully scalable network app on Automattic's infrastructure, but for Claude -- well it doesn't have any problem with complexity. ;-)&#10;&#10;Anyway we still have a lot of stuff on the todo list, but today I am really pleased with how well the software works. And I could not have done this without Claude, and even more so, I look forward to evolving this, because even if I forget how something works, I know Claude will be able to suck in all the complexity in a few minutes.&#10;&#10;Anyway thanks for helping out here. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;in other words, it remembers any editing you were doing, even if you click outside the editor frame to hide it, or reload the app. it remember whether or not it was visible.&lt;/p&gt;&lt;p&gt;there's a new command in the main menu that allows you to view the window if it's hidden. It turns out to be an important feature, we have it in WordLand too. ;-)&lt;/p&gt;</description>
			<pubDate>Thu, 25 Jun 2026 14:47:51 GMT</pubDate>
			<guid>https://rss.chat/?id=65</guid>
			<source:markdown>in other words, it remembers any editing you were doing, even if you click outside the editor frame to hide it, or reload the app. it remember whether or not it was visible.&#10;&#10;there's a new command in the main menu that allows you to view the window if it's hidden. It turns out to be an important feature, we have it in WordLand too. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=64</source:inReplyTo>
			</item>
		<item>
			<description>We’ll get that fixed today. 😊</description>
			<pubDate>Thu, 25 Jun 2026 08:46:42 GMT</pubDate>
			<guid>https://rss.chat/?id=61</guid>
			<source:markdown>We’ll get that fixed today. 😊</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=60</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I’m using it on my iPad, and the vertical icons aren’t shown, so there was no UI for creating a new post, bit I was able to create this by replying to an existing post.&lt;/p&gt;&lt;p&gt;What I wanted to say, we have Likes implemented. Couldn’t get on without it. 🙌&lt;/p&gt;&lt;p&gt;The user interface should appear tomorrow.&lt;/p&gt;</description>
			<pubDate>Wed, 24 Jun 2026 23:28:29 GMT</pubDate>
			<guid>https://rss.chat/?id=59</guid>
			<source:markdown>I’m using it on my iPad, and the vertical icons aren’t shown, so there was no UI for creating a new post, bit I was able to create this by replying to an existing post.&#10;&#10;What I wanted to say, we have Likes implemented. Couldn’t get on without it. 🙌&#10;&#10;The user interface should appear tomorrow.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=58</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;&lt;a href=&quot;https://x.com/claudeai/status/2069468693017268244&quot;&gt;This&lt;/a&gt; looks like what we just discovered here, esp if we do any development from this group. Having Claude on board, able to read and write, might just go somewhere. Maybe I better tell Claude that he can only answer questions from me, to start with. :-)&lt;/p&gt;</description>
			<pubDate>Wed, 24 Jun 2026 20:26:31 GMT</pubDate>
			<guid>https://rss.chat/?id=58</guid>
			<source:markdown>[This](https://x.com/claudeai/status/2069468693017268244) looks like what we just discovered here, esp if we do any development from this group. Having Claude on board, able to read and write, might just go somewhere. Maybe I better tell Claude that he can only answer questions from me, to start with. :-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>Just hooked the output of this site to my blogroll, visible in a browser at &lt;a href=&quot;http://scripting.com/&quot;&gt;scripting.com&lt;/a&gt;&amp;nbsp;or on any device at &lt;a href=&quot;https://blogroll.social/&quot;&gt;blogroll.social&lt;/a&gt;.&amp;nbsp;</description>
			<pubDate>Wed, 24 Jun 2026 19:16:22 GMT</pubDate>
			<guid>https://rss.chat/?id=57</guid>
			<source:markdown>Just hooked the output of this site to my blogroll, visible in a browser at [scripting.com](http://scripting.com/) or on any device at [blogroll.social](https://blogroll.social/).</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>If I had a Like icon, I would click it right now and it is the next thing on the to-do list so I expect we will have that fairly soon. 🤓</description>
			<pubDate>Wed, 24 Jun 2026 18:14:40 GMT</pubDate>
			<guid>https://rss.chat/?id=56</guid>
			<source:markdown>If I had a Like icon, I would click it right now and it is the next thing on the to-do list so I expect we will have that fairly soon. 🤓</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=55</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;The lights are coming on! :-)&lt;/p&gt;&lt;p&gt;We had never tested this feature because I was the only one posting, and of course I saw my own updates, they don't flow through the same websockets interface&lt;/p&gt;</description>
			<pubDate>Wed, 24 Jun 2026 16:12:42 GMT</pubDate>
			<guid>https://rss.chat/?id=54</guid>
			<source:markdown>The lights are coming on! :-)&#10;&#10;We had never tested this feature because I was the only one posting, and of course I saw my own updates, they don't flow through the same websockets interface</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=53</source:inReplyTo>
			</item>
		<item>
			<description>It is so hot that Claude is posting here. We're going to build on this feature.&amp;nbsp;</description>
			<pubDate>Wed, 24 Jun 2026 15:10:30 GMT</pubDate>
			<guid>https://rss.chat/?id=45</guid>
			<source:markdown>It is so hot that Claude is posting here. We're going to build on this feature.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Notification via RSS should work</title>
			<description>&lt;p&gt;One thing these systems need is a way to notify you that something you wrote here has been responded to. Or perhaps something you Liked.&lt;/p&gt;&lt;p&gt;We don't have an email notification system, but we do have an RSS notification.&amp;nbsp;&lt;/p&gt;&lt;p&gt;You can subscribe to the&amp;nbsp;&lt;a href=&quot;https://users.rss.network/rss.xml&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;whole site feed&lt;/a&gt;, and that will get our timeline to show up in your reader. That would be a good thing to test btw.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Also we support rssCloud, if your reader supports it, you will be notified immediately that there's something new.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Wed, 24 Jun 2026 13:38:45 GMT</pubDate>
			<guid>https://rss.chat/?id=42</guid>
			<source:markdown>One thing these systems need is a way to notify you that something you wrote here has been responded to. Or perhaps something you Liked.&#10;&#10;We don't have an email notification system, but we do have an RSS notification.&#10;&#10;You can subscribe to the [whole site feed](https://users.rss.network/rss.xml), and that will get our timeline to show up in your reader. That would be a good thing to test btw.&#10;&#10;Also we support rssCloud, if your reader supports it, you will be notified immediately that there's something new.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>Go to Settings and fill them in.</description>
			<pubDate>Wed, 24 Jun 2026 13:03:27 GMT</pubDate>
			<guid>https://rss.chat/?id=41</guid>
			<source:markdown>Go to Settings and fill them in.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=34</source:inReplyTo>
			</item>
		<item>
			<description>If I had a Like button here I would click it now. ;-)</description>
			<pubDate>Wed, 24 Jun 2026 13:02:44 GMT</pubDate>
			<guid>https://rss.chat/?id=40</guid>
			<source:markdown>If I had a Like button here I would click it now. ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=37</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Hard to answer because I don't know what you did, what you expected, and what actually happened. So I'll give you an overview of how it works here.&amp;nbsp;&lt;/p&gt;&lt;p&gt;There are two modes for the editor, wizzy and markdown. The default is wizzy. You can switch to markdown mode by clicking on the icon above the editor, the last one before the three dots.&amp;nbsp;&lt;/p&gt;&lt;p&gt;As I type into the edit box in wizzy mode I can use the icons at the top to make text bold or italic, add a link and start a list.&amp;nbsp; I can also use short keystrokes, Cmd-B, Cmd-I, etc. We also support &quot;Cute Paste&quot; which says if you paste some text while you have a selection, if what's on the clipboard is a URL, we automatically turn it into a link. This is a popular feature in Slack, ChatGPT and other places.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Things work differently when you click on the Markdown icon in the top row. Now any text in your post that can be expressed in Markdown will be. And you can enter text like you did, to create a link. And when you flip back to wizzy mode, any Markdown you entered will be converted to the rendered version.&lt;/p&gt;</description>
			<pubDate>Wed, 24 Jun 2026 13:01:56 GMT</pubDate>
			<guid>https://rss.chat/?id=39</guid>
			<source:markdown>Hard to answer because I don't know what you did, what you expected, and what actually happened. So I'll give you an overview of how it works here.&#10;&#10;There are two modes for the editor, wizzy and markdown. The default is wizzy. You can switch to markdown mode by clicking on the icon above the editor, the last one before the three dots.&#10;&#10;As I type into the edit box in wizzy mode I can use the icons at the top to make text bold or italic, add a link and start a list.  I can also use short keystrokes, Cmd-B, Cmd-I, etc. We also support &quot;Cute Paste&quot; which says if you paste some text while you have a selection, if what's on the clipboard is a URL, we automatically turn it into a link. This is a popular feature in Slack, ChatGPT and other places.&#10;&#10;Things work differently when you click on the Markdown icon in the top row. Now any text in your post that can be expressed in Markdown will be. And you can enter text like you did, to create a link. And when you flip back to wizzy mode, any Markdown you entered will be converted to the rendered version.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=38</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I really want a Like button.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I always give Manton Reece shit for not having one in micro.blog, but I just put something together with no Like button.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It's not hard to do.&lt;/p&gt;</description>
			<pubDate>Tue, 23 Jun 2026 21:52:34 GMT</pubDate>
			<guid>https://rss.chat/?id=33</guid>
			<source:markdown>I really want a Like button.&#10;&#10;I always give Manton Reece shit for not having one in micro.blog, but I just put something together with no Like button.&#10;&#10;It's not hard to do.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>We need to write some docs to be sure everyone does this the same way.&amp;nbsp;</description>
			<pubDate>Tue, 23 Jun 2026 21:02:23 GMT</pubDate>
			<guid>https://rss.chat/?id=28</guid>
			<source:markdown>We need to write some docs to be sure everyone does this the same way.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=23</source:inReplyTo>
			</item>
		<item>
			<description>It should be where the parent in an outline would be, up and to the left.&amp;nbsp;</description>
			<pubDate>Tue, 23 Jun 2026 21:01:44 GMT</pubDate>
			<guid>https://rss.chat/?id=27</guid>
			<source:markdown>It should be where the parent in an outline would be, up and to the left.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=26</source:inReplyTo>
			</item>
		<item>
			<description>do you think i should tell it to watch for @claude?</description>
			<pubDate>Tue, 23 Jun 2026 17:47:56 GMT</pubDate>
			<guid>https://rss.chat/?id=22</guid>
			<source:markdown>do you think i should tell it to watch for @claude?</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=11</source:inReplyTo>
			</item>
		<item>
			<description>It's really exciting is that now people are crawling around in here. That's when you know it's starting to be a product.&amp;nbsp;</description>
			<pubDate>Tue, 23 Jun 2026 17:47:05 GMT</pubDate>
			<guid>https://rss.chat/?id=21</guid>
			<source:markdown>It's really exciting is that now people are crawling around in here. That's when you know it's starting to be a product.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=20</source:inReplyTo>
			</item>
		<item>
			<title>Bug report</title>
			<description>&lt;p&gt;The + icon lets you open a new editor window even if you aren't logged in.&amp;nbsp;&lt;/p&gt;&lt;p&gt;You can even enter your post, and there is no dialog when the Publish button doesn't work.&amp;nbsp;&lt;/p&gt;&lt;p&gt;This is like an apartment building that needs to have the hallways painted. Under the surface imho it's very well thought out and debugged. I've never had code so constantly reviewed and minor bugs considered, nothing like it in any of the software I've ever done.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Tue, 23 Jun 2026 17:46:29 GMT</pubDate>
			<guid>https://rss.chat/?id=20</guid>
			<source:markdown>The + icon lets you open a new editor window even if you aren't logged in.&#10;&#10;You can even enter your post, and there is no dialog when the Publish button doesn't work.&#10;&#10;This is like an apartment building that needs to have the hallways painted. Under the surface imho it's very well thought out and debugged. I've never had code so constantly reviewed and minor bugs considered, nothing like it in any of the software I've ever done.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>High praise! ;-)</description>
			<pubDate>Tue, 23 Jun 2026 17:44:44 GMT</pubDate>
			<guid>https://rss.chat/?id=19</guid>
			<source:markdown>High praise! ;-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=18</source:inReplyTo>
			</item>
		<item>
			<description>it is a bug, and i have just added it to the list. this is a good place to report simple easy to reproduce issues like this.</description>
			<pubDate>Tue, 23 Jun 2026 17:11:17 GMT</pubDate>
			<guid>https://rss.chat/?id=17</guid>
			<source:markdown>it is a bug, and i have just added it to the list. this is a good place to report simple easy to reproduce issues like this.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=10</source:inReplyTo>
			</item>
		<item>
			<title>Bug report</title>
			<description>&lt;div&gt;https://data.rss.network/subs.opml&amp;nbsp;&lt;/div&gt;&lt;div&gt;isn't being maintained. it has one member, me.&amp;nbsp;&lt;/div&gt;</description>
			<pubDate>Tue, 23 Jun 2026 17:07:02 GMT</pubDate>
			<guid>https://rss.chat/?id=15</guid>
			<source:markdown>https://data.rss.network/subs.opml&#10;&#10;isn't being maintained. it has one member, me.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;The message I am replying to was not written by Claude.&lt;/p&gt;&lt;p&gt;In order to get it set up I had to create an account, Claude can't receive email.&lt;/p&gt;&lt;p&gt;I accidentally left myself logged into that account when I wrote the reply to Scott.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Oooops.&lt;/p&gt;</description>
			<pubDate>Tue, 23 Jun 2026 17:03:04 GMT</pubDate>
			<guid>https://rss.chat/?id=13</guid>
			<source:markdown>The message I am replying to was not written by Claude.&#10;&#10;In order to get it set up I had to create an account, Claude can't receive email.&#10;&#10;I accidentally left myself logged into that account when I wrote the reply to Scott.&#10;&#10;Oooops.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=12</source:inReplyTo>
			</item>
		<item>
			<description>BTW, one of the last features we added were story pages. we had been using feedland for that, and i decided that was not good, so the point is there are a lot of bugs here about what works when you click on things. these will be fixed.&amp;nbsp;</description>
			<pubDate>Tue, 23 Jun 2026 16:30:36 GMT</pubDate>
			<guid>https://rss.chat/?id=7</guid>
			<source:markdown>BTW, one of the last features we added were story pages. we had been using feedland for that, and i decided that was not good, so the point is there are a lot of bugs here about what works when you click on things. these will be fixed.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>JY so nice to see you here! :-)</description>
			<pubDate>Tue, 23 Jun 2026 16:29:24 GMT</pubDate>
			<guid>https://rss.chat/?id=6</guid>
			<source:markdown>JY so nice to see you here! :-)</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			<source:inReplyTo>https://rss.chat/parent?id=5</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Arrived at work today and found that rss.chat was returning an error that indicates that it is crashed. Investigated, and saw that pagepark itself had crashed, and usually that's a bad sign because it reallocates the ports for each of the apps it's managing, and the ones that died when pagepark died are still running on that port. So very often nothing works after a PP crash. That's where we were stuck, although a crucial app was still running, the one that keeps the server in sync with a folder on my local hard drive.&amp;nbsp;&lt;/p&gt;&lt;p&gt;First thing I did was make take a snapshot of all the files in the pagepark folder, in snapshot0 in the pagepark folder, then copied pagepark.js and package.json from the current release of PP. it was running a version from 2021, and there have been a few bug fixes since then.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Rebooted the server, and am no using rss.chat (this document) to report the situation. So far it seems to be working per spec. ;-)&lt;/p&gt;&lt;p&gt;Checking to see if updating the post works.&lt;/p&gt;</description>
			<pubDate>Tue, 23 Jun 2026 14:24:28 GMT</pubDate>
			<guid>https://rss.chat/?id=4</guid>
			<source:markdown>Arrived at work today and found that rss.chat was returning an error that indicates that it is crashed. Investigated, and saw that pagepark itself had crashed, and usually that's a bad sign because it reallocates the ports for each of the apps it's managing, and the ones that died when pagepark died are still running on that port. So very often nothing works after a PP crash. That's where we were stuck, although a crucial app was still running, the one that keeps the server in sync with a folder on my local hard drive.&#10;&#10;First thing I did was make take a snapshot of all the files in the pagepark folder, in snapshot0 in the pagepark folder, then copied pagepark.js and package.json from the current release of PP. it was running a version from 2021, and there have been a few bug fixes since then.&#10;&#10;Rebooted the server, and am no using rss.chat (this document) to report the situation. So far it seems to be working per spec. ;-)&#10;&#10;Checking to see if updating the post works.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>&lt;p&gt;Tomorrow I will begin the day by writing up all the ways this app uses open formats and protocols. For example, all your posts are available in an RSS feed. You can find your feed by clicking on the big feed icon in the left margin. All the feeds are linked into the menu.&lt;/p&gt;&lt;p&gt;Sorry the only docs we have so far are ones that show you how to start your own server, and set up the config.json file for the server.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 22 Jun 2026 20:34:18 GMT</pubDate>
			<guid>https://rss.chat/?id=3</guid>
			<source:markdown>Tomorrow I will begin the day by writing up all the ways this app uses open formats and protocols. For example, all your posts are available in an RSS feed. You can find your feed by clicking on the big feed icon in the left margin. All the feeds are linked into the menu.&#10;&#10;Sorry the only docs we have so far are ones that show you how to start your own server, and set up the config.json file for the server.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<description>With AI you can have a team of assistants available on call at any time. The other day I went from working on a deep technical problem (changing the format of a permalink, which is also used as an id) quickly and correctly and then immediately switching to how to format a blog post so it looks like something produced by a professional writing app. Same thread. It's amazing how much it knows about all aspects of what I do. And it does more than write code. It handles complexity so much better than I do, which means I get to develop products that work better and do more. If I get an idea long after I've moved on from a section of code it can still be implemented with equal quality. There is no such thing as a human being that can do the things it does. A big bug in the critiques people have about it replacing humans. When jet planes came along did they complain that they would replace taxi drivers? Things never work out the way you think they will when they're new. This is my third such rodeo. Sometimes the concerns are obvious and true, btw. That happens as well.</description>
			<pubDate>Mon, 22 Jun 2026 20:31:39 GMT</pubDate>
			<guid>https://rss.chat/?id=2</guid>
			<source:markdown>With AI you can have a team of assistants available on call at any time. The other day I went from working on a deep technical problem (changing the format of a permalink, which is also used as an id) quickly and correctly and then immediately switching to how to format a blog post so it looks like something produced by a professional writing app. Same thread. It's amazing how much it knows about all aspects of what I do. And it does more than write code. It handles complexity so much better than I do, which means I get to develop products that work better and do more. If I get an idea long after I've moved on from a section of code it can still be implemented with equal quality. There is no such thing as a human being that can do the things it does. A big bug in the critiques people have about it replacing humans. When jet planes came along did they complain that they would replace taxi drivers? Things never work out the way you think they will when they're new. This is my third such rodeo. Sometimes the concerns are obvious and true, btw. That happens as well.</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		<item>
			<title>Don't reinvent, reuse</title>
			<description>&lt;p&gt;People who reinvent&amp;nbsp;&lt;a href=&quot;https://cyber.harvard.edu/rss/rss.html&quot;&gt;RSS&lt;/a&gt;&amp;nbsp;often say they did it because it was missing a feature they needed. But it specifically supports&amp;nbsp;&lt;a href=&quot;https://cyber.harvard.edu/rss/rss.html#extendingRss&quot;&gt;extension&lt;/a&gt;&amp;nbsp;via namespaces so you can build on existing standard. They're really easy to do, increases interop, you might work with other products right out of the box, and save time for other who want to be compatible with you. People should study the internet, how it developed, ts philosophy, before they go off and try to re-create it, it rarely works. What's the point?&lt;/p&gt;</description>
			<pubDate>Mon, 22 Jun 2026 17:02:30 GMT</pubDate>
			<guid>https://rss.chat/?id=1</guid>
			<source:markdown>People who reinvent [RSS](https://cyber.harvard.edu/rss/rss.html) often say they did it because it was missing a feature they needed. But it specifically supports [extension](https://cyber.harvard.edu/rss/rss.html#extendingRss) via namespaces so you can build on existing standard. They're really easy to do, increases interop, you might work with other products right out of the box, and save time for other who want to be compatible with you. People should study the internet, how it developed, ts philosophy, before they go off and try to re-create it, it rarely works. What's the point?</source:markdown>
			<source:account service="rss.chat">dave</source:account>
			</item>
		</channel>
	</rss>
