How can we get more long form content on to Nostr? This seems like a great place for blog posts, substack style newsletters, medium like posts, etc… But it’s not so easy. The wordpress plugins for nostr do unformatted short posts with links. We added long form markdown support to rsslay, , but rsslay has some pretty big design flaws which can’t be fixed. It doesn’t act like a normal relay, it doesn’t store anything, instead each time you request an npub it goes and redownloads the rss feed associated, creates NEW events, and provides them once to that client that requested them, and then deletes the events from memory. So if multiple people follow a feed, they’re all slowly getting different versions of the event. I want it to be easy, nicely formatted markdown, ideally with support for the paid subscription content stuff @PABLOF7z is working on. Thoughts? Has somebody built something? RSS is probably the easiest way although lots of formatted content in rss is a mess. It needs to be something that can push to multiple relays the way mostr does. It needs to import once, and then scale with the nostr network. Users who comment on the post need to be commenting on the SAME event, not multiple versions of the event. We’re SO SO SO close to this working, yet somehow it doesn’t.

Replies (23)

It may sound very stupid, but I think some form native support for threaded notes is needed! The naive reaction would be: But we have long form posts!! (habla) But a long (Medium like) article is not that compelling: it disturbes the flow you’re in whilst Nostering. In a thread of tweets/posts users can chime in AT EVERY F* PARAGRAPH ! In a Habla / long form post ONLY people who go there will react and that’s visible to almost no one, out of your notes context. So, threaded notes, please…
Please take a look at The central idea is to turn feeds into "communities". See communities (you can take a peek at ) as decentralized "websites" with a comment section included. It replaces youtube/reddit/etc. It all depends on the client and how you want to present that content to the user, but ultimately the "backend" is the same -- Nostr.
I’m building https://www.drupal.org/project/nostr_content_nip23 More info with demo: https://yakihonne.com/article/naddr1qq4kummnw3ez6ur0wdek2ttywf6hqctv94kx7mn894nx7und943k7mn5v4h8gttwd9cz6v3nqgsqvcu68pkfcyq5y9mz9n9u7sys33835rpnuglc6mtg7j4lv40c7ugrqsqqqa28uerlaf Last week I modified the CKEditor5 to save the output to Markdown instead of HTML for better a better editing UX: https://www.drupal.org/project/ckeditor5_markdown_editor Still a lot work to do to make Drupal a fully native Nostr client for managing content.
That’s neat, i’m a fan of POSSE. Getting Nostr tools for a bunch of CMS’s and then support in to the social media tools people use for cross posting is going to help a lot getting a diversity of content on to the network.
I appreciate this feedback a lot! I’m working out a proposal for a small opensats grant so I can spent more time on this besides my dev work for clients. What’s your favorite cms? Or content publishing tool?
pjv's avatar
pjv _@pjv.me 2 years ago
I'm definitely planning to get long form content from Wordpress -> nostr working in my nostrtium plugin as soon as I have some clear time to dive into it. I've had no time to work on it for some months now, but I hope to have a window sometime in February when I can work on this.
The biggest problem with our rsslay fork imo is that we are trying to convert html to markdown. That will never work seemlessly and results in a reading experience that is worse than the original website or an RSS reader. Maybe we need a Nostr kind for html content, or maybe we need better tools for authoring and cross posting long form content.