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. 🐶🐾🫡

At one point nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z recommended an upgrade.

nostr:npub1tjyl4n64583tgn2xjlsf3v6dvce07endn6upnj5tykkzl09hfhdsyq0e9k , nostr:npub1ds8fq94ec8h70m00sljstc4puq7mr7aulhp76660324yk4q2mx8sdyf93l , are you using Amethyst? If so can you try upgrading?

Reply to this note

Please Login to reply.

Discussion

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.