PABLOF7z's avatar
PABLOF7z _@f7z.io 2 years ago
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.
PABLOF7z's avatar PABLOF7z
It's time. Guess what microapp I'm going to be building next image
View quoted note →

Replies (13)

brah's avatar
brah 2 years ago
This website should teach us about the areola
negr0's avatar
negr0 negr0@hodl.ar 2 years ago
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
1 replies ↓
negr0's avatar
negr0 negr0@hodl.ar 2 years ago
😂😂😂 esto es para vos y para todos aquellos que odian discord, nos está pasando que nos quedó chico
w3ird_'s avatar
w3ird_ _@w3ird.tech 2 years ago
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. View quoted note →
1 replies ↓
Default avatar
npub1l6uy...zvtg 2 years ago
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. image
↑