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?
