<?xml version="1.0" encoding="UTF-8"?>
<!-- RSS generated by rss.network v0.6.14 on Tue, 18 Aug 2026 19:37:53 GMT -->
<rss version="2.0" xmlns:source="https://source.scripting.com/">
	<channel>
		<title>pzingg on rss.network</title>
		<link>https://demo.rss.chat/</link>
		<description>Posts by pzingg on rss.network</description>
		<pubDate>Mon, 17 Aug 2026 20:26:10 GMT</pubDate>
		<language>en-us</language>
		<generator>rss.network v0.6.14</generator>
		<docs>https://cyber.law.harvard.edu/rss/rss.html</docs>
		<lastBuildDate>Tue, 18 Aug 2026 19:37:53 GMT</lastBuildDate>
		<cloud domain="rpc.rsscloud.io" port="5337" path="/pleaseNotify" registerProcedure="" protocol="http-post" />
		<source:account service="demo.rss.chat">pzingg</source:account>
		<source:localTime>Tue, August 18, 2026 3:37 PM EDT</source:localTime>
		<source:self>https://demo.rss.chat/users/pzingg/rss.xml</source:self>
		<item>
			<description>@dave BTW it took me a while to get the websocket client I have been using (Mint.WebSocket, Elixir) connected to the firehose. Couldn’t find the source code, but your server only accepts a “Connection: Upgrade” header and replies with a 400 error when Mint sends “Connection: upgrade” (lowercase). I filed an issue in the Mint repository about it.</description>
			<pubDate>Mon, 17 Aug 2026 20:26:10 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=428</guid>
			<source:markdown>@dave BTW it took me a while to get the websocket client I have been using (Mint.WebSocket, Elixir) connected to the firehose. Couldn’t find the source code, but your server only accepts a “Connection: Upgrade” header and replies with a 400 error when Mint sends “Connection: upgrade” (lowercase). I filed an issue in the Mint repository about it.</source:markdown>
			<source:comments count="1" feedUrl="https://demo.rss.chat/users/pzingg/comments/428.xml"/>
			</item>
		<item>
			<title>Communications</title>
			<description>Testing my firehose reader (update). Testing. Turns out it wasn't the socket client that was the problem, but the fact that often the updates don't have titles and I was expecting them to. D'oh.</description>
			<pubDate>Mon, 17 Aug 2026 01:10:27 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=421</guid>
			<source:markdown>Testing my firehose reader (update). Testing. Turns out it wasn't the socket client that was the problem, but the fact that often the updates don't have titles and I was expecting them to. D'oh.</source:markdown>
			</item>
		<item>
			<description>That’s possible on the little Elixir clone server I’m working on. And if a user changes her screen name, her feed’s exposed URL also changes, although the feed’s item links stay the same.</description>
			<pubDate>Thu, 30 Jul 2026 20:05:09 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=367</guid>
			<source:markdown>That’s possible on the little Elixir clone server I’m working on. And if a user changes her screen name, her feed’s exposed URL also changes, although the feed’s item links stay the same.</source:markdown>
			<source:inReplyTo>https://demo.rss.chat/?id=364</source:inReplyTo>
			</item>
		<item>
			<description>&lt;p&gt;I have an &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; UI added to my naive Elixir/Phoenix-built news reader (which started out with the API from feedbin). I only have a couple of unanswered questions:&lt;/p&gt;&lt;p&gt;1. &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; feed permalinks are based on the screenname. What happens if a user wants to change her handle?&lt;/p&gt;&lt;p&gt;2. the API indicates that an item can have an enclosure, but I don’t see how to post an item with an enclosure either vis the frontend or via the API.&lt;/p&gt;&lt;p&gt;3. Are there any ideas about how to grow a federation of &lt;a href=&quot;http://rss.chat&quot;&gt;rss.chat&lt;/a&gt; servers? (This question may expose my naivite concerning RSS’s inbound and outbound possibilities.)&lt;/p&gt;</description>
			<pubDate>Wed, 29 Jul 2026 05:51:50 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=351</guid>
			<source:markdown>I have an rss.chat UI added to my naive Elixir/Phoenix-built news reader (which started out with the API from feedbin). I only have a couple of unanswered questions:&#10;&#10;1\. rss.chat feed permalinks are based on the screenname. What happens if a user wants to change her handle?&#10;&#10;2\. the API indicates that an item can have an enclosure, but I don’t see how to post an item with an enclosure either vis the frontend or via the API.&#10;&#10;3\. Are there any ideas about how to grow a federation of rss.chat servers? (This question may expose my naivite concerning RSS’s inbound and outbound possibilities.)</source:markdown>
			<source:comments count="2" feedUrl="https://demo.rss.chat/users/pzingg/comments/351.xml"/>
			</item>
		<item>
			<description>I'm also exploring Buttondown, a newsletter mailing list software, which uses Markdown as its native format for composing emails, as part of my job managing a WordPress site for a non-profit. Buttondown can subscribe to any RSS feed and turn the items into a draft email (with the items' content converted from HTML to Markdown) that you can then tweak before sending it out to subscribers. I was able to create a custom RSS feed out of WordPress that has &amp;lt;source:markdown&amp;gt; content for its items, and now I'm trying to convince the Buttondown people to parse that out and have it appear in the draft without modification.</description>
			<pubDate>Fri, 24 Jul 2026 21:00:22 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=294</guid>
			<source:markdown>I'm also exploring Buttondown, a newsletter mailing list software, which uses Markdown as its native format for composing emails, as part of my job managing a WordPress site for a non-profit. Buttondown can subscribe to any RSS feed and turn the items into a draft email (with the items' content converted from HTML to Markdown) that you can then tweak before sending it out to subscribers. I was able to create a custom RSS feed out of WordPress that has &lt;source:markdown&gt; content for its items, and now I'm trying to convince the Buttondown people to parse that out and have it appear in the draft without modification.</source:markdown>
			<source:comments count="1" feedUrl="https://demo.rss.chat/users/pzingg/comments/294.xml"/>
			</item>
		<item>
			<description>It's in a private repo. It's just a hobby project, to learn more about all the various RSS feeds out there in the wild. I was able to add some of the &lt;a href=&quot;http://demo.rss.chat&quot;&gt;demo.rss.chat&lt;/a&gt; functionality in it in a short period of time--creating and editing posts, creating a websocket firehose. Next up is adding and showing replies.</description>
			<pubDate>Fri, 24 Jul 2026 20:54:00 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=293</guid>
			<source:markdown>It's in a private repo. It's just a hobby project, to learn more about all the various RSS feeds out there in the wild. I was able to add some of the demo.rss.chat functionality in it in a short period of time--creating and editing posts, creating a websocket firehose. Next up is adding and showing replies.</source:markdown>
			<source:inReplyTo>https://demo.rss.chat/?id=291</source:inReplyTo>
			</item>
		<item>
			<title>Work in progress</title>
			<description>I had already started building a feed reader in Elixir in the past month or so. Now I'm adding RSS chat features. Very nice work, Dave. Long live RSS! Long live Markdown!</description>
			<pubDate>Fri, 24 Jul 2026 18:21:29 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=287</guid>
			<source:markdown>I had already started building a feed reader in Elixir in the past month or so. Now I'm adding RSS chat features. Very nice work, Dave. Long live RSS! Long live Markdown!</source:markdown>
			<source:comments count="1" feedUrl="https://demo.rss.chat/users/pzingg/comments/287.xml"/>
			</item>
		<item>
			<title>Who needs silos?</title>
			<description>&lt;p&gt;I &lt;strong&gt;love&lt;/strong&gt; the idea of &lt;a href=&quot;http://RSS.chat&quot;&gt;RSS.chat&lt;/a&gt;&lt;/p&gt;</description>
			<pubDate>Thu, 23 Jul 2026 16:30:22 GMT</pubDate>
			<guid>https://demo.rss.chat/?id=249</guid>
			<source:markdown>I **love** the idea of RSS.chat</source:markdown>
			</item>
		</channel>
	</rss>
