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. 🐶🐾🫡
At one point nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z recommended an upgrade.
nostr:npub1tjyl4n64583tgn2xjlsf3v6dvce07endn6upnj5tykkzl09hfhdsyq0e9k , nostr:npub1ds8fq94ec8h70m00sljstc4puq7mr7aulhp76660324yk4q2mx8sdyf93l , are you using Amethyst? If so can you try upgrading?
Discussion
Hey guys! Yes, we can mitigate this issue on our end. Next builds of our iOS and Android apps will handle this scenario. I expect both updates to be available next week.
Awesome! It would be great if cache headers were respected too, so we can allow users to delete images that are exposing their privacy. 🐶🐾🫂