We’re going to display both the short posts event type 3, and the longer event type 30023 for longer form texts with markdown formatting in the same feed.
The confusing part is going to be in posting where we will need to communicate to users that if they use markdown then not all clients will display their content.
So if there is markdown it will be considered long form, or does the user control the type (via the client)?
Not exactly. The way it works is that if it’s an event type 3, you shouldn’t use markdown and if it’s event type 30023 you can use markdown. The lengths of the two message types are the same.
Personally I would rather have a field on event type 3 that said formatting. But my understanding is that #[7]​ didn’t want markdown showing up in the primary tweet like messages so the support was relegated to a secondary event type.
Clients choose which message types they support. Relays can also choose which they’ll host.
Right, I was asking how the type is set, does a user have to know about types? Or if they use markdown it becomes the long form type?
Event type is set with all messages, the text ones we’re using here are type 3… but there are a ton of others. It’s set upon writing and signing the messages.
Habla.news is a good example of a nostr app that uses longer form events vs the normal type 3.
