pull down to refresh
0 sats \ 1 reply \ @thrown 4 Mar 2023 \ on: Nostr: First experience posting NIP-23 Long-form Content nostr
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
From what I understand:
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
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...
reply