Niel Liesmons's avatar
Niel Liesmons 3 months ago
Saw this coming from a freaking gazillion miles away: image Just create a very simple Nostr-Markdown spec already. That can be used in ALL longform. View article → Stop jumping to the next-best-thing all the time like babies. Breaking the current implementations (and motivations!) of others.

Replies (18)

Niel Liesmons's avatar
Niel Liesmons 3 months ago
Yup :checkmarkgreen: And I agree. Honestly think 🦋 Bluesky is waaay better in this regard too btw.
Niel Liesmons's avatar
Niel Liesmons 3 months ago
In fact, you could make the whole protocol work with just two text syntaxes: 1️⃣ Nostrified Markdown, for all simple short and longform text 2️⃣ Nostrified HTML, for all complex renderings and functions Keep 1️⃣ very simple and just reference 2️⃣ events in it for the complex stuff.
Niel Liesmons's avatar
Niel Liesmons 3 months ago
I have been acknowledging for way too long hombre. Good thing my fixes are :90percent: there and i don't have to care about the :AirQuoteLeft: momentum :AirQuoteRight: of the main protocol devs for my use cases.
Niel Liesmons's avatar
Niel Liesmons 3 months ago
:nostr: Markdown wins. All the :AirQuoteLeft: cool stuff :AirQuoteRight: djot adds, can be referenced Nostr events (Math, Tables, etc...).
Yea, me too monsieur, but no wider recognition around the ecosystem, nor nip maintainers did ack
This is very well written. I looked at the comments, a lot of them understandably based on people's experience of Nostr as a network with something like 7k daily active users, give or take. There is just no comparison between that size and a network of even just 1m daily actives. The article nods to this and so thumbs up.