๐๐๐๐
nostr:naddr1qqwxzmnwda6kucm9d4jkuapddanz6ctwdehh2mnrv4kk2mn5qgsg8kve59yxyhpa9wupntesvnq0dgfd0k5g769jc6fzrua8gct36xgrqsqqqa28aepjch
๐๐๐๐
nostr:naddr1qqwxzmnwda6kucm9d4jkuapddanz6ctwdehh2mnrv4kk2mn5qgsg8kve59yxyhpa9wupntesvnq0dgfd0k5g769jc6fzrua8gct36xgrqsqqqa28aepjch
This is a perfect example ๐คฃ
nostr:note1cwqtha6k9kpnhgzmdfma9gzamn8gezq84x0tzvyw0z3msxu6xv5strwrkq
In other words, I see only an โaddrkksblahblahโ and I canโt search it. So I have no clue what your note is about ๐
This one links to a long form article, not all clients support it yet
https://nostrcheck.me/media/public/nostrcheck.me_3880476600694788791691073195.webp
There also seems to be a lot of inconsistency in handling of โnostr:โ linking. Is that actually in a nip somewhere or do some clients just use that URI scheme for their own purposes?
Thanks I had missed that one!
I've had the best experience on iOS with the Nostur app supporting a wider variety of event kinds like this one.