Unfortunately I cannot unbreak your image posts. Only vitor can do that.
Discussion
oh come on... you definitely can... You just don't want to...
You could implement your change in a backward compatible way, but you chose to make Amethyst users unable to share images with other clients, instead
I could if I didn't care about following a NIP and just decided to do things my own way, like Will is doing.
🍿
But that begs the question, do we want to be creating NIPs that break fundamental existing functionality like sharing images for clients that haven't adopted it yet?
I would imagine the majority of users aren't going to be stoked about their client adding the cutting edge NIP if it means their followers can't properly see their posts.
I need to look into it deeper, but it sounds like NIP94 was a well-intentioned attempt to add functionality to *specific* nostr use cases outside of social, but because it includes a benefit that social network clients can also use, it ended up being confusing.
Usually, they don't break anything fundamental. But they do break things all the time.
Every new event kind can't be seen in Damus until they code it. In Amethyst, it shows as "Post not found". We don't remove the post. It's just the way Nostr works. Anyone can create these new event kinds, with or without NIPs. And when that happens, things "break" (wrong word, though. They don't break, people just can't see it for a while)
This happened when Markdown was implemented. Suddenly many clients, Amethyst included, couldn't display the content correctly. More recently we had mathematical equations being added to Habla News. Those don't render in Amethyst as well. Similar to Private Zaps (which is not even a NIP) that Amethyst users couldn't see it until last Monday.
This is a normal course of business for any Nostr client.
Refusing to implement a NIP and creating a hacked-up version of the same NIP, however, is something new.
