hodlbod
hodlbod
> Your comments won't reach without you knowing why. That's fair, maybe that would be ok. > Correct me wrong but can't you verify it has been received by looking...
In pretty much every case I've seen it's better for d tags to be random. Maybe p/e tags would make sense though, since they're immutable, but what's the use case?
That's not great, I didn't know issues could be deleted completely. Do you know what used to be there?
We should also add `icon`, which I've seen in practice.
I think we're thinking of different things with `icon`. I don't think there's any point in providing an `.ico` format, which in my understanding is sort of a legacy format...
nostrelites.org - jpg cyberspace.nostr1.com - png relay.proxymana.net - png bitcoiner.social - ico relay.0xchat.com - jpg yabu.me - png nostr.wine -jpg I think just keeping it to "image" is descriptive enough....
It would be great to merge this so that we can start checking `supported_nips` for support rather than targeting negentropy software versions.
Other examples include syncing NIP 29 `h` tags or topics. I think arbitrary syncing is a very good thing to have. If we have the flexible version I'm not sure...
I saw your note, and I agree, it would be nice to know if you have a complete dataset, although this is kind of a fundamental trade off of nostr...
I agree with Vitor, and will elaborate by saying that edit should be append-only (or switch kind 1s to be replaceable).