I was actually thinking of something like this for a while now. Could we have the clients focused on kind-1 notes fetch kind 30023 events and then if someone replies to such posts on the blogging platform, provide a link to the source instead of displaying the comment as a standalone note? Maybe there’s some other solution? I do understand the decision of some clients to avoid support for long-form posts as that can mess up the UI, but people get confused when they see something that feels like a reply, but can’t figure out what the original note is.

What you think, nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg ? nostr:note13vt26xqjaczvzqvp842d2zffjqute76u6xukr5hl285ef4e7kv4qx63hp0

Reply to this note

Please Login to reply.

Discussion

Ideally, they should use NIP89 to pass that event to an app that can handle it. Each user can then register the apps they use for each event type on https://nostrapp.link/

I think clients need better handling of unknown event types. I'd argue that most social clients will want to at least render an article preview for long form, is super easy. Making comments kind 1 also heps long form content discoverability.

Previews would be nice!

In the meantime, use #Amethyst lol

That’s the plan

this is what flycat does

Have to manually get from inspector note1zr29z86sftl9dkfcavneevhyv045m6ed0t62fyp5dfw5hnvh4pyszzdn2k