<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>moshyfawn</title>
    <link>https://moshyfawn.dev</link>
    <atom:link href="https://moshyfawn.dev/rss.xml" rel="self" type="application/rss+xml" />
    <description>Projects, extensions, and atproto work - with the occasional post.</description>
    <language>en</language>
    <item>
      <title>Trying ATapult</title>
      <link>https://moshyfawn.dev/blog/trying-atapult</link>
      <guid isPermaLink="true">https://moshyfawn.dev/blog/trying-atapult</guid>
      <pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate>
      <description>Syndicating a static site to atproto so posts are portable.</description>
      <content:encoded><![CDATA[<p>My posts live as plain Markdown in a git repo - simple, portable, and mine. But
I also wanted them to exist <em>on the network</em>: discoverable from atproto apps,
not only from this domain.</p>
<p>That’s the part I chose to try <a href="https://github.com/Wilto/ATapult">ATapult</a> to handle. The Markdown stays the source of truth, and
ATapult mirrors each post into my atproto repo as a <a href="https://standard.site">standard.site</a> record - a small, structured pointer back to the real page over here.</p>
<p>So it’s the best of both: I write once in Markdown, and the post also shows up
on the Atmosphere without me having to propagate it to the network. The site is still just static files; the network presence comes along.</p>]]></content:encoded>
    </item>
    <item>
      <title>Hello, world</title>
      <link>https://moshyfawn.dev/blog/hello-world</link>
      <guid isPermaLink="true">https://moshyfawn.dev/blog/hello-world</guid>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <description>A first post, and what this place is for.</description>
      <content:encoded><![CDATA[<p>Every site needs its obligatory first post, so here’s mine.</p>
<p>This is a small home on the web for the things I build - extensions,
tools, games, and a fair amount of tinkering on atproto. Mostly it’s
somewhere to point at, but every so often I’ll write something down here too.</p>
<p>If you’re reading this from somewhere other than moshyfawn.dev, that’s the
atproto side doing its thing. More on that soon.</p>]]></content:encoded>
    </item>
  </channel>
</rss>