This morning, I decided to look into the NIP-23 specialized clients, and try to publish long-form content on the Nostr network of relays:
First, I encourage you to read the NIP, and the first thing that you will notice is that the
kind id used to publish is 30023 instead of 1, so most social clients (like snort.social and maybe damus?) will ignore these notes. But Amethyst supports fetching kind 30023, so it will appear in your feed next to normal kind 1 notes.Then, to publish using habla.news and blogstack.io, you need the
getalby extension to log in.First impressions on publishing
habla.news
- offers a markdown editor and a toolbar to help if you don't know markdown very well
- also gives you additional fields, for a title, slug, banner image, tags, and a summary
blogstack.io
- offers the same markdown editor as habla.news
- no additional fields :( (Note: I could not log in again to test if additional fields were offered before publishing after having written the long-form content, because of a weird message: "Install Alby Extension and setup keys to Login". even though I was properly logged in with my getalby extension)
First impressions on viewing
blogstack.io blog post rendering is a lot better than habla.news (especially with paddings, blockquotes, and nested bullet points...)
| blogstack | habla |
|---|---|
Like everything Nostr, it's very early. But if the last months have shown us anything, the ecosystem is moving super fast.
I am going to start integrating NIP-23 into my publishing habits and see how it goes...
What about you? Did you try publishing some long-form content? Any experiences, good or bad, to share?
kind 30023properly defines the note as an editable one, with specific "blog-like" metadata (title, summary, banner, content as markdown) (see https://github.com/nostr-protocol/nips/blob/master/23.md)kind 1are simple immutable notes in plaintext: https://github.com/nostr-protocol/nips/blob/master/01.md