nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg will the next update support the nostr:nprofile, nostr:nevent, and nostr:naddr formats? I see so many broken links in notes when I use Primal because other clients post those formats by default.
Discussion
We already support those formats. When you see broken links it means that we couldn't find the event in question. Working on improving that. š«”
Oh ok cool, thanks for the explanation šš«”
if I copy your note's ID and paste it here, it looks like this:
note1p098zjg6w3yg9khxwwk7svjxr5v0c8ldxtwn4jggavpaqf0u24fsdf4q79
shouldn't we copy an event that primal displays correctly?
oh interesting, the Android client displays it correctly as "a note within a reply". seems like only my browser primal client can't make use of the note ID.
The correct syntax is nostr:[noteid].
Some clients try to display the embedded events even without the "nostr:" prefix. Maybe Primal should too.
So its a primal caching/crawling issue? I thought primal client is using outbox model as a fallback