Added an optional "a" tag to the spec so nip-33 events can be referenced by zaps https://github.com/nostr-protocol/nips/blob/master/57.md#lnurl-server-side Including the a tag in the receipt allows to get the zaps for a replaceable event even after is updated.
Las listas y los badges son eventos nip 33 por lo que pueden ser zapeados también.
Hasta hace poco solo podías zapear un evento por su id o una pubkey. Los eventos reemplazables NIP-33 son editables por lo que cada versión tiene un id de evento distinto pero solo la última se guarda en nostr. El tag "a" permite referenciar un evento reemplazable independiente de su id de evento con la forma "kind:pubkey:d" para que versiones posteriores mantengan los zaps. Espero haberme explicado!
porque es un artículo sobre la comunidad hispanohablante en nostr.
Great news! The fine folks at #[0] have implemented "a" tag support for zaps so people can zap your long-form content (or any nip-33 event) and zaps can be retrieved even when the content changes. #[1] thanks for the zap in https://habla.news/a/naddr1qqgxs6tnwpskummgv93xcctww3jhxq3q07jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2qxpqqqp65wp8usm4 ⚡
Added two more historical badges to my long-form article: the #[0] #nostrica attendance badge and #[1] pioneering the use of badges as in-game awards.
sorry for spreading misinformation man, I just posted a public apology 🙏 Should have verified pubkey, my bad.
Earlier today complained about #[0] spamming badges but I was wrong, turns out it was an impersonator. My bad, should have verified the pubkey first but was sleepy and angry. I'd like to publicly apologize 🙏 Will be adding better moderation to badges.page whenever I find some time, sorry for the inconvenience.
yep, we already do that for embedded nevent for instance. need to: generate naddr with relay URLs embedded, use those relays to get the article when visiting the link. will do soon™️
does it have any obvious issues or shortcomings?
seems like we are building a bunch of apps on top of nostr without solving fundamental key management, security and UX issues first. i'm guilty of that too so focusing on shilling/implementing NIP-26 and NIP-46 where i can.
yes, I'm going to add relay list to the naddr URLs habla generates. URLs will be longer but the site will know where to find the content.
is only published to the wss://nostr-pub.wellorder.net/ relay. I need to add relay to generated `naddr` URL so they are always found, in the meantime you should see it if you add that relay to your list.
look at what #[5] folks did with badges yesterday, really cool use case imo https://stacker.news/items/149993
that is lame af. good part is that they can't steal your ideas, creativity and reputation so your badges are worth much more imo. we are showing badge author alongside badges so people can verify that it comes from a reputable source.
allowing you to mute people and adding a toggle to only show awards by ppl you follow in Awarded.