Nostr: First experience posting NIP-23 Long-form Content \ stacker news ~nostr

pull down to refresh

Nostr: First experience posting NIP-23 Long-form Content

836 sats \ 6 comments \ @bataroot 4 Mar 2023 nostr

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.

https://nostr.build/i/nostr.build_176775f37e909ff065f66f805236b5e54192dc1dfa953fd87b36d2ad099459b8.png

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
https://nostr.build/i/nostr.build_df1fdb35d4350b2e1afe4749af2577f535c10f061a3104a6ee08557e25e096ed.png	https://nostr.build/i/nostr.build_0e0e7349e09c3c1452924289529bdbe2d3b9fe9b3b300ac56856c32e203559c3.png

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?

view all related items

105 sats \ 2 replies \ @chrisatmachine 4 Mar 2023

we'll look into the login issue, thanks for trying out blogstack. We do offer the additional fields after clicking publish.

0 sats \ 0 replies \ @nout 4 Mar 2023

Nice! I like blogstack! There's still couple of css nits I have with it - too much spacing everywhere (e.g. in ul>li lists), links are not linkified, there are scrollbar borders in random spots.

Just for inspiration I recommend checking out lesswrong: (e.g. https://www.lesswrong.com/posts/895quRDaK6gR2rM82/diseased-thinking-dissolving-questions-about-disease ). They have really fine tuned their reading experience...

0 sats \ 0 replies \ @bataroot OP 4 Mar 2023

Great! I will definitely try it for my next post. Thanks for the great work on this.

0 sats \ 0 replies \ @66fdcf7c58 22 Oct 2023 freebie

Had a great experience with blogstack on my first longform content "Setting up a Nostr and Express web app (Part 1)" https://blogstack.io/naddr1qqyrqwry8yexxcm9qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsygrxlh8hckrapewuvy6g2ud48dgd028r6af549s0qgjv32322t3fzgpsgqqqw4rszhzje5

0 sats \ 1 reply \ @thrown 4 Mar 2023

Why was a new kind and NIP needed when clients could just cut off the text if it got too long and hide it behind a “read more” button?

People already post whole newsletters as regular notes.

Also, if we need a different key signing app for every platform and device, it kinda defeats the purpose of the key signing app consolidating and securing our keys to begin with. Nostore on iOS, Alby on desktop, etc

0 sats \ 0 replies \ @bataroot OP 4 Mar 2023

From what I understand:

kind 30023 properly 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 1 are simple immutable notes in plaintext: https://github.com/nostr-protocol/nips/blob/master/01.md

About the signing, it's just a design decision of these 2 apps (habla and blogstack) to delegate the signing of new notes to getalby, nothing prevents anyone to publish a NIP-23 long-form content signed by a different method...