Saw this coming from a freaking gazillion miles away:
Just create a very simple Nostr-Markdown spec already. That can be used in ALL longform.
nostr:naddr1qvzqqqr4gupzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyt8wumn8ghj7mnfv4kzumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qq2f4shy6mydamku26wshwvvp
Stop jumping to the next-best-thing all the time like babies.
Breaking the current implementations (and motivations!) of others.
Did you read this?
nostr:naddr1qq2k642sveax7uzf0far2k2kg3uh5urdgvu5xq3qgzuushllat7pet0ccv9yuhygvc8ldeyhrgxuwg744dn5khnpk3gsxpqqqp65w3vgu9p
Yup :checkmarkgreen:
And I agree. Honestly think 🦋 Bluesky is waaay better in this regard too btw.
And so bad in so many others hahaha we just need to acknowledge the stuff that makes us weak
I learned how to make tables on asciidoc now I have to learn how to make them on djot, it seems fun
*fix the stuff that makes us weak
First step its acknowledge, then fix 💪
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.
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.
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.
