My idea would be to post a long form kind 30023 https://github.com/nostr-protocol/nips/blob/master/23.md at a separate "mister-monster's blog" public key, that way followers who just want to read your blog don't have to see your day to day social discussions. Then I'd boost it with this key. You have an actual blog and I wouldnt, so you'd maybe want to include a link to the blog post URL at the bottom of the note.
I'd probably write a CLI up that reads a text file and publishes as a note. You'd probably prefer to write something up (or find something that already exists) that subscribes to your blog and when a new post appears, publishes a nostr note. That way the process is automatic, either you run a command or it happens by itself somewhere once you publish a new blog post to your blog.
For boosting with your "main" key, if you decide to go the separate key route, I'm sure there's an auto boost bot out there, but that shouldn't be hard to write either. I'm sure there's another way with delegated signing or something like that, but that's all overkill to me. I like to KISS, and 2 separate keys, one for my social and one for my long form, are perfectly fine to me.
I love this idea. Super cool… and doesn’t sound too hard to implement. I can probably write a GitHub action when I deploy to my main branch. I already have that working for my blog deploy which is just parses Markdown files.
What clients currently support this NIP type?
I know amethyst supports it. Most do I believe, it's not that different from kind 1, it's just formatted long form text, I think most clients that render kind 1 also render the long form by default.
nostr:npub1m5s9w4t03znyetxswhgq0ud7fq8ef8y3l4kscn2e8wkvmv42hh3qujgjl3 Finally got around to posting my blog stuff on Nostr using the NIP 23 spec. Thanks for pointing me in that direction. Super cool! I still need to configure an automation, but I wrote a parser/posting system in python, so it shouldn’t be too hard to do.
