Nostr NIPS wiki to replace GitHub’s repo
No canonical article for any NIP; you can define what Nostr is to you. No merges, PRs, just organic coalescing around ideas when the benefits of interoperability surpass the disagreements over details of the specs.
This is the way nostr already works, my plan is to build the tool that makes understanding/observing it this way more obvious. nostr:note193ppd9jvgygw5gpfyuv2lqk5tjhtldvqk7lmszl9l4xskjxmpp3sqjn9xd
This website should teach us about the areola
Con la crypta vamos a construir un Discord en NOSTR, cualquier tipo de consulta si llegamos a necesitar no voy a dudar en consultarte ya que sos el programador número 1 de Argentina para mi
Conta conmigo, sobretodo si es para no tener que usar discord ever again!
😂😂😂 esto es para vos y para todos aquellos que odian discord, nos está pasando que nos quedó chico
can’t wait for the on-site cashu mint, nipcoin
without standards, interoperability between clients falls away. client maintenance to support all the "nonstandard" things creates friction in the development process. there are definitely at least a few highly recommended if not standardized NIPs that need to be adhered to. there's a reason the browser wars have started to end in browsers working together to standardize.
nostr:nevent1qqszsypl99cq3yuke4lhtve7x9jyqk8l694sx32h2l2uqmwvgd4qu7spz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqvzqqqqqqymea045
The whole point of a standards spec document is that it is STANDARD. Saying "everyone should define their own standards" (especially for a network communication protocol) is like telling vehicle drivers to choose their own traffic bylaws.
Relevant XKCD. https://imgs.xkcd.com/comics/standards.png
how can a protocol exist with a canonical spec?
“you can define what nostr is to you”
lol what?
Oddbean new post about login | logout 