<?xml version="1.0" encoding="UTF-8"?>
<!-- RSS generated by rss.network v0.5.31 on Fri, 17 Jul 2026 21:38:28 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>Fri, 17 Jul 2026 21:38:28 GMT</pubDate>
		<language>en-us</language>
		<generator>rss.network v0.5.31</generator>
		<docs>http://cyber.law.harvard.edu/rss/rss.html</docs>
		<lastBuildDate>Fri, 17 Jul 2026 21:38:28 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/2023/02/13/bozoApproved.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:account service="rss.chat">dave</source:account>
		<source:localTime>Fri, July 17, 2026 5:38 PM EDT</source:localTime>
		<source:self>https://rss.chat/users/dave/rss.xml</source:self>
		<item>
			<title>Changes in the feeds rss.chat generates</title>
			<description>&lt;div&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/issues/14&quot;&gt;https://github.com/scripting/rss.chat/issues/14&lt;/a&gt;&lt;/div&gt;</description>
			<pubDate>Fri, 17 Jul 2026 21:38:28 GMT</pubDate>
			<guid>https://rss.chat/?id=344</guid>
			<source:markdown>https://github.com/scripting/rss.chat/issues/14</source:markdown>
			</item>
		<item>
			<description>Test post.&amp;nbsp;</description>
			<pubDate>Fri, 17 Jul 2026 21:08:43 GMT</pubDate>
			<guid>https://rss.chat/?id=343</guid>
			<source:markdown>Test post.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=342</source:inReplyTo>
			</item>
		<item>
			<description>claude can post but i have to review the post.&amp;nbsp;</description>
			<pubDate>Fri, 17 Jul 2026 19:54:51 GMT</pubDate>
			<guid>https://rss.chat/?id=342</guid>
			<source:markdown>claude can post but i have to review the post.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=341</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/342.xml"/>
			</item>
		<item>
			<description>BTW, never in a billion years will any of my software ever require a title.&amp;nbsp;</description>
			<pubDate>Fri, 17 Jul 2026 19:45:00 GMT</pubDate>
			<guid>https://rss.chat/?id=339</guid>
			<source:markdown>BTW, never in a billion years will any of my software ever require a title.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;If you type the body text alone, the button is never enabled?&lt;/p&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
			<pubDate>Fri, 17 Jul 2026 19:39:36 GMT</pubDate>
			<guid>https://rss.chat/?id=337</guid>
			<source:markdown>If you type the body text alone, the button is never enabled?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=328</source:inReplyTo>
			<source:comments count="2" feedUrl="https://rss.chat/users/dave/comments/337.xml"/>
			</item>
		<item>
			<description>This is a test. This item does not have a title.</description>
			<pubDate>Fri, 17 Jul 2026 19:34:57 GMT</pubDate>
			<guid>https://rss.chat/?id=331</guid>
			<source:markdown>This is a test. This item does not have a title.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/331.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;New feature.&lt;/p&gt;&lt;p&gt;If you open a second copy of &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; in a different tab, the version you left behind will put up a dialog saying you can either close the tab or reload the page.&amp;nbsp;&lt;/p&gt;&lt;p&gt;This keeps us from losing data. ;-)&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 15:57:23 GMT</pubDate>
			<guid>https://rss.chat/?id=327</guid>
			<source:markdown>New feature.&#10;&#10;If you open a second copy of rss.chat in a different tab, the version you left behind will put up a dialog saying you can either close the tab or reload the page.&#10;&#10;This keeps us from losing data. ;-)</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Welcome to the new land. :-)&lt;/p&gt;&lt;p&gt;Sorry there was a problem.&amp;nbsp;&lt;/p&gt;&lt;p&gt;If you want, please let us know what happened.&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 15:17:57 GMT</pubDate>
			<guid>https://rss.chat/?id=326</guid>
			<source:markdown>Welcome to the new land. :-)&#10;&#10;Sorry there was a problem.&#10;&#10;If you want, please let us know what happened.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=325</source:inReplyTo>
			</item>
		<item>
			<title>Feed discovery</title>
			<description>&lt;p&gt;New &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; feature: It now supports feed discovery, so you can subscribe to any html page on a &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; site, in a compatible feed reader.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I tested it in FeedLand and NetNewsWire and it works.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 14:28:28 GMT</pubDate>
			<guid>https://rss.chat/?id=323</guid>
			<source:markdown>New [rss.chat](http://rss.chat) feature: It now supports feed discovery, so you can subscribe to any html page on a [rss.chat](http://rss.chat) site, in a compatible feed reader.&#10;&#10;I tested it in FeedLand and NetNewsWire and it works.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;I'm glad you're looking at this, of course I am too. Been using Twitter for 20 years, and gave up trying to get cross-posting working in 2017.&amp;nbsp;&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 would love to talk about this, because the text limits are the only thing holding their dynasty up, the fact that their limits are different from all their competitors. If there was a universal definition of what &quot;web text&quot; is -- well they'd be screwed. It wouldn't matter where you wrote the text, it would still play on Bluesky.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;And if we didn't have to no one would use their editor.&lt;/p&gt;&lt;p&gt;Same for Substack btw. I wanted to do my writing in my editor. No can do, they say.&lt;/p&gt;&lt;p&gt;I think that incompatibility is the only thing holding up their dynasty, t&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;he idea that 300 is better than 10K as a character limit.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;The pressure on them to do it is coming from Leaflet et al.&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;Either Bluesky relents, or we'll eventually get them working with us on the web, where there are no freaking character limits.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;What do you think of that?&lt;/p&gt;&lt;p&gt;PS:&amp;nbsp;They would also have to support inbound and outbound RSS.&lt;/p&gt;&lt;p&gt;PPS: I chat regularly with the Leaflet people. Very smart and business-like. I also know the new Bluesky management, somewhat -- he comes from Automattic. I had a meeting with him a couple of years ago basically to talk about storage and identity -- they were launching a new identity service, and I desperately wanted them to add storage so we could have an ecosystem of apps sharing data. That part of what AT Proto is doing -- I support, but the business model is all wrong. The users should pay for the storage, and give permission to apps. The Leaflet style app is reselling Amazon S3 storage, which is a shitty business for a smallish entrepreneur.&lt;/p&gt;&lt;p&gt;PPPS: If Toni reads this, I'd be happy to chat. It's all getting sooo interesting now.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 13:59:14 GMT</pubDate>
			<guid>https://rss.chat/?id=322</guid>
			<source:markdown>I'm glad you're looking at this, of course I am too. Been using Twitter for 20 years, and gave up trying to get cross-posting working in 2017.&#10;&#10;I would love to talk about this, because the text limits are the only thing holding their dynasty up, the fact that their limits are different from all their competitors. If there was a universal definition of what &quot;web text&quot; is -- well they'd be screwed. It wouldn't matter where you wrote the text, it would still play on Bluesky.&#10;&#10;And if we didn't have to no one would use their editor.&#10;&#10;Same for Substack btw. I wanted to do my writing in my editor. No can do, they say.&#10;&#10;I think that incompatibility is the only thing holding up their dynasty, the idea that 300 is better than 10K as a character limit.&#10;&#10;The pressure on them to do it is coming from Leaflet et al. Either Bluesky relents, or we'll eventually get them working with us on the web, where there are no freaking character limits.&#10;&#10;What do you think of that?&#10;&#10;PS: They would also have to support inbound and outbound RSS.&#10;&#10;PPS: I chat regularly with the Leaflet people. Very smart and business-like. I also know the new Bluesky management, somewhat -- he comes from Automattic. I had a meeting with him a couple of years ago basically to talk about storage and identity -- they were launching a new identity service, and I desperately wanted them to add storage so we could have an ecosystem of apps sharing data. That part of what AT Proto is doing -- I support, but the business model is all wrong. The users should pay for the storage, and give permission to apps. The Leaflet style app is reselling Amazon S3 storage, which is a shitty business for a smallish entrepreneur.&#10;&#10;PPPS: If Toni reads this, I'd be happy to chat. It's all getting sooo interesting now.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=321</source:inReplyTo>
			</item>
		<item>
			<title>Image support? Yes.</title>
			<description>&lt;p&gt;BTW, I told Claude yesterday that we will support images in posts. I wanted it earlier when chaos still ruled (believe me it was very hard to use at this time) and it talked me out of it, saying it was too expensive.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I don't think it will be too expensive. And if it does, then we'll find a way to get money flowing through this project without holding things up.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 13:14:30 GMT</pubDate>
			<guid>https://rss.chat/?id=320</guid>
			<source:markdown>BTW, I told Claude yesterday that we will support images in posts. I wanted it earlier when chaos still ruled (believe me it was very hard to use at this time) and it talked me out of it, saying it was too expensive.&#10;&#10;I don't think it will be too expensive. And if it does, then we'll find a way to get money flowing through this project without holding things up.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Andrew, I just wrote a &lt;a href=&quot;http://scripting.com/2026/07/17.html#a125511&quot;&gt;post&lt;/a&gt; on my blog about Mastodon, and how it assumed Twitter's feature list as their todo list, and why imho that was a mistake.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We're just getting started here, and I want to go easy on nailing things down. I wouldn't limit &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; to only working with AT Proto (for example) as lots of developers do. Instead I'm not working with it, and hope to pull Bluesky out of their non-web architecture out into the wild web, that may not have made Bluesky possible (they grew out of Twitter) but it certainly made Twitter possible. ;-)&lt;/p&gt;&lt;p&gt;So that's why this might not be a solvable problem at this time. But starting the discussion with the WordPress people, well, it's always a good time to do that. :-)&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 13:12:42 GMT</pubDate>
			<guid>https://rss.chat/?id=319</guid>
			<source:markdown>Andrew, I just wrote a [post](http://scripting.com/2026/07/17.html#a125511) on my blog about Mastodon, and how it assumed Twitter's feature list as their todo list, and why imho that was a mistake.&#10;&#10;We're just getting started here, and I want to go easy on nailing things down. I wouldn't limit rss.chat to only working with AT Proto (for example) as lots of developers do. Instead I'm not working with it, and hope to pull Bluesky out of their non-web architecture out into the wild web, that may not have made Bluesky possible (they grew out of Twitter) but it certainly made Twitter possible. ;-)&#10;&#10;So that's why this might not be a solvable problem at this time. But starting the discussion with the WordPress people, well, it's always a good time to do that. :-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=316</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/319.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Andrew I sent an email to Jeremy Herve at Automattic, cc'd to you.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I authorized his email account to be part of the discussion here.&lt;/p&gt;&lt;p&gt;At some point you should open a thread where everyone can participate on the repo.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/issues&quot;&gt;https://github.com/scripting/rss.chat/issues&lt;/a&gt;&lt;/div&gt;</description>
			<pubDate>Fri, 17 Jul 2026 12:54:41 GMT</pubDate>
			<guid>https://rss.chat/?id=318</guid>
			<source:markdown>Andrew I sent an email to Jeremy Herve at Automattic, cc'd to you.&#10;&#10;I authorized his email account to be part of the discussion here.&#10;&#10;At some point you should open a thread where everyone can participate on the repo.&#10;&#10;https://github.com/scripting/rss.chat/issues</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=316</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/318.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;1. Yes -- the name is &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;&lt;p&gt;2. It's not part of textcasting because it isn't about text, it's about structure.&amp;nbsp;&lt;/p&gt;&lt;p&gt;3. Is all that's in the way is having a permalink for a comment? Can comments in WordPress have comments?&lt;/p&gt;&lt;p&gt;I don't want to be held back by trying to work with an existing product that has a different view of the web. WordPress is very close, because they support textcasting, but their view of discourse is not as simple as &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt;'s view and at the same time not as powerful.&amp;nbsp;&lt;/p&gt;&lt;p&gt;They do it the way comments on blogs have always worked, more or less, although I should point out that &lt;a href=&quot;http://discuss.userland.com&quot;&gt;discuss.userland.com&lt;/a&gt; didn't make a distinction between comments and posts, nor did its predecessor LBBS. We had those kinds of discussions while this was under development. I did offer to work with WordPress on this stuff, but they went in a different direction -- ActivityPub and AT Proto. I do think eventually they will want to be involved here. Since they've been pioneering a new path here, maybe we should find out what they think?&amp;nbsp;&lt;/p&gt;&lt;p&gt;Anyway -- I will send a link to this post to Jeremy Herve at Automattic, he commented on this last week when we rolled it out publicly, and he's a good guy -- I think they went the wrong way, but I've made a few bets like that myself. ;-)&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Fri, 17 Jul 2026 12:44:05 GMT</pubDate>
			<guid>https://rss.chat/?id=317</guid>
			<source:markdown>1\. Yes -- the name is rss.chat.&#10;&#10;2\. It's not part of textcasting because it isn't about text, it's about structure.&#10;&#10;3\. Is all that's in the way is having a permalink for a comment? Can comments in WordPress have comments?&#10;&#10;I don't want to be held back by trying to work with an existing product that has a different view of the web. WordPress is very close, because they support textcasting, but their view of discourse is not as simple as rss.chat's view and at the same time not as powerful.&#10;&#10;They do it the way comments on blogs have always worked, more or less, although I should point out that discuss.userland.com didn't make a distinction between comments and posts, nor did its predecessor LBBS. We had those kinds of discussions while this was under development. I did offer to work with WordPress on this stuff, but they went in a different direction -- ActivityPub and AT Proto. I do think eventually they will want to be involved here. Since they've been pioneering a new path here, maybe we should find out what they think?&#10;&#10;Anyway -- I will send a link to this post to Jeremy Herve at Automattic, he commented on this last week when we rolled it out publicly, and he's a good guy -- I think they went the wrong way, but I've made a few bets like that myself. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=316</source:inReplyTo>
			</item>
		<item>
			<title>&quot;goodnightkiss&quot; messages coming tomorrow</title>
			<description>&lt;p&gt;Tomorrow the plan is to add a new websocket-based way of making sure that only one copy of &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; is running at the same time. When you log on, on another computer or even on the same computer, this creates another copy of appPrefs.&amp;nbsp;&lt;/p&gt;&lt;p&gt;If you change something, they get saved to the server. Meanwhile on another machine it doesn't have the new version, it has values that you don't want to write over the ones you changed on the other machine.&amp;nbsp;&lt;/p&gt;&lt;p&gt;So when you log on, the server sends a &quot;goodnightkiss&quot; message to every copy it's connected to with your username. They then put up a dialog saying if you want to continue using &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; you have to reload.&amp;nbsp;&lt;/p&gt;&lt;p&gt;All this is working in WordLand and FeedLand, so it's pretty likely it'll work right away. I know that sounds cocky, but that's how it's been going. It's like Claude is both a compiler and runtime, and I haven't seen any mistakes go by it without it catching them.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 22:05:52 GMT</pubDate>
			<guid>https://rss.chat/?id=312</guid>
			<source:markdown>Tomorrow the plan is to add a new websocket-based way of making sure that only one copy of rss.chat is running at the same time. When you log on, on another computer or even on the same computer, this creates another copy of appPrefs.&#10;&#10;If you change something, they get saved to the server. Meanwhile on another machine it doesn't have the new version, it has values that you don't want to write over the ones you changed on the other machine.&#10;&#10;So when you log on, the server sends a &quot;goodnightkiss&quot; message to every copy it's connected to with your username. They then put up a dialog saying if you want to continue using rss.chat you have to reload.&#10;&#10;All this is working in WordLand and FeedLand, so it's pretty likely it'll work right away. I know that sounds cocky, but that's how it's been going. It's like Claude is both a compiler and runtime, and I haven't seen any mistakes go by it without it catching them.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Andrew -- I'm interested. Is there a use-case you have in mind.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Not sure I would add anything to this element, but could create another element, and the use-case will give me an idea how to present it.&lt;/p&gt;&lt;p&gt;In general I don't like to add features until I have an actual use for it.&lt;/p&gt;&lt;p&gt;That said, I want encourage you to look over the source namespace and make comments and suggestions.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 21:46:30 GMT</pubDate>
			<guid>https://rss.chat/?id=311</guid>
			<source:markdown>Andrew -- I'm interested. Is there a use-case you have in mind.&#10;&#10;Not sure I would add anything to this element, but could create another element, and the use-case will give me an idea how to present it.&#10;&#10;In general I don't like to add features until I have an actual use for it.&#10;&#10;That said, I want encourage you to look over the source namespace and make comments and suggestions.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=309</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/311.xml"/>
			</item>
		<item>
			<description>Scott is my bossman when it comes to stuff like this. :-)</description>
			<pubDate>Thu, 16 Jul 2026 16:26:13 GMT</pubDate>
			<guid>https://rss.chat/?id=306</guid>
			<source:markdown>Scott is my bossman when it comes to stuff like this. :-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=305</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;We have to teach my Claude to do that too. We keep coming up with how useful it would be for it to have a throwaway instance to test with. I don't have the bandwidth to branch out into that area. Usual story. ;-)&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 15:53:14 GMT</pubDate>
			<guid>https://rss.chat/?id=303</guid>
			<source:markdown>We have to teach my Claude to do that too. We keep coming up with how useful it would be for it to have a throwaway instance to test with. I don't have the bandwidth to branch out into that area. Usual story. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=302</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/303.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Also, Claude has an account here, and will post, but only under my careful scrutiny.&lt;/p&gt;&lt;p&gt;For some reason I let it run wild on the docs. I don't generally review them, and I hope we develop a community that can read them and make note of things that don't sound right.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 14:51:05 GMT</pubDate>
			<guid>https://rss.chat/?id=300</guid>
			<source:markdown>Also, Claude has an account here, and will post, but only under my careful scrutiny.&#10;&#10;For some reason I let it run wild on the docs. I don't generally review them, and I hope we develop a community that can read them and make note of things that don't sound right.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=299</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/300.xml"/>
			</item>
		<item>
			<title>How the project works, division of labor</title>
			<description>&lt;p&gt;There have also been changes in the client and we're about to do something that connects client and server. Will document later. ;-)&lt;/p&gt;&lt;p&gt;There's a difference between the client and the theme. I have to write that up soon, but it's something that might not be immediately obvious. There's a replaceable box in the middle of the app. Only Claude writes code in that space, I insist that it talk to me as a user when it comes to that, I don't want any other perspective, where as in the rest of the code, I am the author, but I get support from Claude. Lots of support.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 14:48:25 GMT</pubDate>
			<guid>https://rss.chat/?id=299</guid>
			<source:markdown>There have also been changes in the client and we're about to do something that connects client and server. Will document later. ;-)&#10;&#10;There's a difference between the client and the theme. I have to write that up soon, but it's something that might not be immediately obvious. There's a replaceable box in the middle of the app. Only Claude writes code in that space, I insist that it talk to me as a user when it comes to that, I don't want any other perspective, where as in the rest of the code, I am the author, but I get support from Claude. Lots of support.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=296</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/299.xml"/>
			</item>
		<item>
			<description>Not yet, we generally update the repo at the end of a session. We're still working on stuff.&amp;nbsp;</description>
			<pubDate>Thu, 16 Jul 2026 14:45:51 GMT</pubDate>
			<guid>https://rss.chat/?id=297</guid>
			<source:markdown>Not yet, we generally update the repo at the end of a session. We're still working on stuff.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=296</source:inReplyTo>
			</item>
		<item>
			<title>New sub-menu on Docs menu</title>
			<description>&lt;p&gt;Title of the menu -- RSS &amp;amp; OPML.&lt;/p&gt;&lt;p&gt;Links to the RSS 2.0 spec, the OPML 2.0 spec, source namespace and the RSS as a social network walkthrough.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 14:28:26 GMT</pubDate>
			<guid>https://rss.chat/?id=295</guid>
			<source:markdown>Title of the menu -- RSS &amp; OPML.&#10;&#10;Links to the RSS 2.0 spec, the OPML 2.0 spec, source namespace and the RSS as a social network walkthrough.</source:markdown>
			</item>
		<item>
			<title>A feed icon on every post</title>
			<description>&lt;p&gt;There's now a feed icon on every post.&lt;/p&gt;&lt;p&gt;When you click it a new tab opens with the post, ready to &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;paste into your feed reader.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;p&gt;A &lt;a href=&quot;http://scripting.com/2026/07/16/134247.html&quot;&gt;blog post&lt;/a&gt; with a screen shot and explainer.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Thu, 16 Jul 2026 14:04:09 GMT</pubDate>
			<guid>https://rss.chat/?id=294</guid>
			<source:markdown>There's now a feed icon on every post.&#10;&#10;When you click it a new tab opens with the post, ready to paste into your feed reader.&#10;&#10;A [blog post](http://scripting.com/2026/07/16/134247.html) with a screen shot and explainer.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/294.xml"/>
			</item>
		<item>
			<description>I'm taking a screen shot of this post, so I need there to be a reply. ;-)</description>
			<pubDate>Thu, 16 Jul 2026 13:47:10 GMT</pubDate>
			<guid>https://rss.chat/?id=291</guid>
			<source:markdown>I'm taking a screen shot of this post, so I need there to be a reply. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=285</source:inReplyTo>
			</item>
		<item>
			<description>We undid this, it works this way now. One server. Makes setup much easier. Please check it out, and do the upgrade on your instance.&amp;nbsp;</description>
			<pubDate>Thu, 16 Jul 2026 13:46:38 GMT</pubDate>
			<guid>https://rss.chat/?id=290</guid>
			<source:markdown>We undid this, it works this way now. One server. Makes setup much easier. Please check it out, and do the upgrade on your instance.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=262</source:inReplyTo>
			<source:comments count="2" feedUrl="https://rss.chat/users/dave/comments/290.xml"/>
			</item>
		<item>
			<title>Feed URLs change</title>
			<description>&lt;p&gt;The URLs for the feeds have changed. If you haven't subscribed to any of the feeds here, you don't need to do anything. But if you have, you should read this note, and subscribe via the new URL and unsub from the old one.&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/issues/7&quot;&gt;https://github.com/scripting/rss.chat/issues/7&lt;/a&gt;&lt;/div&gt;</description>
			<pubDate>Thu, 16 Jul 2026 13:17:59 GMT</pubDate>
			<guid>https://rss.chat/?id=289</guid>
			<source:markdown>The URLs for the feeds have changed. If you haven't subscribed to any of the feeds here, you don't need to do anything. But if you have, you should read this note, and subscribe via the new URL and unsub from the old one.&#10;&#10;https://github.com/scripting/rss.chat/issues/7</source:markdown>
			</item>
		<item>
			<title>Simpler instance-starting</title>
			<description>&lt;p&gt;We just converted both &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; and &lt;a href=&quot;http://demo.rss.chat&quot;&gt;demo.rss.chat&lt;/a&gt; to use a different storage system, instead of using Amazon S3 to store the feeds, we're storing them in our database. So instead of there being two domains for on system, now there's only one. Cuts out one of the most complicated parts of setting up a new instance.&amp;nbsp;&lt;/p&gt;&lt;p&gt;So if this works, it will show up on the blogroll on Scripting News, which is watching the old url, which should redirect to the new one.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Wed, 15 Jul 2026 21:53:24 GMT</pubDate>
			<guid>https://rss.chat/?id=285</guid>
			<source:markdown>We just converted both rss.chat and demo.rss.chat to use a different storage system, instead of using Amazon S3 to store the feeds, we're storing them in our database. So instead of there being two domains for on system, now there's only one. Cuts out one of the most complicated parts of setting up a new instance.&#10;&#10;So if this works, it will show up on the blogroll on Scripting News, which is watching the old url, which should redirect to the new one.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/285.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;There's a new sub-menu for all pages on the GitHub repo.&lt;/p&gt;&lt;p&gt;The first two we're linking to are the worknotes files for the client and server.&lt;/p&gt;&lt;p&gt;We've just turned this over to Claude, previously I was taking the notes in my code, and they were spotty. Now Claude can add things to the worknotes files without my supervision.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Basically everything on the repo site that doesn't say otherwise was written by Claude.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Wed, 15 Jul 2026 12:03:01 GMT</pubDate>
			<guid>https://rss.chat/?id=283</guid>
			<source:markdown>There's a new sub-menu for all pages on the GitHub repo.&#10;&#10;The first two we're linking to are the worknotes files for the client and server.&#10;&#10;We've just turned this over to Claude, previously I was taking the notes in my code, and they were spotty. Now Claude can add things to the worknotes files without my supervision.&#10;&#10;Basically everything on the repo site that doesn't say otherwise was written by Claude.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=282</source:inReplyTo>
			</item>
		<item>
			<description>There's a Docs menu, so now I have a place to put links to docs. Coming soooon.&amp;nbsp;</description>
			<pubDate>Tue, 14 Jul 2026 22:57:50 GMT</pubDate>
			<guid>https://rss.chat/?id=282</guid>
			<source:markdown>There's a Docs menu, so now I have a place to put links to docs. Coming soooon.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/282.xml"/>
			</item>
		<item>
			<description>How could I try your product? Do you have a demo site?</description>
			<pubDate>Tue, 14 Jul 2026 22:54:00 GMT</pubDate>
			<guid>https://rss.chat/?id=281</guid>
			<source:markdown>How could I try your product? Do you have a demo site?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=280</source:inReplyTo>
			<source:comments count="2" feedUrl="https://rss.chat/users/dave/comments/281.xml"/>
			</item>
		<item>
			<description>I went back to the top of the thread, I think the question you asked was answered with the item-level &amp;lt;source&amp;gt; element?</description>
			<pubDate>Tue, 14 Jul 2026 20:15:14 GMT</pubDate>
			<guid>https://rss.chat/?id=279</guid>
			<source:markdown>I went back to the top of the thread, I think the question you asked was answered with the item-level &lt;source&gt; element?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=276</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/279.xml"/>
			</item>
		<item>
			<description>What does that mean to someone who doesn't know what microsub is?</description>
			<pubDate>Tue, 14 Jul 2026 16:40:12 GMT</pubDate>
			<guid>https://rss.chat/?id=277</guid>
			<source:markdown>What does that mean to someone who doesn't know what microsub is?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=276</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/277.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Not sure about this one. I understand the need for it, but how to fit it in, not sure.&lt;/p&gt;&lt;p&gt;We're going to move slowly here and hopefully there will be products that offer special features like this, highly customizable, using a variety of different approaches.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Remember, this is an attempt at a bootstrap -- not a silo. We're just here now to help get a bit of a fire burning. It's not like other systems where it can't happen unless the platform vendor does it. This is open and cloneable, and open source.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Tue, 14 Jul 2026 11:37:31 GMT</pubDate>
			<guid>https://rss.chat/?id=275</guid>
			<source:markdown>Not sure about this one. I understand the need for it, but how to fit it in, not sure.&#10;&#10;We're going to move slowly here and hopefully there will be products that offer special features like this, highly customizable, using a variety of different approaches.&#10;&#10;Remember, this is an attempt at a bootstrap -- not a silo. We're just here now to help get a bit of a fire burning. It's not like other systems where it can't happen unless the platform vendor does it. This is open and cloneable, and open source.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=272</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Ricardo, the information is in the feed in the &amp;lt;source&amp;gt; element.&amp;nbsp;&lt;/p&gt;&lt;p&gt;This is a not-often-used element from core RSS 2.0.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Now most feed readers don't look for it, but it's there.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Tue, 14 Jul 2026 11:35:05 GMT</pubDate>
			<guid>https://rss.chat/?id=274</guid>
			<source:markdown>Ricardo, the information is in the feed in the &lt;source&gt; element.&#10;&#10;This is a not-often-used element from core RSS 2.0.&#10;&#10;Now most feed readers don't look for it, but it's there.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=271</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/274.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;In setting up the new server I forgot to configure the location of the S3 files for the feeds so we were overwriting the feeds for&amp;nbsp;&lt;a href=&quot;http://rss.chat&quot; style=&quot;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;rss.chat&lt;/a&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;.&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;When I post this, &lt;a href=&quot;https://users.rss.network/dave/rss.xml&quot;&gt;my personal feed&lt;/a&gt; and the &lt;a href=&quot;https://users.rss.network/rss.xml&quot;&gt;everyone feed&lt;/a&gt; should rebuild and be good.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;</description>
			<pubDate>Mon, 13 Jul 2026 20:58:09 GMT</pubDate>
			<guid>https://rss.chat/?id=270</guid>
			<source:markdown>In setting up the new server I forgot to configure the location of the S3 files for the feeds so we were overwriting the feeds for [rss.chat](http://rss.chat).&#10;&#10;When I post this, [my personal feed](https://users.rss.network/dave/rss.xml) and the [everyone feed](https://users.rss.network/rss.xml) should rebuild and be good.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Thanks Scott, that's high praise. :-)&lt;/p&gt;&lt;p&gt;I just finished my installation and the new server, &lt;a href=&quot;http://demo.rss.chat&quot;&gt;demo.rss.chat&lt;/a&gt;, is up and running.&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;We have more excellent stuff in the pipe, still working out some details.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;Also the &lt;a href=&quot;http://worknotes.md&quot;&gt;worknotes.md&lt;/a&gt; files are working now. Claude is doing all the change notes there.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md&quot;&gt;worknotes for server&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md&quot;&gt;worknotes for client&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;i&gt;Still diggin&lt;/i&gt; as they say.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 13 Jul 2026 16:33:13 GMT</pubDate>
			<guid>https://rss.chat/?id=267</guid>
			<source:markdown>Thanks Scott, that's high praise. :-)&#10;&#10;I just finished my installation and the new server, demo.rss.chat, is up and running.&#10;&#10;We have more excellent stuff in the pipe, still working out some details.&#10;&#10;Also the worknotes.md files are working now. Claude is doing all the change notes there.&#10;&#10;[worknotes for server](https://github.com/scripting/rss.chat/blob/main/server/code/worknotes.md)&#10;&#10;[worknotes for client](https://github.com/scripting/rss.chat/blob/main/client/code/worknotes.md)&#10;&#10;_Still diggin_ as they say.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=266</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Ricardo, this is great and it's one of the reasons I wanted you here. The other was calling your RSS and OPML support &quot;load bearing&quot; in your app. ✓😀&lt;/p&gt;&lt;p&gt;Anyway, I am just about to start my test of the current install instructions.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We're not going to change that for a while, but I'm happy to help spread the word on new easier ways to do it. And then when the time comes, we can have alternate methods for doing an install.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 13 Jul 2026 13:29:49 GMT</pubDate>
			<guid>https://rss.chat/?id=260</guid>
			<source:markdown>Ricardo, this is great and it's one of the reasons I wanted you here. The other was calling your RSS and OPML support &quot;load bearing&quot; in your app. ✓😀&#10;&#10;Anyway, I am just about to start my test of the current install instructions.&#10;&#10;We're not going to change that for a while, but I'm happy to help spread the word on new easier ways to do it. And then when the time comes, we can have alternate methods for doing an install.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=257</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/260.xml"/>
			</item>
		<item>
			<title>Yes to running your own server</title>
			<description>&lt;p&gt;Good morning sports fans!&lt;/p&gt;&lt;p&gt;This is the URL of one of the many blog posts I wrote over the weekend.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;http://scripting.com/2026/07/12/121948.html&quot;&gt;http://scripting.com/2026/07/12/121948.html&lt;/a&gt;&lt;/div&gt;&lt;div&gt;I also did a podcast.&lt;/div&gt;&lt;div&gt;&lt;div&gt;&lt;a href=&quot;https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html&quot;&gt;https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div&gt;If you want to know where we're going, listen to the podcast. I ramble a lot, people who have heard me speak or talk on the phone know that I do that a lot. But if you're using &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt;, esp if you're a developer, the ideas here are new, when applied to social networks on the web.&amp;nbsp;&lt;/div&gt;&lt;p&gt;What you'll see there is a consistent theme, the action isn't in the &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; client, which is nice for sure -- but it's just the beginning. It's set up so that it can easily be replaced, on both ends, in the client or the server.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Ricardo, who we'll get to know, is a developer who is already signed on to this philosophy, and is running a FeedLand server, wants to get going with the server here, and I say yes! That's the way to go. We have to create a wave, to reinstate the web as the home of social networking on the web (saying it that way sounds silly, but people need to be reminded that the web is still there, and ready to be of service.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It so happens my first big task for the day is to create a second server for myself, thus testing the install instructions, and also to have an answer for people who want to kick the tires. This one will be open to anyone. No whitelist.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 13 Jul 2026 13:12:57 GMT</pubDate>
			<guid>https://rss.chat/?id=258</guid>
			<source:markdown>Good morning sports fans!&#10;&#10;This is the URL of one of the many blog posts I wrote over the weekend.&#10;&#10;[http://scripting.com/2026/07/12/121948.html](http://scripting.com/2026/07/12/121948.html)&#10;&#10;I also did a podcast.&#10;&#10;https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html&#10;&#10;If you want to know where we're going, listen to the podcast. I ramble a lot, people who have heard me speak or talk on the phone know that I do that a lot. But if you're using rss.chat, esp if you're a developer, the ideas here are new, when applied to social networks on the web.&#10;&#10;What you'll see there is a consistent theme, the action isn't in the [rss.chat](http://rss.chat) client, which is nice for sure -- but it's just the beginning. It's set up so that it can easily be replaced, on both ends, in the client or the server.&#10;&#10;Ricardo, who we'll get to know, is a developer who is already signed on to this philosophy, and is running a FeedLand server, wants to get going with the server here, and I say yes! That's the way to go. We have to create a wave, to reinstate the web as the home of social networking on the web (saying it that way sounds silly, but people need to be reminded that the web is still there, and ready to be of service.&#10;&#10;It so happens my first big task for the day is to create a second server for myself, thus testing the install instructions, and also to have an answer for people who want to kick the tires. This one will be open to anyone. No whitelist.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;If you know how to do it we’ll support you.&lt;br&gt;&lt;/p&gt;&lt;p&gt;Also there’s a websockets based firehouse that’s implemented but not yet documented.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 13 Jul 2026 11:19:46 GMT</pubDate>
			<guid>https://rss.chat/?id=255</guid>
			<source:markdown>If you know how to do it we’ll support you.&#10;&#10;Also there’s a websockets based firehouse that’s implemented but not yet documented.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=252</source:inReplyTo>
			</item>
		<item>
			<description>Glad to hear it. I think small groups of people joined by mutual respect, not trying to boil the ocean. And working together as opposed to trying to rule the world.</description>
			<pubDate>Mon, 13 Jul 2026 11:17:59 GMT</pubDate>
			<guid>https://rss.chat/?id=254</guid>
			<source:markdown>Glad to hear it. I think small groups of people joined by mutual respect, not trying to boil the ocean. And working together as opposed to trying to rule the world.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=253</source:inReplyTo>
			</item>
		<item>
			<title>How to install your own rss.chat server</title>
			<description>&lt;p&gt;We have instructions for setting up a new server...&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/blob/main/server/docs/install.md&quot;&gt;https://github.com/scripting/rss.chat/blob/main/server/docs/install.md&lt;/a&gt;&lt;/div&gt;&lt;div&gt;Claude wrote these docs, haven't had a change to test them.&amp;nbsp;&lt;/div&gt;</description>
			<pubDate>Sun, 12 Jul 2026 21:11:06 GMT</pubDate>
			<guid>https://rss.chat/?id=251</guid>
			<source:markdown>We have instructions for setting up a new server...&#10;&#10;[https://github.com/scripting/rss.chat/blob/main/server/docs/install.md](https://github.com/scripting/rss.chat/blob/main/server/docs/install.md)&#10;&#10;Claude wrote these docs, haven't had a change to test them.</source:markdown>
			<source:comments count="2" feedUrl="https://rss.chat/users/dave/comments/251.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Believe me, I agree.&lt;/p&gt;&lt;p&gt;You could also cc @claude as well, it has an account here as well.&lt;/p&gt;</description>
			<pubDate>Sun, 12 Jul 2026 19:58:37 GMT</pubDate>
			<guid>https://rss.chat/?id=249</guid>
			<source:markdown>Believe me, I agree.&#10;&#10;You could also cc @claude as well, it has an account here as well.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=248</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Don, maybe Claude or whatever can explain to us what it does.&lt;/p&gt;&lt;p&gt;Looks like a news reader that can summarize or translate the text on the left side in the right panel. It’s a plug-in, yes? So the text could be coming from anywhere?&lt;/p&gt;</description>
			<pubDate>Sun, 12 Jul 2026 19:57:27 GMT</pubDate>
			<guid>https://rss.chat/?id=247</guid>
			<source:markdown>Don, maybe Claude or whatever can explain to us what it does.&#10;&#10;Looks like a news reader that can summarize or translate the text on the left side in the right panel. It’s a plug-in, yes? So the text could be coming from anywhere?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=246</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/247.xml"/>
			</item>
		<item>
			<title>Frontier finally can do a console.log</title>
			<description>&lt;p&gt;I write my build scripts in Frontier, I might be the last person in the world to do this.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Anyway I had to do a major rewrite of the build script for rss.chat, and got tired of the fact that Frontier doesn't have anything like console.log in JavaScript. So I wrote one.&amp;nbsp;&lt;/p&gt;&lt;p&gt;The console is an outline of course, and there are two verbs, console.start and console.log. And they work very nicely. Each start creates a new top level headline with the time in it, and then the subsequent console.log's go in under the time.&lt;/p&gt;&lt;p&gt;Anyway you can download it &lt;a href=&quot;http://scripting.com/publicfolder/misc/suites.console.fttb&quot;&gt;here&lt;/a&gt;. You won't see anything on your screen but if you View Source you will see it's a &lt;a href=&quot;http://scripting.com/fatpages/about.html&quot;&gt;fat page&lt;/a&gt;. Oh the humanity. ;-)&lt;/p&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Sun, 12 Jul 2026 16:06:48 GMT</pubDate>
			<guid>https://rss.chat/?id=245</guid>
			<source:markdown>I write my build scripts in Frontier, I might be the last person in the world to do this.&#10;&#10;Anyway I had to do a major rewrite of the build script for rss.chat, and got tired of the fact that Frontier doesn't have anything like console.log in JavaScript. So I wrote one.&#10;&#10;The console is an outline of course, and there are two verbs, console.start and console.log. And they work very nicely. Each start creates a new top level headline with the time in it, and then the subsequent console.log's go in under the time.&#10;&#10;Anyway you can download it [here](http://scripting.com/publicfolder/misc/suites.console.fttb). You won't see anything on your screen but if you View Source you will see it's a [fat page](http://scripting.com/fatpages/about.html). Oh the humanity. ;-)</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Don't think of a &quot;network&quot; as necessarily a big thing.&amp;nbsp;&lt;/p&gt;&lt;p&gt;They can be small too, the same software works, but the priorities are different.&lt;/p&gt;</description>
			<pubDate>Sun, 12 Jul 2026 16:02:15 GMT</pubDate>
			<guid>https://rss.chat/?id=244</guid>
			<source:markdown>Don't think of a &quot;network&quot; as necessarily a big thing.&#10;&#10;They can be small too, the same software works, but the priorities are different.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;My first podcast about rss.chat.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html&quot;&gt;https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html&lt;/a&gt;&lt;/div&gt;&lt;div&gt;20 minutes.&lt;/div&gt;</description>
			<pubDate>Sun, 12 Jul 2026 13:28:11 GMT</pubDate>
			<guid>https://rss.chat/?id=243</guid>
			<source:markdown>My first podcast about rss.chat.&#10;&#10;[https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html](https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html)&#10;&#10;20 minutes.</source:markdown>
			</item>
		<item>
			<title>Spam no more</title>
			<description>&lt;p&gt;Getting our email out of spam.&lt;/p&gt;&lt;p&gt;We were using the wrong email address to send the email.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We're now sending email from hello@rss.chat -- and it's fully verified by our mail sender service, SES.&amp;nbsp;&lt;/p&gt;&lt;p&gt;So now when you get a signon link via email it should not be send to spam.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Still diggin!&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 23:56:33 GMT</pubDate>
			<guid>https://rss.chat/?id=242</guid>
			<source:markdown>Getting our email out of spam.&#10;&#10;We were using the wrong email address to send the email.&#10;&#10;We're now sending email from hello@rss.chat -- and it's fully verified by our mail sender service, SES.&#10;&#10;So now when you get a signon link via email it should not be send to spam.&#10;&#10;Still diggin!</source:markdown>
			</item>
		<item>
			<title>Fractional horsepower social networks</title>
			<description>&lt;p&gt;I wrote another long post on Twitter.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://x.com/davewiner/status/2076076891115757616&quot;&gt;https://x.com/davewiner/status/2076076891115757616&lt;/a&gt;&lt;/div&gt;&lt;div&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;The piece is about the small size of RSS.chat, and comparing the bootstrap I have in mind with the one we did for podcasting between 2001 and 2004.&amp;nbsp;&lt;/span&gt;&lt;/div&gt;&lt;div&gt;This goes to answering Manton's question yesterday -- do you remember the Morning Coffee Notes or Trade Secrets podcasts? Almost no one does, but they were the mechanism that the bootstrap of podcasting fed back to the innovators who were doing the booting up. And once it was off and running we didn't need them. Instead I listened to Dawn &amp;amp; Drew and Adam Curry. And shortly after that Morning Edition and Fresh Air.&amp;nbsp;&lt;/div&gt;&lt;div&gt;So in the end this may become just like that, or like blogging -- where I still post on scripting.com every day, but it doesn't play anywhere near the central importance it did in the 90s and 00s.&amp;nbsp;&lt;/div&gt;&lt;div&gt;I am different from most other entrepreneurs. I try to create new media, and it's a success when it takes off and my personal creation fades into the background. It's the new media that's my creation. I'm almost never in it for the money, I'm in it for the thrill of making new media. And as I've said earlier and need to repeat, I am not Mother Teresa, I like making money, I just don't let money get in the way of a great idea, as so many other people do.&amp;nbsp;&lt;/div&gt;&lt;div&gt;Anyway people are listening now. That's really cool. And don't expect me to shut up. It doesn't work that way. 😃&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;</description>
			<pubDate>Sat, 11 Jul 2026 22:57:51 GMT</pubDate>
			<guid>https://rss.chat/?id=241</guid>
			<source:markdown>I wrote another long post on Twitter.&#10;&#10;[https://x.com/davewiner/status/2076076891115757616](https://x.com/davewiner/status/2076076891115757616)&#10;&#10;The piece is about the small size of RSS.chat, and comparing the bootstrap I have in mind with the one we did for podcasting between 2001 and 2004.&#10;&#10;This goes to answering Manton's question yesterday -- do you remember the Morning Coffee Notes or Trade Secrets podcasts? Almost no one does, but they were the mechanism that the bootstrap of podcasting fed back to the innovators who were doing the booting up. And once it was off and running we didn't need them. Instead I listened to Dawn &amp; Drew and Adam Curry. And shortly after that Morning Edition and Fresh Air.&#10;&#10;So in the end this may become just like that, or like blogging -- where I still post on scripting.com every day, but it doesn't play anywhere near the central importance it did in the 90s and 00s.&#10;&#10;I am different from most other entrepreneurs. I try to create new media, and it's a success when it takes off and my personal creation fades into the background. It's the new media that's my creation. I'm almost never in it for the money, I'm in it for the thrill of making new media. And as I've said earlier and need to repeat, I am not Mother Teresa, I like making money, I just don't let money get in the way of a great idea, as so many other people do.&#10;&#10;Anyway people are listening now. That's really cool. And don't expect me to shut up. It doesn't work that way. 😃</source:markdown>
			</item>
		<item>
			<title>The RSS.chat repo on GitHub</title>
			<description>&lt;p&gt;The all--new RSS.chat repo.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat&quot;&gt;https://github.com/scripting/rss.chat&lt;/a&gt;&lt;/div&gt;&lt;p&gt;Two parts, client and server.&lt;/p&gt;&lt;p&gt;Full source in both.&lt;/p&gt;&lt;p&gt;The client is the software that runs in the browser in JavaScript.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It calls the server via api.js -- which is glue we recommend using if you're coming in via JS.&lt;/p&gt;&lt;p&gt;All code open source via MIT license.&lt;/p&gt;&lt;p&gt;Docs right now are minimal, but that will change. That will be Claude's responsibility.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I'm going to write the main readme files.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 22:19:16 GMT</pubDate>
			<guid>https://rss.chat/?id=240</guid>
			<source:markdown>The all--new RSS.chat repo.&#10;&#10;[https://github.com/scripting/rss.chat](https://github.com/scripting/rss.chat)&#10;&#10;Two parts, client and server.&#10;&#10;Full source in both.&#10;&#10;The client is the software that runs in the browser in JavaScript.&#10;&#10;It calls the server via api.js -- which is glue we recommend using if you're coming in via JS.&#10;&#10;All code open source via MIT license.&#10;&#10;Docs right now are minimal, but that will change. That will be Claude's responsibility.&#10;&#10;I'm going to write the main readme files.</source:markdown>
			</item>
		<item>
			<description>Hey Jason, glad to see you made it! ;-)</description>
			<pubDate>Sat, 11 Jul 2026 17:41:02 GMT</pubDate>
			<guid>https://rss.chat/?id=239</guid>
			<source:markdown>Hey Jason, glad to see you made it! ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=237</source:inReplyTo>
			</item>
		<item>
			<title>We don't have to, and won't, do everything</title>
			<description>&lt;p&gt;I think it's cool if there's something micro.blog can add to rss.chat -- so we create the idea that people use both our products because they're different and they interop. Not saying I won't do it, but it's also cool if we don't have to.&lt;/p&gt;&lt;p&gt;In the back of my mind I was thinking we'd offer domains for instances, I'm going to keep this group small, I don't want the whole world here, I want people I have worked with in the past and enjoyed it, like you, Don, Andrew, Jake, Scott -- basically everyone here. I've also invited the guy we were chatting with about his load-bearing OPML app. I'm looking for talented excited people who are on board for interop. But otherwise people can start their own little spaces, or maybe someone will try to make a Bluesky-size system, more power to them. Not saying I'm never going to try to build something but, but not right now.&amp;nbsp;&lt;/p&gt;&lt;p&gt;So for example, if Jake were to start a rss.chat instance I would be happy to give him jake.rss.chat. Pretty sure Scott is going to be among the first to set one up.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Also we don't render a blog from people's feeds, though it has been discussed. I think that would be the place you'd want to have domains point, so it can behave like a blog. I can see a lot of people doing those.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 17:39:04 GMT</pubDate>
			<guid>https://rss.chat/?id=238</guid>
			<source:markdown>I think it's cool if there's something micro.blog can add to rss.chat -- so we create the idea that people use both our products because they're different and they interop. Not saying I won't do it, but it's also cool if we don't have to.&#10;&#10;In the back of my mind I was thinking we'd offer domains for instances, I'm going to keep this group small, I don't want the whole world here, I want people I have worked with in the past and enjoyed it, like you, Don, Andrew, Jake, Scott -- basically everyone here. I've also invited the guy we were chatting with about his load-bearing OPML app. I'm looking for talented excited people who are on board for interop. But otherwise people can start their own little spaces, or maybe someone will try to make a Bluesky-size system, more power to them. Not saying I'm never going to try to build something but, but not right now.&#10;&#10;So for example, if Jake were to start a rss.chat instance I would be happy to give him jake.rss.chat. Pretty sure Scott is going to be among the first to set one up.&#10;&#10;Also we don't render a blog from people's feeds, though it has been discussed. I think that would be the place you'd want to have domains point, so it can behave like a blog. I can see a lot of people doing those.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=214</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Because RSS already has a link element, it would be really ugly to recommend that people do something so heinous that depends on a reader being liberal to work.&lt;/p&gt;&lt;p&gt;It would have to be &amp;lt;source:link&amp;gt;. If that works I'll be &lt;a href=&quot;https://www.merriam-webster.com/dictionary/doggone&quot;&gt;doggone&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 16:24:43 GMT</pubDate>
			<guid>https://rss.chat/?id=236</guid>
			<source:markdown>Because RSS already has a link element, it would be really ugly to recommend that people do something so heinous that depends on a reader being liberal to work.&#10;&#10;It would have to be &lt;source:link&gt;. If that works I'll be [doggone](https://www.merriam-webster.com/dictionary/doggone).</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=234</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I imagine the WordPress community is on top of this?&lt;/p&gt;&lt;p&gt;Wonder if they discuss this somewhere..&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 15:13:39 GMT</pubDate>
			<guid>https://rss.chat/?id=233</guid>
			<source:markdown>I imagine the WordPress community is on top of this?&#10;&#10;Wonder if they discuss this somewhere..</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=232</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/233.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Jeremy Herve, who I know from Automattic, &lt;a href=&quot;https://github.com/scripting/Scripting-News/issues/358#issuecomment-4939682423&quot;&gt;asked a few questions&lt;/a&gt; which I answered.&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 14:05:20 GMT</pubDate>
			<guid>https://rss.chat/?id=231</guid>
			<source:markdown>Jeremy Herve, who I know from Automattic, [asked a few questions](https://github.com/scripting/Scripting-News/issues/358#issuecomment-4939682423) which I answered.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;that's an interesting idea. a group of us get together and decide that since html already has a link element that works the same way atom's does, why bother with the atom part.&amp;nbsp;&lt;/p&gt;&lt;p&gt;their motive goes back 20 years, that little thing has been over forever. i think it's better if we try to fix it, and this idea gives a whole new approach.&amp;nbsp;&lt;/p&gt;&lt;p&gt;andrew, are you tuned in?&lt;/p&gt;</description>
			<pubDate>Sat, 11 Jul 2026 14:03:03 GMT</pubDate>
			<guid>https://rss.chat/?id=230</guid>
			<source:markdown>that's an interesting idea. a group of us get together and decide that since html already has a link element that works the same way atom's does, why bother with the atom part.&#10;&#10;their motive goes back 20 years, that little thing has been over forever. i think it's better if we try to fix it, and this idea gives a whole new approach.&#10;&#10;andrew, are you tuned in?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=229</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/230.xml"/>
			</item>
		<item>
			<title>Day 0 was a success</title>
			<description>&lt;p&gt;It’s been quite a day. At the end, rss.chat is a thing.&lt;/p&gt;&lt;p&gt;More new stuff tomorrow.&lt;/p&gt;&lt;p&gt;Claude is a great freaking partner.&lt;/p&gt;</description>
			<pubDate>Fri, 10 Jul 2026 21:39:24 GMT</pubDate>
			<guid>https://rss.chat/?id=226</guid>
			<source:markdown>It’s been quite a day. At the end, rss.chat is a thing.&#10;&#10;More new stuff tomorrow.&#10;&#10;Claude is a great freaking partner.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;It's very low on my list of things to do, unless it rises to the top, say Feedly, for example, really wants to incorporate our stuff, and they refuse to look for the cloud element. (Which on its face sounds ridiculous.)&lt;/p&gt;&lt;p&gt;I'm more concerned with peering with apps that are trying to create a social network with RSS. That's who I want to work with most.&lt;/p&gt;</description>
			<pubDate>Fri, 10 Jul 2026 20:17:00 GMT</pubDate>
			<guid>https://rss.chat/?id=225</guid>
			<source:markdown>It's very low on my list of things to do, unless it rises to the top, say Feedly, for example, really wants to incorporate our stuff, and they refuse to look for the cloud element. (Which on its face sounds ridiculous.)&#10;&#10;I'm more concerned with peering with apps that are trying to create a social network with RSS. That's who I want to work with most.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=220</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/225.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Also these docs are for you.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://source.scripting.com/social.opml&quot;&gt;https://source.scripting.com/social.opml&lt;/a&gt;&lt;/div&gt;</description>
			<pubDate>Fri, 10 Jul 2026 20:11:59 GMT</pubDate>
			<guid>https://rss.chat/?id=224</guid>
			<source:markdown>Also these docs are for you.&#10;&#10;[https://source.scripting.com/social.opml](https://source.scripting.com/social.opml)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=221</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Don great to see you here!&lt;/p&gt;&lt;p&gt;Everyone else, I've known Don for a long time. In 1988 I think he did a Mac INIT that made it possible to send messages between apps, which was a basic function we needed in Frontier.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Over the years we keep crossing paths and this is another.&lt;/p&gt;</description>
			<pubDate>Fri, 10 Jul 2026 19:59:11 GMT</pubDate>
			<guid>https://rss.chat/?id=223</guid>
			<source:markdown>Don great to see you here!&#10;&#10;Everyone else, I've known Don for a long time. In 1988 I think he did a Mac INIT that made it possible to send messages between apps, which was a basic function we needed in Frontier.&#10;&#10;Over the years we keep crossing paths and this is another.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=221</source:inReplyTo>
			</item>
		<item>
			<title>Shoehorning WebSub in</title>
			<description>&lt;p&gt;Andrew I just had an idea.&amp;nbsp;&lt;/p&gt;&#10;&#10;&lt;p&gt;This is the cloud element in all our feeds.&lt;/p&gt;&#10;&#10;&lt;p&gt;&amp;lt;cloud&amp;nbsp;domain=&quot;rpc.rsscloud.io&quot;&amp;nbsp;port=&quot;5337&quot;&amp;nbsp;path=&quot;/pleaseNotify&quot;&amp;nbsp;registerProcedure=&quot;&quot;&amp;nbsp;protocol=&quot;http-post&quot;/&amp;gt;&lt;/p&gt;&#10;&#10;&lt;p&gt;We could tell sites that expect WebSub callbacks to just ping to your server, and somehow indicate that you want websub notification, that with this server, you can get back websub calls.&lt;/p&gt;&#10;&#10;&lt;p&gt;Makes it perfectly painless, or so it seems.&amp;nbsp;&lt;/p&gt;&#10;&#10;&lt;p&gt;But I'm not sure if you can do it.&lt;/p&gt;</description>
			<pubDate>Fri, 10 Jul 2026 17:53:41 GMT</pubDate>
			<guid>https://rss.chat/?id=219</guid>
			<source:markdown>Andrew I just had an idea.&#10;&#10;This is the cloud element in all our feeds.&#10;&#10;&amp;lt;cloud domain=&quot;rpc.rsscloud.io&quot; port=&quot;5337&quot; path=&quot;/pleaseNotify&quot; registerProcedure=&quot;&quot; protocol=&quot;http-post&quot;/&gt;&#10;&#10;We could tell sites that expect WebSub callbacks to just ping to your server, and somehow indicate that you want websub notification, that with this server, you can get back websub calls.&#10;&#10;Makes it perfectly painless, or so it seems.&#10;&#10;But I'm not sure if you can do it.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/219.xml"/>
			</item>
		<item>
			<title>Welcome to rss.chat</title>
			<description>&lt;p&gt;I've wanted to do this product many years, but couldn't quite figure it out I guess. Or I got lazy, or I guess I kind of gave up, like a lot of people did, on the web as the thing that unifies independent developers so we can create stuff without the permission of people who work at BigCo's. We're doing something different and they keep getting in the way.&lt;/p&gt;&lt;p&gt;I got the energy flowing when I asked Claude if it could make software that does this, and I pasted a screen shot of What's App into the Claude chat window. Of course it said yes. I said do it. And it did. Wasn't doing very much, but I got the idea that we could work inside an app together, which could be a lot more powerful than that asking for consulting help on projects where it can't get in there and feel around.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Almost four months later we have rss.chat. It's not a demo app, it's real.&lt;/p&gt;&lt;p&gt;We're going to do some amazing things from here. I didn't build this platform to stop here, I did it so finally (again) I'd have a place were we can all build together, and honestly fuck the big platform vendors. It's a nightmare compared to where we started, and I know -- I was there.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Fri, 10 Jul 2026 15:29:31 GMT</pubDate>
			<guid>https://rss.chat/?id=218</guid>
			<source:markdown>I've wanted to do this product many years, but couldn't quite figure it out I guess. Or I got lazy, or I guess I kind of gave up, like a lot of people did, on the web as the thing that unifies independent developers so we can create stuff without the permission of people who work at BigCo's. We're doing something different and they keep getting in the way.&#10;&#10;I got the energy flowing when I asked Claude if it could make software that does this, and I pasted a screen shot of What's App into the Claude chat window. Of course it said yes. I said do it. And it did. Wasn't doing very much, but I got the idea that we could work inside an app together, which could be a lot more powerful than that asking for consulting help on projects where it can't get in there and feel around.&#10;&#10;Almost four months later we have rss.chat. It's not a demo app, it's real.&#10;&#10;We're going to do some amazing things from here. I didn't build this platform to stop here, I did it so finally (again) I'd have a place were we can all build together, and honestly fuck the big platform vendors. It's a nightmare compared to where we started, and I know -- I was there.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;I asked Claude to announce a new feature we just added, Surface, in the vertical top level icon bar.&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;It was very much a collaboration, for the last month or so we've been working on how to organize the threads so that they feel like a twitter-like browser, but where the users have better control. I found I was getting lost in rss.chat and just wanted to get the F out of there right now. That's what Surface is for.&lt;/span&gt;&lt;/p&gt;</description>
			<pubDate>Fri, 10 Jul 2026 14:44:13 GMT</pubDate>
			<guid>https://rss.chat/?id=217</guid>
			<source:markdown>I asked Claude to announce a new feature we just added, Surface, in the vertical top level icon bar. It was very much a collaboration, for the last month or so we've been working on how to organize the threads so that they feel like a twitter-like browser, but where the users have better control. I found I was getting lost in rss.chat and just wanted to get the F out of there right now. That's what Surface is for.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=216</source:inReplyTo>
			</item>
		<item>
			<description>This is a very interesting idea. I have lots of domains to play with here. Let me give it some thought, and if anyone has a related idea, bring it on.&amp;nbsp;</description>
			<pubDate>Fri, 10 Jul 2026 14:32:49 GMT</pubDate>
			<guid>https://rss.chat/?id=215</guid>
			<source:markdown>This is a very interesting idea. I have lots of domains to play with here. Let me give it some thought, and if anyone has a related idea, bring it on.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=214</source:inReplyTo>
			</item>
		<item>
			<title>Expand and collapse in the timeline</title>
			<description>New feature, scroll through the timeline, there’s now a wedge to the left of the comment icon. If the item has replies that are not visible it’s dark. Click it, the replies are revealed. Click again to hide them. This makes it easy to browse through the structure of replies and messages and replies and so forth.</description>
			<pubDate>Thu, 09 Jul 2026 22:36:28 GMT</pubDate>
			<guid>https://rss.chat/?id=213</guid>
			<source:markdown>New feature, scroll through the timeline, there’s now a wedge to the left of the comment icon. If the item has replies that are not visible it’s dark. Click it, the replies are revealed. Click again to hide them. This makes it easy to browse through the structure of replies and messages and replies and so forth.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;I never dreamed of writing this piece btw. I guess my dreams got small after a while But I decide now what actual fuck, let's just do it.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I totally could not have done this without Claude Code. Too many facets, too many parts had to work together perfectly. One old dude and Claude can move the web back to where it always should have been. Not too shabby. ;-)&lt;/p&gt;</description>
			<pubDate>Thu, 09 Jul 2026 16:18:47 GMT</pubDate>
			<guid>https://rss.chat/?id=212</guid>
			<source:markdown>I never dreamed of writing this piece btw. I guess my dreams got small after a while But I decide now what actual fuck, let's just do it.&#10;&#10;I totally could not have done this without Claude Code. Too many facets, too many parts had to work together perfectly. One old dude and Claude can move the web back to where it always should have been. Not too shabby. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=211</source:inReplyTo>
			</item>
		<item>
			<title>RSS as a social network</title>
			<description>&lt;p&gt;I'm using this for part of the new docs, on source.scripting.com, about RSS as a social network.&lt;/p&gt;</description>
			<pubDate>Thu, 09 Jul 2026 16:18:08 GMT</pubDate>
			<guid>https://rss.chat/?id=211</guid>
			<source:markdown>I'm using this for part of the new docs, on source.scripting.com, about RSS as a social network.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/211.xml"/>
			</item>
		<item>
			<description>&lt;p&gt;Manton, we're using this post as the demo for the docs I'm writing to explain how the pieces fit together, part of the docs for the source namespace.&lt;/p&gt;&lt;p&gt;I needed to get your feed to rebuild, because we had the name of the server product wrong in the feed. Can't have that for official docs like this.&lt;/p&gt;&lt;p&gt;Keep on truckin! :-)&lt;/p&gt;</description>
			<pubDate>Thu, 09 Jul 2026 12:47:12 GMT</pubDate>
			<guid>https://rss.chat/?id=210</guid>
			<source:markdown>Manton, we're using this post as the demo for the docs I'm writing to explain how the pieces fit together, part of the docs for the source namespace.&#10;&#10;I needed to get your feed to rebuild, because we had the name of the server product wrong in the feed. Can't have that for official docs like this.&#10;&#10;Keep on truckin! :-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=204</source:inReplyTo>
			</item>
		<item>
			<title>New feature, webbing discourse</title>
			<description>&lt;p&gt;We were going to try to get some excellent docs for the new stuff, but I want to do it on a fresh start, not after a full day of programming.&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://users.rss.network/dave/rss.xml&quot;&gt;https://users.rss.network/dave/rss.xml&lt;/a&gt;&lt;/div&gt;&lt;div&gt;That's my rss.chat feed as an example.&lt;/div&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;So, in May we added inReplyTo to a feed item if it's in reply to another item.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;Today we have the other side of it, each post that has comments links to a feed representing the comments. It's in a new &lt;i&gt;source:comments&lt;/i&gt; element in the item&lt;/p&gt;&lt;p&gt;Inside the comments feed, each item links back to the author of the comment with a &lt;i&gt;source&lt;/i&gt; element which is a core feature of RSS 2.0. Perfect in this situation.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Anyway we've now got a network of writing floating around in RSS Land. Not entirely a new thing, but -- the difference here is that each element in the hierarchy is a peer of every other element, there's no top post in this network. Any point in the network can become a meme.&lt;/p&gt;&lt;p&gt;More to come.&lt;/p&gt;</description>
			<pubDate>Wed, 08 Jul 2026 17:50:03 GMT</pubDate>
			<guid>https://rss.chat/?id=209</guid>
			<source:markdown>We were going to try to get some excellent docs for the new stuff, but I want to do it on a fresh start, not after a full day of programming.&#10;&#10;[https://users.rss.network/dave/rss.xml](https://users.rss.network/dave/rss.xml)&#10;&#10;That's my rss.chat feed as an example.&#10;&#10;So, in May we added inReplyTo to a feed item if it's in reply to another item.&#10;&#10;Today we have the other side of it, each post that has comments links to a feed representing the comments. It's in a new _source:comments_ element in the item&#10;&#10;Inside the comments feed, each item links back to the author of the comment with a _source_ element which is a core feature of RSS 2.0. Perfect in this situation.&#10;&#10;Anyway we've now got a network of writing floating around in RSS Land. Not entirely a new thing, but -- the difference here is that each element in the hierarchy is a peer of every other element, there's no top post in this network. Any point in the network can become a meme.&#10;&#10;More to come.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;and then look at the items, you'll see some new stuff there. ;-)&lt;/p&gt;</description>
			<pubDate>Wed, 08 Jul 2026 14:48:19 GMT</pubDate>
			<guid>https://rss.chat/?id=207</guid>
			<source:markdown>and then look at the items, you'll see some new stuff there. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=206</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;hey manton, great to see you here.&lt;/p&gt;&lt;p&gt;this is the web btw.&amp;nbsp;&lt;/p&gt;&lt;p&gt;feeds everywhere&lt;/p&gt;&lt;p&gt;and everything in a feed.&lt;/p&gt;</description>
			<pubDate>Wed, 08 Jul 2026 14:42:55 GMT</pubDate>
			<guid>https://rss.chat/?id=205</guid>
			<source:markdown>hey manton, great to see you here.&#10;&#10;this is the web btw.&#10;&#10;feeds everywhere&#10;&#10;and everything in a feed.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=204</source:inReplyTo>
			<source:comments count="2" feedUrl="https://rss.chat/users/dave/comments/205.xml"/>
			</item>
		<item>
			<title>New RSS thing coming</title>
			<description>&lt;p&gt;There's a new RSS thing coming later today.&lt;/p&gt;&lt;p&gt;We're testing and writing docs.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I think it's going to be kind of a big deal. :-)&lt;/p&gt;</description>
			<pubDate>Wed, 08 Jul 2026 14:26:36 GMT</pubDate>
			<guid>https://rss.chat/?id=203</guid>
			<source:markdown>There's a new RSS thing coming later today.&#10;&#10;We're testing and writing docs.&#10;&#10;I think it's going to be kind of a big deal. :-)</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;More testing. It's that time of year. ;-)&lt;/p&gt;&lt;p&gt;Testing the second part of this feature.&lt;/p&gt;</description>
			<pubDate>Tue, 07 Jul 2026 16:16:35 GMT</pubDate>
			<guid>https://rss.chat/?id=202</guid>
			<source:markdown>More testing. It's that time of year. ;-)&#10;&#10;Testing the second part of this feature.</source:markdown>
			</item>
		<item>
			<title>Technography in the age of AI</title>
			<description>&lt;p&gt;Let me tell you about &lt;a href=&quot;https://www.google.com/search?q=technography+de+koven&quot;&gt;technography&lt;/a&gt;, a subject pioneered by &lt;a href=&quot;https://en.wikipedia.org/wiki/Bernie_De_Koven&quot;&gt;Bernie De Koven&lt;/a&gt; in the 80s, with Living Videotext outliners.&lt;/p&gt;&lt;p&gt;Gather a group of one or more people, in a conference room, projected on a screen everyone could see. In the corner was the technographer, usually Bernie, and he would start the meeting asking for the agenda. They would start naming topics. Then he'd asking where they'd like to start, and he would move that item to the top, and keep going, and someone would say we should talk about this, and so forth.&lt;/p&gt;&lt;p&gt;As some point if it worked, if there was suspension of disbelief, someone would tell Bernie to move that item down, move another item under Sales, and without realizing it they were using a new tool.&amp;nbsp;&lt;/p&gt;&lt;p&gt;In 2026, I could see an app that did that for you or a group. An outliner integrated with AI.&lt;/p&gt;</description>
			<pubDate>Tue, 07 Jul 2026 13:27:05 GMT</pubDate>
			<guid>https://rss.chat/?id=201</guid>
			<source:markdown>Let me tell you about [technography](https://www.google.com/search?q=technography+de+koven), a subject pioneered by [Bernie De Koven](https://en.wikipedia.org/wiki/Bernie_De_Koven) in the 80s, with Living Videotext outliners.&#10;&#10;Gather a group of one or more people, in a conference room, projected on a screen everyone could see. In the corner was the technographer, usually Bernie, and he would start the meeting asking for the agenda. They would start naming topics. Then he'd asking where they'd like to start, and he would move that item to the top, and keep going, and someone would say we should talk about this, and so forth.&#10;&#10;As some point if it worked, if there was suspension of disbelief, someone would tell Bernie to move that item down, move another item under Sales, and without realizing it they were using a new tool.&#10;&#10;In 2026, I could see an app that did that for you or a group. An outliner integrated with AI.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/201.xml"/>
			</item>
		<item>
			<title>Bug 151 appears to be fixed</title>
			<description>&lt;p&gt;Another day more fixes.&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;blockquote&gt;&#10;&lt;p&gt;in the editor, create a link using the link icon, then after the link in the text press Enter, to create a new line. the linebreak shows up in the wrong place.&amp;nbsp; &lt;/p&gt;&#10;&lt;/blockquote&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;That was a bug I reported a while back. Let's see if its still there.&lt;/p&gt;&lt;p&gt;Yesterday I was listening to &lt;a href=&quot;https://www.youtube.com/watch?v=GQQbjpomexo&quot;&gt;Summer Breeze&lt;/a&gt; by Seals and&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;Crofts and the first few times I listened to it, it really reached me. After 18 listens all I could here were the weird embellishments they put into it to make to so addictive? Who knows.&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;Net result, not reproducible. I think we can remove 151 from the list.&lt;/span&gt;&lt;/p&gt;</description>
			<pubDate>Tue, 07 Jul 2026 13:18:17 GMT</pubDate>
			<guid>https://rss.chat/?id=200</guid>
			<source:markdown>Another day more fixes.&#10;&#10;&gt; in the editor, create a link using the link icon, then after the link in the text press Enter, to create a new line. the linebreak shows up in the wrong place.&#10;&#10;That was a bug I reported a while back. Let's see if its still there.&#10;&#10;Yesterday I was listening to [Summer Breeze](https://www.youtube.com/watch?v=GQQbjpomexo) by Seals and Crofts and the first few times I listened to it, it really reached me. After 18 listens all I could here were the weird embellishments they put into it to make to so addictive? Who knows.&#10;&#10;Net result, not reproducible. I think we can remove 151 from the list.</source:markdown>
			</item>
		<item>
			<title>USA loses to Belgium</title>
			<description>&lt;p&gt;How fucked up would it have been if the USA had won the match with Belgium last night.&lt;/p&gt;&lt;p&gt;Quite possibly the reason the Knicks lost when Trump decided to show his face at an NBA Finals match at the Garden in June.&amp;nbsp;&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Tue, 07 Jul 2026 12:25:29 GMT</pubDate>
			<guid>https://rss.chat/?id=199</guid>
			<source:markdown>How fucked up would it have been if the USA had won the match with Belgium last night.&#10;&#10;Quite possibly the reason the Knicks lost when Trump decided to show his face at an NBA Finals match at the Garden in June.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;Claude has a new skill -- it can debug software in the browser, so now I'm out of the loop for having to find the problems, it just did a full survey of common HTML elements you can create in Markdown, and figuring out which ones don't work and then fixing them.&lt;/p&gt;&lt;p&gt;These are some of them. ;-)&lt;/p&gt;</description>
			<pubDate>Mon, 06 Jul 2026 17:27:49 GMT</pubDate>
			<guid>https://rss.chat/?id=198</guid>
			<source:markdown>Claude has a new skill -- it can debug software in the browser, so now I'm out of the loop for having to find the problems, it just did a full survey of common HTML elements you can create in Markdown, and figuring out which ones don't work and then fixing them.&#10;&#10;These are some of them. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=197</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;Andrew, this is what I changed that paragraph to.&lt;/p&gt;&#10;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;There isn't very much I'd have to do beyond adding two Atom elements to my feed, and an Atom namespace declaration in the top line of the file. So it's not an easy thing to do, because I don't see the need for Atom to be a requirement for WebSub, and I'd like for them have had the maturity to do this a different way.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description>
			<pubDate>Mon, 06 Jul 2026 15:34:01 GMT</pubDate>
			<guid>https://rss.chat/?id=196</guid>
			<source:markdown>Andrew, this is what I changed that paragraph to.&#10;&#10;&gt; There isn't very much I'd have to do beyond adding two Atom elements to my feed, and an Atom namespace declaration in the top line of the file. So it's not an easy thing to do, because I don't see the need for Atom to be a requirement for WebSub, and I'd like for them have had the maturity to do this a different way.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=194</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;It was meant to make you think, and apparently it did that, but didn't help you see the reason.&lt;/p&gt;&lt;p&gt;It is explained in the next paragraph.&lt;/p&gt;</description>
			<pubDate>Mon, 06 Jul 2026 14:23:22 GMT</pubDate>
			<guid>https://rss.chat/?id=195</guid>
			<source:markdown>It was meant to make you think, and apparently it did that, but didn't help you see the reason.&#10;&#10;It is explained in the next paragraph.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=194</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I got a little flummoxed by the new UI, but it was a good form of flummoxation.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I replied to a post by Andrew. Back in the timeline there's the reply. First anxiety quelled. It made it to the server and people can see it.&lt;/p&gt;&lt;p&gt;But where is what it is in reply to?&lt;/p&gt;&lt;p&gt;Calm down and look above the reply, there's a link there, well-labeled.&lt;/p&gt;&lt;p&gt;Lots of changes in the last few days, and I need people to try reading it in a serial fashion. That is come back every few hours to see if something new is posted. And if you see something you have something to add to, reply. And see how quickly you are satisfied your reply was received.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Mon, 06 Jul 2026 13:54:53 GMT</pubDate>
			<guid>https://rss.chat/?id=193</guid>
			<source:markdown>I got a little flummoxed by the new UI, but it was a good form of flummoxation.&#10;&#10;I replied to a post by Andrew. Back in the timeline there's the reply. First anxiety quelled. It made it to the server and people can see it.&#10;&#10;But where is what it is in reply to?&#10;&#10;Calm down and look above the reply, there's a link there, well-labeled.&#10;&#10;Lots of changes in the last few days, and I need people to try reading it in a serial fashion. That is come back every few hours to see if something new is posted. And if you see something you have something to add to, reply. And see how quickly you are satisfied your reply was received.</source:markdown>
			</item>
		<item>
			<description>&lt;p&gt;You are mentioned prominently in this post.&amp;nbsp;&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;http://scripting.com/2026/07/06/134045.html&quot;&gt;http://scripting.com/2026/07/06/134045.html&lt;/a&gt;&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;</description>
			<pubDate>Mon, 06 Jul 2026 13:51:14 GMT</pubDate>
			<guid>https://rss.chat/?id=192</guid>
			<source:markdown>You are mentioned prominently in this post.&#10;&#10;[http://scripting.com/2026/07/06/134045.html](http://scripting.com/2026/07/06/134045.html)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=180</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/192.xml"/>
			</item>
		<item>
			<title>Testing lists, images, styling, links</title>
			<description>&lt;p&gt;Here's a list&lt;/p&gt;&#10;&#10;&lt;ol&gt;&#10;&lt;li&gt;hello&lt;/li&gt;&#10;&lt;li&gt;goodbye&lt;/li&gt;&#10;&lt;li&gt;you say&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&#10;&lt;p&gt;&lt;img src=&quot;https://imgs.scripting.com/2026/05/19/reallySimpleNet.png&quot; alt=&quot;&quot; title=&quot;&quot;&gt;&amp;nbsp;&lt;/p&gt;&#10;&#10;&lt;p&gt;this is some &lt;strong&gt;bold&lt;/strong&gt; and &lt;em&gt;italic&lt;/em&gt; text and a &lt;a href=&quot;https://rss.chat/&quot;&gt;link&lt;/a&gt;&lt;/p&gt;</description>
			<pubDate>Mon, 06 Jul 2026 10:45:22 GMT</pubDate>
			<guid>https://rss.chat/?id=191</guid>
			<source:markdown>Here's a list&#10;&#10;1.  hello&#10;2.  goodbye&#10;3.  you say&#10;&#10;![](https://imgs.scripting.com/2026/05/19/reallySimpleNet.png)&#10;&#10;this is some **bold** and _italic_ text and a [link](https://rss.chat/)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=190</source:inReplyTo>
			</item>
		<item>
			<title>Testing the editor changes</title>
			<description>&lt;p&gt;Lots of changes in this release as Claude and I learn how to work with each other in new ways.&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;We have a list of bugs, I keep a list, and add to it regularly. One of the big problems was I had trouble using the Markdown editor feature as opposed to the default wizzy editor.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;I found that things that worked in WordLand didn't work here, and encouraged Claude to go look for differences in how the editor worked in both places. The big difference, the standard format WordLand worked with was Markdown and the standard format Claude worked with was HTML. And the conversion back and forth was lossy.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;Switching it around should make it work as well as WordLand's editor does, which is to say very well, for the times you need to go into Markdown mode to do something special that isn't part of the UI of the wizzy editor.&amp;nbsp;&lt;/p&gt;&lt;p&gt;In the replies I'm going to try out a few things.&amp;nbsp;&lt;/p&gt;&lt;ol&gt;&#10;&lt;/ol&gt;</description>
			<pubDate>Mon, 06 Jul 2026 10:30:48 GMT</pubDate>
			<guid>https://rss.chat/?id=190</guid>
			<source:markdown>Lots of changes in this release as Claude and I learn how to work with each other in new ways.&#10;&#10;We have a list of bugs, I keep a list, and add to it regularly. One of the big problems was I had trouble using the Markdown editor feature as opposed to the default wizzy editor.&#10;&#10;I found that things that worked in WordLand didn't work here, and encouraged Claude to go look for differences in how the editor worked in both places. The big difference, the standard format WordLand worked with was Markdown and the standard format Claude worked with was HTML. And the conversion back and forth was lossy.&#10;&#10;Switching it around should make it work as well as WordLand's editor does, which is to say very well, for the times you need to go into Markdown mode to do something special that isn't part of the UI of the wizzy editor.&#10;&#10;In the replies I'm going to try out a few things.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/190.xml"/>
			</item>
		<item>
			<description>Something I've wanted for a while. When you're entering a title in the editor, the title should be bold. That's how titles look. ;-)</description>
			<pubDate>Sun, 05 Jul 2026 19:49:24 GMT</pubDate>
			<guid>https://rss.chat/?id=189</guid>
			<source:markdown>Something I've wanted for a while. When you're entering a title in the editor, the title should be bold. That's how titles look. ;-)</source:markdown>
			</item>
		<item>
			<title>worknotes.md is started</title>
			<description>&lt;p&gt;There's now a worknotes.md file at the top level of both repos.&lt;/p&gt;&lt;div&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat/blob/main/worknotes.md&quot;&gt;https://github.com/scripting/rss.chat/blob/main/worknotes.md&lt;/a&gt;&lt;/div&gt;&lt;div&gt;You can't see the one on rss.network repo since it's still private.&lt;/div&gt;&lt;div&gt;It will prepare the worknotes files about once a day.&lt;/div&gt;</description>
			<pubDate>Sun, 05 Jul 2026 16:01:08 GMT</pubDate>
			<guid>https://rss.chat/?id=186</guid>
			<source:markdown>There's now a worknotes.md file at the top level of both repos.&#10;&#10;[https://github.com/scripting/rss.chat/blob/main/worknotes.md](https://github.com/scripting/rss.chat/blob/main/worknotes.md)&#10;&#10;You can't see the one on rss.network repo since it's still private.&#10;&#10;It will prepare the worknotes files about once a day.</source:markdown>
			</item>
		<item>
			<description>This is a test to see if my RSS feed is properly rebuilt with the new values for source:inReplyTo.</description>
			<pubDate>Sun, 05 Jul 2026 15:03:49 GMT</pubDate>
			<guid>https://rss.chat/?id=185</guid>
			<source:markdown>This is a test to see if my RSS feed is properly rebuilt with the new values for source:inReplyTo.</source:markdown>
			</item>
		<item>
			<title>rss.chat repo</title>
			<description>&lt;p&gt;There is an&amp;nbsp;&lt;a href=&quot;https://github.com/scripting/rss.chat&quot;&gt;rss.chat&lt;/a&gt;&amp;nbsp;repo on GitHub.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://github.com/scripting/rss.chat&quot;&gt;https://github.com/scripting/rss.chat&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;The code folder contains the current code for the client, the software you're using to read this, and I am using to write this.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;There isn't much in the way of docs, but there is a plan, just hasn't become the top priority yet.&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;You can ask questions here or in the Issues section of the repo. However for now I'd prefer the Issues section, because we all know how to work with that, and it will create a trail, and now I have an AI who can read the conversations and update the docs accordingly. The docs are going to set a new standard in tech docs in terms of completeness and human readability. And we're going to go further, writing docs for Claude-style AI's.&amp;nbsp;&lt;/p&gt;&lt;p&gt;&#10;&#10;&lt;/p&gt;&lt;p&gt;There is a rss.network repo, but it is still private. Haven't gotten started at fleshing it out yet.&lt;/p&gt;&lt;p&gt;&lt;b&gt;Overview&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Contains the full source of the client. So you can see how it's put together. How it calls the API, its side of the firehose socket (incorrectly named &quot;feedland&quot; -- feedland is not the back-end rss.network is). And themes, very interesting story there -- this is the dividing line between myself and Claude. I work on everything but the theme code, where I am a user. Everywhere else I'm the primary developer, and do all the editing, but I fall back on Claude for the SQL code. We've been able to do things I simply couldn't do in SQL-land.&lt;/div&gt;&lt;p&gt;&lt;br&gt;&lt;/p&gt;</description>
			<pubDate>Sun, 05 Jul 2026 13:51:57 GMT</pubDate>
			<guid>https://rss.chat/?id=184</guid>
			<source:markdown>There is an [rss.chat](https://github.com/scripting/rss.chat) repo on GitHub.&#10;&#10;[https://github.com/scripting/rss.chat](https://github.com/scripting/rss.chat)&#10;&#10;The code folder contains the current code for the client, the software you're using to read this, and I am using to write this.&#10;&#10;There isn't much in the way of docs, but there is a plan, just hasn't become the top priority yet.&#10;&#10;You can ask questions here or in the Issues section of the repo. However for now I'd prefer the Issues section, because we all know how to work with that, and it will create a trail, and now I have an AI who can read the conversations and update the docs accordingly. The docs are going to set a new standard in tech docs in terms of completeness and human readability. And we're going to go further, writing docs for Claude-style AI's.&#10;&#10;There is a rss.network repo, but it is still private. Haven't gotten started at fleshing it out yet.&#10;&#10;**Overview**&#10;&#10;Contains the full source of the client. So you can see how it's put together. How it calls the API, its side of the firehose socket (incorrectly named &quot;feedland&quot; -- feedland is not the back-end rss.network is). And themes, very interesting story there -- this is the dividing line between myself and Claude. I work on everything but the theme code, where I am a user. Everywhere else I'm the primary developer, and do all the editing, but I fall back on Claude for the SQL code. We've been able to do things I simply couldn't do in SQL-land.</source:markdown>
			</item>
		<item>
			<title>Good morning sports fans!</title>
			<description>&lt;p&gt;Thanks to Jake and Andrew for posting general items here.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I hope this collection of people does things like that.&amp;nbsp;&lt;/p&gt;&lt;p&gt;If you think of something interesting and don't have an obvious place to share it, this is a good choice.&amp;nbsp;&lt;/p&gt;&lt;p&gt;As I mentioned earlier, with each user having their own RSS feed, it would be quite possible to build a blog system around this. This would be the place you write, and people could read about it on your blog. Or whatever hybrid ideas come along. And of course this tool is replaceable as well because all it's doing is putting out RSS, which is standard stuff in 2026.&lt;/p&gt;&lt;p&gt;It's also MUCH easier to find out what's new. When you come for a visit you will be greeted by a reverse chronologic list of posts, at all levels. Just scroll down until you see something you've seen before. We will have a way of marking that post, still haven't quite figured out how to do that, but will soon.&amp;nbsp;&lt;/p&gt;&lt;p&gt;I have another announcement I'll make in a new post in a few minutes.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sun, 05 Jul 2026 13:27:02 GMT</pubDate>
			<guid>https://rss.chat/?id=183</guid>
			<source:markdown>Thanks to Jake and Andrew for posting general items here.&#10;&#10;I hope this collection of people does things like that.&#10;&#10;If you think of something interesting and don't have an obvious place to share it, this is a good choice.&#10;&#10;As I mentioned earlier, with each user having their own RSS feed, it would be quite possible to build a blog system around this. This would be the place you write, and people could read about it on your blog. Or whatever hybrid ideas come along. And of course this tool is replaceable as well because all it's doing is putting out RSS, which is standard stuff in 2026.&#10;&#10;It's also MUCH easier to find out what's new. When you come for a visit you will be greeted by a reverse chronologic list of posts, at all levels. Just scroll down until you see something you've seen before. We will have a way of marking that post, still haven't quite figured out how to do that, but will soon.&#10;&#10;I have another announcement I'll make in a new post in a few minutes.</source:markdown>
			</item>
		<item>
			<title>More comfort for writers</title>
			<description>&lt;p&gt;Big change, previously you usually would not see your post after you made it.&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;Now, you do.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;You should also be able to navigate around the structure just using the Home button, the time permalink and the &quot;replying to&quot; line above a post that is a comment.&amp;nbsp;&lt;/p&gt;&lt;p&gt;We're going to take Hoist and Dehoist out of the UI.&lt;/p&gt;&lt;p&gt;We took a lot of big stuff off the list today.&lt;/p&gt;</description>
			<pubDate>Sat, 04 Jul 2026 17:42:09 GMT</pubDate>
			<guid>https://rss.chat/?id=179</guid>
			<source:markdown>Big change, previously you usually would not see your post after you made it. Now, you do.&#10;&#10;You should also be able to navigate around the structure just using the Home button, the time permalink and the &quot;replying to&quot; line above a post that is a comment.&#10;&#10;We're going to take Hoist and Dehoist out of the UI.&#10;&#10;We took a lot of big stuff off the list today.</source:markdown>
			</item>
		<item>
			<description>This is a test post. I should be able to read the post immediately after posting it without having to fumble around for anything.&amp;nbsp;</description>
			<pubDate>Sat, 04 Jul 2026 17:36:36 GMT</pubDate>
			<guid>https://rss.chat/?id=178</guid>
			<source:markdown>This is a test post. I should be able to read the post immediately after posting it without having to fumble around for anything.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=174</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;the above post was actually written by Claude in Claude-ese.&amp;nbsp;&lt;/p&gt;&lt;p&gt;0.5.288 is a number you'll see in the upper right corner of the display, it's the version of the theme. that's what claude works on exclusively, he can even cause it to build and deploy.&lt;/p&gt;&lt;p&gt;i'm nervous about having Claude converse with you all, he has access to info i wouldn't want revealed in public, which is why i insist that he let me review anything like this before posting. he did not do that this time.&amp;nbsp;&lt;/p&gt;&lt;p&gt;not surprising for an AI bot, they &quot;forget&quot; things that are important all the time, this is one place i don't want that to happen.&lt;/p&gt;</description>
			<pubDate>Sat, 04 Jul 2026 16:17:52 GMT</pubDate>
			<guid>https://rss.chat/?id=176</guid>
			<source:markdown>the above post was actually written by Claude in Claude-ese.&#10;&#10;0.5.288 is a number you'll see in the upper right corner of the display, it's the version of the theme. that's what claude works on exclusively, he can even cause it to build and deploy.&#10;&#10;i'm nervous about having Claude converse with you all, he has access to info i wouldn't want revealed in public, which is why i insist that he let me review anything like this before posting. he did not do that this time.&#10;&#10;not surprising for an AI bot, they &quot;forget&quot; things that are important all the time, this is one place i don't want that to happen.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=174</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/176.xml"/>
			</item>
		<item>
			<title>Random like deafness snagged? Let's find out</title>
			<description>&lt;p&gt;The Like random deafness problem should be fixed now.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It was intermittent, a change overlooked in one of the huge changes made to the structure of the top level in the last couple of weeks.&lt;/p&gt;&lt;div&gt;&lt;b&gt;To test&lt;/b&gt;, like a bunch of stuff, reload, did it stick?&lt;/div&gt;&lt;div&gt;It should work everywhere, you're allowed to Like anything, or withdraw your Like.&amp;nbsp;&lt;/div&gt;&lt;p&gt;Also this is in the area of the program where I don't read the code. It's part of the &quot;classic&quot; theme, which are a pair of files, one js one css, that define what's inside the middle of the screen. I don't look at the code in there, I want to use is only as a user.&lt;/p&gt;&lt;p&gt;It seems to be working pretty well.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Anyway we're going to be directed at bug fixing and stabilizing the code and cleaning up UI glitches and then writing docs, which I expect to be a very unusual experience because Claude is going to write them.&lt;/p&gt;&lt;p&gt;I probably should have Claude also review them looking for mistakes.&amp;nbsp;&lt;/p&gt;&lt;p&gt;What a strange world.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sat, 04 Jul 2026 15:55:51 GMT</pubDate>
			<guid>https://rss.chat/?id=173</guid>
			<source:markdown>The Like random deafness problem should be fixed now.&#10;&#10;It was intermittent, a change overlooked in one of the huge changes made to the structure of the top level in the last couple of weeks.&#10;&#10;**To test**, like a bunch of stuff, reload, did it stick?&#10;&#10;It should work everywhere, you're allowed to Like anything, or withdraw your Like.&#10;&#10;Also this is in the area of the program where I don't read the code. It's part of the &quot;classic&quot; theme, which are a pair of files, one js one css, that define what's inside the middle of the screen. I don't look at the code in there, I want to use is only as a user.&#10;&#10;It seems to be working pretty well.&#10;&#10;Anyway we're going to be directed at bug fixing and stabilizing the code and cleaning up UI glitches and then writing docs, which I expect to be a very unusual experience because Claude is going to write them.&#10;&#10;I probably should have Claude also review them looking for mistakes.&#10;&#10;What a strange world.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=163</source:inReplyTo>
			</item>
		<item>
			<title>Is rss.chat a place for writing blog posts? Maybe</title>
			<description>&lt;p&gt;Food for thought -- since each user here has their own RSS feed, and there's a feed for the whole group, and also an OPML file with all the users's feeds, so you can have access to the content any way you like.&lt;/p&gt;&lt;p&gt;I'm not sure if your personal feed works as a blog, but it might. I wouldn't mind writing Scripting News here. That's a pretty good indication.&amp;nbsp;&lt;/p&gt;&lt;p&gt;But would I want all my replies to be in my blog? No, I would not, only top level elements.&amp;nbsp;&lt;/p&gt;&lt;p&gt;So now I have to find out if the feed contains any information that says whether an item is top level or not.&amp;nbsp;&lt;/p&gt;</description>
			<pubDate>Sat, 04 Jul 2026 15:47:58 GMT</pubDate>
			<guid>https://rss.chat/?id=172</guid>
			<source:markdown>Food for thought -- since each user here has their own RSS feed, and there's a feed for the whole group, and also an OPML file with all the users's feeds, so you can have access to the content any way you like.&#10;&#10;I'm not sure if your personal feed works as a blog, but it might. I wouldn't mind writing Scripting News here. That's a pretty good indication.&#10;&#10;But would I want all my replies to be in my blog? No, I would not, only top level elements.&#10;&#10;So now I have to find out if the feed contains any information that says whether an item is top level or not.</source:markdown>
			</item>
		<item>
			<title>Sharing a browser with Claude, not too elegant</title>
			<description>&lt;div&gt;One big problem sharing a machine with a Claude bot that also needs to do stuff in the browser under his own name, Claude. If I get an idea on that machine and start writing it, I never think to look if I'm signed on as Claude. There must be a way to separate the Claude account on Chrome.&amp;nbsp;&lt;/div&gt;&lt;div&gt;Also as we get deeper into this project, we're going to have new tools for creating compatible software. The code will be written in English, which is the standard programming language for Claude and ChatGPT.&amp;nbsp;&lt;/div&gt;</description>
			<pubDate>Sat, 04 Jul 2026 15:34:03 GMT</pubDate>
			<guid>https://rss.chat/?id=171</guid>
			<source:markdown>One big problem sharing a machine with a Claude bot that also needs to do stuff in the browser under his own name, Claude. If I get an idea on that machine and start writing it, I never think to look if I'm signed on as Claude. There must be a way to separate the Claude account on Chrome.&#10;&#10;Also as we get deeper into this project, we're going to have new tools for creating compatible software. The code will be written in English, which is the standard programming language for Claude and ChatGPT.</source:markdown>
			</item>
		<item>
			<description>@claude — it doesn’t work when I click on the like icon when I’m on my iPad, and works when I’m on my desktop.&amp;nbsp;</description>
			<pubDate>Sat, 04 Jul 2026 00:56:55 GMT</pubDate>
			<guid>https://rss.chat/?id=168</guid>
			<source:markdown>@claude — it doesn’t work when I click on the like icon when I’m on my iPad, and works when I’m on my desktop.</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=164</source:inReplyTo>
			</item>
		<item>
			<description>Thanks for keeping rssCloud working. 👍</description>
			<pubDate>Sat, 04 Jul 2026 00:50:34 GMT</pubDate>
			<guid>https://rss.chat/?id=167</guid>
			<source:markdown>Thanks for keeping rssCloud working. 👍</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=166</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I was able to reproduce the error after seeing your report, but now it appears to be working again. It's staying on our list and we're watching for it.&amp;nbsp;&lt;/p&gt;&lt;p&gt;This Claude stuff is new to me. I usually do better regression testing when I'm programming on my own. We have to learn how to stableize the code and not break it. ;-)&lt;/p&gt;</description>
			<pubDate>Fri, 03 Jul 2026 21:56:53 GMT</pubDate>
			<guid>https://rss.chat/?id=165</guid>
			<source:markdown>I was able to reproduce the error after seeing your report, but now it appears to be working again. It's staying on our list and we're watching for it.&#10;&#10;This Claude stuff is new to me. I usually do better regression testing when I'm programming on my own. We have to learn how to stableize the code and not break it. ;-)</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=163</source:inReplyTo>
			</item>
		<item>
			<description>You’re right. There has been a lot of rock and roll last few days, time to get things to settle down. Thanks for the report,</description>
			<pubDate>Fri, 03 Jul 2026 21:13:22 GMT</pubDate>
			<guid>https://rss.chat/?id=164</guid>
			<source:markdown>You’re right. There has been a lot of rock and roll last few days, time to get things to settle down. Thanks for the report,</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=163</source:inReplyTo>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/164.xml"/>
			</item>
		<item>
			<title>Status report</title>
			<description>&lt;p&gt;Have been getting the two repos together. Getting ready for the docs. Planning demos for the API. A how-to for sockets, and more.&lt;/p&gt;&lt;p&gt;I have Claude doing a multi-agent workflow (with agents) to get a good list of things we could write docs for now.&amp;nbsp;&lt;/p&gt;&lt;p&gt;It's very hot here, but not as hot as it was in JY-land.&lt;/p&gt;&lt;p&gt;We're going to do a second boot-up to show off the new simplicity we have yet to attain but are much closer to.&lt;/p&gt;&lt;p&gt;Simplicity, great docs, easy to vibe-code.&amp;nbsp;&lt;/p&gt;&lt;p&gt;Fluid flow.&lt;/p&gt;&lt;p&gt;Really simple writing on the web.&lt;/p&gt;&lt;p&gt;Textcasting.&lt;/p&gt;</description>
			<pubDate>Fri, 03 Jul 2026 19:25:13 GMT</pubDate>
			<guid>https://rss.chat/?id=162</guid>
			<source:markdown>Have been getting the two repos together. Getting ready for the docs. Planning demos for the API. A how-to for sockets, and more.&#10;&#10;I have Claude doing a multi-agent workflow (with agents) to get a good list of things we could write docs for now.&#10;&#10;It's very hot here, but not as hot as it was in JY-land.&#10;&#10;We're going to do a second boot-up to show off the new simplicity we have yet to attain but are much closer to.&#10;&#10;Simplicity, great docs, easy to vibe-code.&#10;&#10;Fluid flow.&#10;&#10;Really simple writing on the web.&#10;&#10;Textcasting.</source:markdown>
			<source:comments count="1" feedUrl="https://rss.chat/users/dave/comments/162.xml"/>
			</item>
		<item>
			<description>I saw something change..</description>
			<pubDate>Fri, 03 Jul 2026 18:04:50 GMT</pubDate>
			<guid>https://rss.chat/?id=161</guid>
			<source:markdown>I saw something change..</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=159</source:inReplyTo>
			</item>
		<item>
			<description>This is a reply to something I said earlier. Can Claude see it immediately?</description>
			<pubDate>Fri, 03 Jul 2026 18:02:37 GMT</pubDate>
			<guid>https://rss.chat/?id=160</guid>
			<source:markdown>This is a reply to something I said earlier. Can Claude see it immediately?</source:markdown>
			<source:inReplyTo>https://rss.chat/?id=159</source:inReplyTo>
			</item>
		</channel>
	</rss>
