nostr:npub1jrx7jrtky3hr9g4kg5xzdy23yde2ga3huxdxezvmmryn06nry7csh4qv9r nostr:npub1rqwkxyzs2z93wdhl2eu56put4c8mqzar0rpeq7d087hcl9z2xcuqnf8g6a nostr:npub18qspvzn3qyxh4jrex8ed07nzrgxjvxfykmglzvzy8dneta4hy5usg60s8s Took a while to get it to work, and it doesn't seem to work on all Mastodon instances... yet.
nostr:npub1rqwkxyzs2z93wdhl2eu56put4c8mqzar0rpeq7d087hcl9z2xcuqnf8g6a nostr:npub1lj756j70nykyqjtz5hfs43gkzyvzjpq36lt9u2qxxrp9jtqws5mqkdzczx ,
I see it now. I looked earlier using #Chrome which has some strange caching behavior.
Repeating the process using a different browser, as I should have in the first place, confirms the placement of "me" attribute and value (one's profile doc url) pair in
Now I need to see if nostr:npub18qspvzn3qyxh4jrex8ed07nzrgxjvxfykmglzvzy8dneta4hy5usg60s8s is picking up my cross references en route to validation :)
Discussion
nostr:npub1lj756j70nykyqjtz5hfs43gkzyvzjpq36lt9u2qxxrp9jtqws5mqkdzczx nostr:npub1rqwkxyzs2z93wdhl2eu56put4c8mqzar0rpeq7d087hcl9z2xcuqnf8g6a nostr:npub18qspvzn3qyxh4jrex8ed07nzrgxjvxfykmglzvzy8dneta4hy5usg60s8s,
Finally cracked it. Here's how.
Over here I was pointing to https://www.threads.net/@kidehen (which does resolve) rather than https://threads.net/@kidehen.
That was it, bar confusion introduced by caching in my particular #Chrome instance.
This is a "Big Boy" move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).
