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