nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z it seems that some users on Amethyst experiencing issues and seeing long links instead of media. Any help or remedy for this? 🐶🐾🫂🫡

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z it seems that some users on Amethyst experiencing issues and seeing long links instead of media. Any help or remedy for this? 🐶🐾🫂🫡

A new update released
Dear nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z even updating to the latest version doesn't work. And I checked. The links open and show in chrome. It is imdeed #amethyst

Hum.. how common is this? Many images are now like that. It should happen alat every 4 images or so if the url is the issue. If it is more rare, then it's definitely something else. 🤔
Also, I have only seen reports of this with nostr.build. have you ever seen a url from void.cat or nostrcheck?
But what is causing this? Is the string parsed on the client? Is URL interpreted correctly? Is it because TLD is .build? 🐶🐾🤷♂️
I am not sure. It could be as simple as an Internet connection issue. If Amethyst can't download it, for any reason, just displays the url. So, it could be anything.
Ok. Why did it start when the URL was modified to include hashtags client-side arguments? Do we have a good nostrcheck.me example with identical URLs showing that one works and one doesn’t? Why were metadata not included in the note as nip-94? 🐶🐾🫡
I don't know. The interface is new on both nostr.build and amethyst (as well as many other servers). We didn't include as NIP94 just because other clients are not displaying it, so these tags were the little hack to keep it working.
But again, how many times do you see these urls per day?
I am on Damus, I see 0 times and never saw them to start with. The little hack caused a little havoc in other clients for sure, but in reality it shouldn’t be a problem and shouldn’t be a long term solution either 🐶🐾🫡
Wait, is this an old screenshot, then? I only have 2or 3 reports of this happening. I though you had a new case, but maybe it's one of the old ones?
No, it’s nostr:npub1cpazafytvafazxkjn43zjfwtfzatfz508r54f6z6a3rf2ws8223qc3xxpk who is still experiencing issues. I think he stated it loud and clear in his note. He is on the latest version (AFAIK) 🐶🐾🫡
It's me who raises a voice because I care and think it is useful. There are probably more such UX amoung the thousands of users.
Maybe I need to make it retry to download after a few seconds. 🤔
Does it actually fail? 🐶🐾🫡
Also, are you 💯 sure that you are not sending the #… params to the server, since they should only be interpreted at the client and never seen by the server. As per the http standard … 🐶🐾🤔
Retry and erfresh is a good idea but only if it is actually needed. To avoid wasting expensive internet traffic.
Not sure how common but I see it quite a lot.
Many times a day?
Are they on the latest Amethyst version? Those links should render fine on newer versions that support NIP-54 (later than v0.82.3 in Amethyst)
If I go and get the latest version from github it'll resolve?
Tbh, I am dreading a new update after this.
That should fix it. There's also a new marketplace built into that release that's worth the upgrade IMHO.
Yes. Amethyst is awesome like that.
If only I was not prisoned in a secluded island...
Oh, my note 😔😭
I'm using the latest update v0.83.4
Works fine on my end. Let me know if you are able to see my note correctly after the update.
I updated and got the long ugly link again. But saw your beautiful clip in the browser.
How do you see that one? I deleted everything after . mp4
https://video.nostr.build/458d71bfb5b42ecd1a1e2bc5ca9ef6e1f5880546d5cf19a28d31b6f32884293b.mp4
Like this ...

This one shows ok in the app. I wish I lived there
Ok, then I think I'll always delete the part of the links that are shown after .jpeg / .gif / .mp4 !
🫡🧡🫂✨🤙
Good but temporary solution
To be honest, I don't even know what this long link is for?
I'm not that technical 😁
Me neither. Not at all.
I just try to give feedback to help make things better as much as I can.
Check the version string in your amethyst menu, if you're like me and are counting on side loading you might have been tricked into thinking you updated (but instead the app installer just silently dies). Android broke side loading I had install with adb.
v0.80.7-FDROID
Yes, you’ll need to update it. Seems old to me 🐶🐾🫡
But I'm on the latest according to Fdroid
Yup, you got fooled like I did. I ran that version for months before I realized 😭
It is the most recent in fdroid app
Hm, who updates the fdroid repo is it nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z ? 🤔
Yeah old version. New version creates these links and renders correctly.
I was having trouble, updated the app today to 0.83.4 and now it works fine.
FWIW I'm using the play version and I have beta testing enabled
Android broke side loading in a way that makes you think you updated (but in reality the app installer just silently crashes with no error).. probably worth checking the menu version string imho.. I haven't had this problem since actually updating.