<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2026-08-06T16:44:15+02:00</updated><id>/feed.xml</id><entry><title type="html">Nsite blogger is coming</title><link href="/2026/08/06/2b8cd8ef.html" rel="alternate" type="text/html" title="Nsite blogger is coming" /><published>2026-08-06T15:18:21+02:00</published><updated>2026-08-06T15:18:21+02:00</updated><id>/2026/08/06/2b8cd8ef</id><content type="html" xml:base="/2026/08/06/2b8cd8ef.html"><![CDATA[<p><strong>Publishing on Nostr</strong> is still hard. Readers have to run apps that fetch events from relays concurrently and render them locally. This is rather complicated, it can be fragile and slow, ruining reader experience.</p>

<p>Content born on Nostr lives on Nostr with all its censorship resistant properties.</p>

<p>But for more importantly:</p>
<ul>
  <li><strong>Choose your style</strong> for the blog - this is what jekyll themes were built for.</li>
  <li><strong>Choose your editor</strong> - Nostr thrives in this space. Mobile or desktop, use the editor you already love.</li>
  <li><strong>Never lose your followers</strong> - on Nostr you own your identity</li>
  <li><strong>SEO</strong> is good!</li>
</ul>

<p>This is about connecting the dots, wiring already existing tools together to create old-style blogs from your Nostr articles - in other words: we make your Nostr blog widely visible for the Free People of the Internet.</p>

<p>Stay tuned!</p>

<p>(v3)</p>

<p>#publishing #longform #blog #nsite</p>]]></content><author><name>Lez</name></author><category term="publishing" /><category term="longform" /><category term="blog" /><category term="nsite" /><summary type="html"><![CDATA[v3]]></summary></entry><entry><title type="html">Nsite blogger is coming</title><link href="/2026/08/06/003402ad.html" rel="alternate" type="text/html" title="Nsite blogger is coming" /><published>2026-08-06T13:44:48+02:00</published><updated>2026-08-06T13:44:48+02:00</updated><id>/2026/08/06/003402ad</id><content type="html" xml:base="/2026/08/06/003402ad.html"><![CDATA[<p><strong>Publishing on Nostr</strong> is still not perfect. Readers have to run apps that fetch events from relays concurrently and render them locally. This is rather complicated, it can be fragile and slow, ruining reader experience.</p>

<p><strong>Static HTML</strong> files are best to deliver content, scripts are only needed when there is interaction from the user.</p>

<p>We are building a bridge from <strong>long-form Nostr articles</strong> to static HTML files. This tool uses <strong>jekyll</strong> blog engine to generate the static files and publish it via an <strong>nsite</strong>.</p>

<p>With a simple 
are always I am working on a simple tool that makes <strong>Nostr</strong> long-form content widely visible to the public.
The idea is to use the markdown content from long form posts and feed it into jekyll, a lovely static html blogging engine.
The generated static site is published on an <strong>nsite</strong>, which closes the loop. Content born on nostr, lives on nostr with all its censorship resistant properties.</p>

<p>But for more importantly:</p>
<ul>
  <li><strong>Choose your style</strong> for the blog - this is what jekyll themes were built for.</li>
  <li><strong>Choose your editor</strong> - Nostr thrives in this space. Mobile or desktop, use the editor you already love.</li>
  <li><strong>Never lose your followers</strong> - on Nostr you own your identity</li>
</ul>

<p>This is about connecting the dots, wiring already existing tools together to create old-style blogs from your Nostr articles - in other words: we make your Nostr blog widely visible for the Free People of the Internet.</p>

<p>Stay tuned!</p>

<p>#publishing #longform #blog #nsite</p>]]></content><author><name>Lez</name></author><category term="publishing" /><category term="longform" /><category term="blog" /><category term="nsite" /><summary type="html"><![CDATA[Publishing on Nostr is still not perfect. Readers have to run apps that fetch events from relays concurrently and render them locally. This is rather complicated, it can be fragile and slow, ruining reader experience.]]></summary></entry><entry><title type="html">Nsite blogger is coming</title><link href="/2026/08/05/5fa574ca.html" rel="alternate" type="text/html" title="Nsite blogger is coming" /><published>2026-08-05T12:59:55+02:00</published><updated>2026-08-05T12:59:55+02:00</updated><id>/2026/08/05/5fa574ca</id><content type="html" xml:base="/2026/08/05/5fa574ca.html"><![CDATA[<p>I am working on a simple tool that makes <strong>Nostr</strong> long-form content widely visible to the public.
The idea is to use the markdown content from long form posts and feed it into jekyll, a lovely static html blogging engine.
The generated static site is published on an <strong>nsite</strong>, which closes the loop. Content born on nostr, lives on nostr with all its censorship resistant properties.</p>

<p>But for more importantly:</p>
<ul>
  <li><strong>Choose your style</strong> for the blog - this is what jekyll themes were built for.</li>
  <li><strong>Choose your editor</strong> - Nostr thrives in this space. Mobile or desktop, use the editor you already love.</li>
  <li><strong>Never lose your followers</strong> - on Nostr you own your identity</li>
</ul>

<p>Already existing tools are wired together, dots are connected to make real blogs possible on Nostr - in other words: make Nostr widely visible for blog readers.</p>

<p>Stay tuned!</p>]]></content><author><name>Lez</name></author><summary type="html"><![CDATA[I am working on a simple tool that makes Nostr long-form content widely visible to the public. The idea is to use the markdown content from long form posts and feed it into jekyll, a lovely static html blogging engine. The generated static site is published on an nsite, which closes the loop. Content born on nostr, lives on nostr with all its censorship resistant properties.]]></summary></entry></feed>