<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Crofty</title>
		<link>https://crofty.pages.dev/</link>
		<description>Recent content on Crofty</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 14 Jun 2026 01:00:00 +0900</lastBuildDate>
		
			<atom:link href="https://crofty.pages.dev/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Sharing without handing over an account</title>
				<link>https://crofty.pages.dev/posts/share-without-an-account/</link>
				<pubDate>Sun, 14 Jun 2026 01:00:00 +0900</pubDate>
				<guid>https://crofty.pages.dev/posts/share-without-an-account/</guid>
				<description>&lt;p&gt;Most tools that &amp;ldquo;post to your socials&amp;rdquo; want your passwords first. crofty&amp;rsquo;s&#xA;&lt;code&gt;share&lt;/code&gt; command takes the opposite bet: it never logs in anywhere.&lt;/p&gt;&#xA;&lt;p&gt;Run it on a post and it composes the fragment — the title, a trimmed summary,&#xA;and a link back to the page you own — then prints it. You paste it, or click a&#xA;pre-filled compose link that opens the network&amp;rsquo;s own box. For the networks with&#xA;a real API and a friendly stance on links, &lt;code&gt;publish&lt;/code&gt; can still do the posting&#xA;for you; but that&amp;rsquo;s the opt-in path, not the default.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Hello from crofty</title>
				<link>https://crofty.pages.dev/posts/hello-crofty/</link>
				<pubDate>Sun, 14 Jun 2026 00:00:00 +0900</pubDate>
				<guid>https://crofty.pages.dev/posts/hello-crofty/</guid>
				<description>&lt;p&gt;This is a test post. The body lives only on the owned site; only the title,&#xA;description and a link back here are ever syndicated.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
