Thread - Nostr Hypermedia

Anhern Sarsalor [IQ: 102] _@animestr.xyz 4 months ago

I will definitely implement support for multiple nip05s in animestr today or tomorrow. The biggest problem is that the spec for kind 0 doesn't allow that, but kind 0s are badly designed anyhow, we can just add the other 05s as tags. Stringified json in the content when we already have tags makes no sense to me haha

↑ Parent

Replies (4)

The Beave TheBeave@GitCitadel.com 4 months ago

You are not the only one who thinks that. Tags should be used instead of the kind overload, IMO. But, whatever. I don't code, so . . . meh. It will be cool to see how you implement multi-nips. It will be like a Multi-Pass. I can finally live my 5th Element Dream IRL. LOL! https://imgs.search.brave.com/PMIpDmdhrqtFlwSjWYpwi5zaftHudHqmolRzHC6Bkms/rs:fit:500:0:1:0/g:ce/aHR0cHM6Ly9pLmlt/Z2ZsaXAuY29tLzRv/Ymc5My5qcGc

1 replies ↓

imp0stor imp0stor.com 4 months ago

Check out my pull request in the repo, I suggest using aliases as an optional nip-05 parameter that is a list of up to 100 additional nip-05 ids

1 replies ↓

Laeserin laeserin@theforest.nostr1.com 4 months ago

Alexandria already supports kind 0 tags, as does Amethyst. There's no compatibility problem with having multiple NIP-05s, lightning addresses, websites, etc.

1 replies ↓

Anhern Sarsalor [IQ: 102] _@animestr.xyz 4 months ago

Do you still parse the legacy kind 0 content and then append the tags? That's what I'm doing right now. When the profile is saved I include both formats to not break compatibility. A bit wasteful IMO, but I can't think of another way until all clients switch to tags for kind 0

1 replies ↓