nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 I am seeing more Nostr.build links not displaying well on Primal iOS. Is it a specific client that is not handling uploads well? Is it Primal display issue? When I upload direct to Nostr.build and copy link I don’t see these issues.

Reply to this note

Please Login to reply.

Discussion

nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr , do you support nip96? Ideas why the broken links?

It’s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ‘s Amethyst (from what I’ve heard) adding the # parameters after the link. I am not sure why it is needed since I assume all of that can and probably should be stored in the note metadata. It also causes issues on Snort and nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 already raised that concern. 🐶🐾🫡

It’s done by the client that makes the note, upgrading Amethyst will not help Primal to render these links. If nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg is having n issue then they could mitigate it, but I still think adding all these metadata to the link is unnecessary and consumes more data than is needed. 🐶🐾🫡

There's no update in the Google play store?

Looks good on Amethyst and Damus. Only on primal iOS (0.9 or 1.0) does it fail to render.