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
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!
Ah, nuts. I am so bad at things sometimes . . .
GAH!
Fine. I'll just upload the thing. This is silly. Images should just load directly from links.
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
No. No new tags. We already have a tag for NIP-05.
Alexandria already supports kind 0 tags, as does Amethyst.
There's no compatibility problem with having multiple NIP-05s, lightning addresses, websites, etc.
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
I'm working on a PR, to do that, right now.
I'm pulling everything from content into the tags and then deduplicating, so that the tags are standalone. Then people can just modernize their kind 0 by running it through our event publisher.
And I show the full set, in the profile display.
Irritating, that we can't just switch to OnlyTags.
Here's one, for my nostr:npub1v30tsz9vw6ylpz63g0a702nj3xa26t3m7p5us8f2y2sd8v6cnsvq465zjx npub. Is this how you were also thinking of doing it? I pull everything from content into the tags, and then I added more tags.
d259fb6cbae3ac42e943d040c9cee1cdd2e80704a62f11eab6fed38512210dfb
It displays like this, but only on Alexandria. Every place else just pulls from content and ignores the tags. The first tag of some type is considered primary, and matches the content tags.
Yes, that's how I'm doing it
And both of your 05s show on animestr. I first parse the content then the tags and merge them together prioritizing the tags. So technically if you had a different display name as a tag, then that would be prioritized.
When editing the profile I still save both versions
Here's a test event for you nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9u2mk7fe.
I can't tell if Amethyst is pulling from the content field or the tags, but it's displaying fine on all clients.
If you want to try for multiple tag entries, it's a good test event.
I can't read kotlin well, but it looks as if vitor is parsing the content first, then putting the tags in like I am?
