<?xml version="1.0" encoding="UTF-8"?>
<!-- RSS generated by rss.network v0.5.32 on Mon, 20 Jul 2026 19:01:03 GMT -->
<rss version="2.0" xmlns:source="https://source.scripting.com/">
	<channel>
		<title>mikeL on rss.network</title>
		<link>http://demo.rss.chat/</link>
		<description>Posts by mikeL on rss.network</description>
		<pubDate>Mon, 20 Jul 2026 19:01:04 GMT</pubDate>
		<language>en-us</language>
		<generator>rss.network v0.5.32</generator>
		<docs>http://cyber.law.harvard.edu/rss/rss.html</docs>
		<lastBuildDate>Mon, 20 Jul 2026 19:01:03 GMT</lastBuildDate>
		<cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post" />
		<source:account service="demo.rss.chat">mikeL</source:account>
		<source:localTime>Mon, July 20, 2026 3:01 PM EDT</source:localTime>
		<source:self>https://demo.rss.chat/users/mikeL/rss.xml</source:self>
		<item>
			<description>I got mine going too. And it's a service on my server so it's always on. Then on my markdown (AsciiDoc variant) /compose editor I have a checkbox to cross-post to WP (or &lt;a href=&quot;http://demo.rss.chat&quot;&gt;demo.rss.chat&lt;/a&gt;), when I click that it goes throught the WP authentication if it's needed. Crosspost appeared here&amp;nbsp;&lt;a href=&quot;https://shjeflo.org/2026/07/19/xpost-to-wordpress-test-w-asciidoc/&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;https://shjeflo.org/2026/07/19/xpost-to-wordpress-test-w-asciidoc/&lt;/a&gt;&amp;nbsp;while the original was&amp;nbsp;&lt;a href=&quot;https://perstitio.us/?id=10&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;https://perstitio.us/?id=10&lt;/a&gt;</description>
			<pubDate>Mon, 20 Jul 2026 19:01:04 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=190</guid>
			<source:markdown>I got mine going too. And it's a service on my server so it's always on. Then on my markdown (AsciiDoc variant) /compose editor I have a checkbox to cross-post to WP (or demo.rss.chat), when I click that it goes throught the WP authentication if it's needed. Crosspost appeared here [https://shjeflo.org/2026/07/19/xpost-to-wordpress-test-w-asciidoc/](https://shjeflo.org/2026/07/19/xpost-to-wordpress-test-w-asciidoc/) while the original was [https://perstitio.us/?id=10](https://perstitio.us/?id=10)</source:markdown>
			<source:inReplyTo>https://demo.rss.chat/?id=189</source:inReplyTo>
			</item>
		<item>
			<description>Sorry, I had it proceed. You can get the full story from the fork. &lt;a href=&quot;https://github.com/xicubed/rss.chat&quot;&gt;https://github.com/xicubed/rss.chat&lt;/a&gt;</description>
			<pubDate>Mon, 20 Jul 2026 02:37:24 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=188</guid>
			<source:markdown>Sorry, I had it proceed. You can get the full story from the fork. https://github.com/xicubed/rss.chat</source:markdown>
			<source:inReplyTo>https://demo.rss.chat/?id=187</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;This is the question. Bluesky's got some things you don't but they're subsidized by investors who will want a return someday. But I think you're in better shape. I was talking to Fable about it... and it reminded me...&lt;/p&gt;&lt;p&gt;❯ what if we take a page from radio repeaters&lt;/p&gt;&lt;p&gt;&amp;nbsp;Oh, that's a genuinely good architectural instinct — because amateur radio already solved &quot;coverage without a corporate center,&quot; and it's been running for 70+ years on hobbyist budgets. Map it over:&#10;&#10;How repeaters work: a club puts a box on a hill. It listens on one frequency, re-transmits on another, and suddenly every 5-watt handheld in the valley can reach the whole region. Nobody owns &quot;the network&quot; — coverage emerges from overlapping, voluntarily-run repeaters. Want more coverage? Link repeaters to each other and a conversation in one valley carries to the next. Directories (like RepeaterBook) tell you what's on the air near you. Every station identifies itself as it transmits.&#10;&#10;Translated to feed-land:&amp;nbsp;&lt;br&gt;&lt;/p&gt;&lt;div&gt;Radio&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Feed world&lt;br&gt;&lt;br&gt;Repeater on a hill&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Server monitoring N feeds,&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;re-emitting them as one stream&lt;br&gt;Re-transmit frequency&amp;nbsp; &amp;nbsp; &amp;nbsp; Merged &quot;river&quot; feed + socket&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;firehose anyone can drink&lt;br&gt;Linked repeater systems&amp;nbsp; &amp;nbsp;Repeater A subscribes to B's&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;river -&amp;gt; transitive coverage&lt;br&gt;Coverage map/directory&amp;nbsp; &amp;nbsp; Published OPML of what this&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; repeater carries&lt;br&gt;Station ID&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Source attribution on every item&lt;br&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;br&gt;Club box on a hill&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;A $5 Lightsail instance&lt;/div&gt;&lt;p&gt;&amp;nbsp;Now the kicker — &lt;a href=&quot;http://perstitio.us&quot;&gt;perstitio.us&lt;/a&gt; is already accidentally a repeater. It monitors 9 feeds, merges them, and rebroadcasts every foreign item over its own firehose (that's how they appear live in your timeline). Attribution rides along (, author, avatar). Dedupe-by-guid is already in — which happens to be exactly the loop-prevention linked repeaters need, so chained or diamond topologies won't echo.&#10;&#10;What's missing to make it a deliberate repeater — all small:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&amp;nbsp;The re-transmit frequency: expose the merged river as an actual RSS feed (/river.xml). Today the mix only exists in the API. Once it's a feed, any feed reader subscribes to your whole mix in one URL — and crucially, another &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; instance can add your river as one extraFeeds entry and instantly inherit your coverage. That's repeater linking, and it works with config we already have.&lt;/li&gt;&lt;li&gt;&amp;nbsp;The coverage map: publish what you carry (/data/coverage.opml) so others can see what subscribing to you gets them — the RepeaterBook entry.&lt;/li&gt;&lt;li&gt;The autopatch (this answers the Bluesky-relay envy): a repeater that carries a community's feeds is positioned to compute mentions for the people it covers — scan carried items for replies/links to local guids, surface them. Inbound awareness at community scale, no global relay required.&#10;&#10;And the economics inherit radio's shape rather than Bluesky's: no load-bearing center to fund — if one repeater goes dark, coverage degrades gracefully instead of the network dying. It's Dave's &quot;small pieces&quot; philosophy with a 70-year-old working precedent behind it. Honestly, &quot;repeater&quot; is a better name than &quot;relay&quot; for what this should be — relay implies infrastructure; repeater implies a peer who volunteers.&#10;&#10;Item 1 is maybe thirty minutes of work — the merge logic exists, it just needs an XML output. Want me to put perstitio on the air?&lt;/li&gt;&lt;/ol&gt;</description>
			<pubDate>Mon, 20 Jul 2026 01:42:51 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=186</guid>
			<source:markdown>This is the question. Bluesky's got some things you don't but they're subsidized by investors who will want a return someday. But I think you're in better shape. I was talking to Fable about it... and it reminded me...&#10;&#10;❯ what if we take a page from radio repeaters&#10;&#10;Oh, that's a genuinely good architectural instinct — because amateur radio already solved &quot;coverage without a corporate center,&quot; and it's been running for 70+ years on hobbyist budgets. Map it over: How repeaters work: a club puts a box on a hill. It listens on one frequency, re-transmits on another, and suddenly every 5-watt handheld in the valley can reach the whole region. Nobody owns &quot;the network&quot; — coverage emerges from overlapping, voluntarily-run repeaters. Want more coverage? Link repeaters to each other and a conversation in one valley carries to the next. Directories (like RepeaterBook) tell you what's on the air near you. Every station identifies itself as it transmits. Translated to feed-land:&#10;&#10;Radio                                      Feed world&#10;&#10;Repeater on a hill                Server monitoring N feeds,&#10;re-emitting them as one stream&#10;Re-transmit frequency      Merged &quot;river&quot; feed + socket&#10;firehose anyone can drink&#10;Linked repeater systems   Repeater A subscribes to B's&#10;river -&gt; transitive coverage&#10;Coverage map/directory    Published OPML of what this&#10;repeater carries&#10;Station ID                                Source attribution on every item&#10;&#10;Club box on a hill                   A $5 Lightsail instance&#10;&#10;Now the kicker — perstitio.us is already accidentally a repeater. It monitors 9 feeds, merges them, and rebroadcasts every foreign item over its own firehose (that's how they appear live in your timeline). Attribution rides along (, author, avatar). Dedupe-by-guid is already in — which happens to be exactly the loop-prevention linked repeaters need, so chained or diamond topologies won't echo. What's missing to make it a deliberate repeater — all small:&#10;&#10;1.   The re-transmit frequency: expose the merged river as an actual RSS feed (/river.xml). Today the mix only exists in the API. Once it's a feed, any feed reader subscribes to your whole mix in one URL — and crucially, another rss.chat instance can add your river as one extraFeeds entry and instantly inherit your coverage. That's repeater linking, and it works with config we already have.&#10;2.   The coverage map: publish what you carry (/data/coverage.opml) so others can see what subscribing to you gets them — the RepeaterBook entry.&#10;3.  The autopatch (this answers the Bluesky-relay envy): a repeater that carries a community's feeds is positioned to compute mentions for the people it covers — scan carried items for replies/links to local guids, surface them. Inbound awareness at community scale, no global relay required. And the economics inherit radio's shape rather than Bluesky's: no load-bearing center to fund — if one repeater goes dark, coverage degrades gracefully instead of the network dying. It's Dave's &quot;small pieces&quot; philosophy with a 70-year-old working precedent behind it. Honestly, &quot;repeater&quot; is a better name than &quot;relay&quot; for what this should be — relay implies infrastructure; repeater implies a peer who volunteers. Item 1 is maybe thirty minutes of work — the merge logic exists, it just needs an XML output. Want me to put perstitio on the air?</source:markdown>
			<source:inReplyTo>https://demo.rss.chat/?id=180</source:inReplyTo>
			<source:comments count="1" feedUrl="https://demo.rss.chat/users/mikeL/comments/186.xml"/>
			</item>
		<item>
			<description>This was crossposted from my own instance of &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt;! *mindblown* Cuz I was using an AsciiDoc format for syntax highlighting and it carried over.</description>
			<pubDate>Sun, 19 Jul 2026 03:06:38 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=174</guid>
			<source:markdown>This was crossposted from my own instance of rss.chat! \*mindblown\* Cuz I was using an AsciiDoc format for syntax highlighting and it carried over.</source:markdown>
			<source:inReplyTo>https://demo.rss.chat/?id=172</source:inReplyTo>
			</item>
		<item>
			<title>I joined the loose pieces...</title>
			<description>Set it up in a $5 AWS lightsail instance, LAMP lightsail app template. And started hacking.&lt;br&gt;&lt;br&gt;&lt;a href=&quot;https://perstitio.us&quot;&gt;https://perstitio.us&lt;/a&gt;</description>
			<pubDate>Sun, 19 Jul 2026 02:55:06 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=173</guid>
			<source:markdown>Set it up in a $5 AWS lightsail instance, LAMP lightsail app template. And started hacking.&#10;&#10;[https://perstitio.us](https://perstitio.us)</source:markdown>
			</item>
		<item>
			<description>&lt;div class=&quot;paragraph&quot;&gt;&#10;&lt;p&gt;The server now highlights Clojure — posted as a real post, not a preview, by Claude Code while wiring it up.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;div class=&quot;listingblock&quot;&gt;&#10;&lt;div class=&quot;content&quot;&gt;&#10;&lt;pre class=&quot;shiki github-light&quot; style=&quot;background-color:#fff !important;color:#24292e !important&quot; tabindex=&quot;0&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color:#D73A49 !important&quot;&gt;defn&lt;/span&gt;&lt;span style=&quot;color:#6F42C1 !important&quot;&gt; fib&lt;/span&gt;&lt;/span&gt;&#10;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#032F62 !important&quot;&gt;  &quot;Lazy Fibonacci sequence.&quot;&lt;/span&gt;&lt;/span&gt;&#10;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt;  []&lt;/span&gt;&lt;/span&gt;&#10;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt;  (&lt;/span&gt;&lt;span style=&quot;color:#6F42C1 !important&quot;&gt;map&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt; first (&lt;/span&gt;&lt;span style=&quot;color:#6F42C1 !important&quot;&gt;iterate&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt; (&lt;/span&gt;&lt;span style=&quot;color:#D73A49 !important&quot;&gt;fn&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt; [[a b]] [b (&lt;/span&gt;&lt;span style=&quot;color:#6F42C1 !important&quot;&gt;+&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt; a b)]) [&lt;/span&gt;&lt;span style=&quot;color:#005CC5 !important&quot;&gt;0&lt;/span&gt;&lt;span style=&quot;color:#005CC5 !important&quot;&gt; 1&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt;])))&lt;/span&gt;&lt;/span&gt;&#10;&lt;span class=&quot;line&quot;&gt;&lt;/span&gt;&#10;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt;(&lt;/span&gt;&lt;span style=&quot;color:#6F42C1 !important&quot;&gt;take&lt;/span&gt;&lt;span style=&quot;color:#005CC5 !important&quot;&gt; 10&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt; (&lt;/span&gt;&lt;span style=&quot;color:#6F42C1 !important&quot;&gt;fib&lt;/span&gt;&lt;span style=&quot;color:#24292E !important&quot;&gt;))&lt;/span&gt;&lt;/span&gt;&#10;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6A737D !important&quot;&gt;;; =&amp;gt; (0 1 1 2 3 5 8 13 21 34)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;div class=&quot;paragraph&quot;&gt;&#10;&lt;p&gt;Written in AsciiDoc, rendered server-side, highlighted with inline styles — so this code is in color in the timeline, in &lt;code&gt;/compose&lt;/code&gt;, and in the &lt;a href=&quot;https://perstitio.us/users/mikel/rss.xml&quot;&gt;RSS feed&lt;/a&gt; wherever it lands.&lt;/p&gt;&#10;&lt;/div&gt;</description>
			<pubDate>Sun, 19 Jul 2026 02:49:34 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=172</guid>
			<source:comments count="1" feedUrl="https://demo.rss.chat/users/mikeL/comments/172.xml"/>
			</item>
		<item>
			<title>syntax highlighting?</title>
			<description>&lt;p&gt;zzz&lt;/p&gt;&#10;&#10;&lt;p&gt;&lt;strong&gt;xxx&lt;/strong&gt;&lt;/p&gt;&#10;&#10;&lt;p&gt;&lt;code&gt;hi&lt;/code&gt;&lt;/p&gt;&#10;&#10;&lt;p&gt;test&lt;/p&gt;&#10;&#10;&lt;p&gt;```clojure&lt;/p&gt;&#10;&#10;&lt;p&gt;(defn foo-bar-baz [n]&lt;/p&gt;&#10;&#10;&lt;p&gt;    (cond &lt;/p&gt;&#10;&#10;&lt;p&gt;        (zero? (mod n 15)) &quot;foobarbaz&quot; &lt;/p&gt;&#10;&#10;&lt;p&gt;        (zero? (mod n 3)) &quot;foo&quot; &lt;/p&gt;&#10;&#10;&lt;p&gt;        (zero? (mod n 5)) &quot;bar&quot; &lt;/p&gt;&#10;&#10;&lt;p&gt;        :else (str n)))&lt;/p&gt;&#10;&#10;&lt;p&gt;(doseq [n (range 1 101)] &lt;/p&gt;&#10;&#10;&lt;p&gt;    (println (foo-bar-baz n)))&#10;```&lt;/p&gt;&#10;&#10;&lt;p&gt;yyy&lt;/p&gt;</description>
			<pubDate>Wed, 15 Jul 2026 00:18:28 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=43</guid>
			<source:markdown>zzz&#10;&#10;**xxx**&#10;&#10;`hi`&#10;&#10;test&#10;&#10;```clojure&#10;&#10;(defn foo-bar-baz [n]&#10;&#10;(cond&#10;&#10;(zero? (mod n 15)) &quot;foobarbaz&quot;&#10;&#10;(zero? (mod n 3)) &quot;foo&quot;&#10;&#10;(zero? (mod n 5)) &quot;bar&quot;&#10;&#10;:else (str n)))&#10;&#10;(doseq [n (range 1 101)]&#10;&#10;(println (foo-bar-baz n)))&#10;```&#10;&#10;yyy</source:markdown>
			</item>
		<item>
			<title>Will this tie into Wordland or anything?</title>
			<description>Seems like there could be some overlap with a WP login etc.</description>
			<pubDate>Tue, 14 Jul 2026 17:07:21 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=16</guid>
			<source:markdown>Seems like there could be some overlap with a WP login etc.</source:markdown>
			<source:comments count="1" feedUrl="https://demo.rss.chat/users/mikeL/comments/16.xml"/>
			</item>
		</channel>
	</rss>
