I find really funny that people are calling this a backward incompatible change or a "hard fork" as if it's breaking from the past.
NIP-94 is a simple new event that is now being quoted in kind 1 in the right way of doing so. This is not a breaking change at all.
This will keep happening at event kind.
This is the definition of stubborn. Clearly people are not ready for this change yet. Please show some humility. β
If this keeps happening Nostr won't last very long.
100%.
We need consensus of simple things like sharing photos! This is damaging for adoption of Nostr. Case in point:
My partner is new to Nostr as of a few days ago... and she's a #Damus user. My photos from Amethyst don't load on her client. I chalked it up to "new tech glitches" but the lasting impression on her is:
"Oh, so this App doesn't work" and "So photos don't work? Oh this is too confusing anyways".
ππ
I am sure it will... I am already working on Marketplaces events and already seeing the outcry when they are linked into Kind 1s.
Links to any other kinds are fine, the only thing that is of concern here is breaking images.
Like this 
This is a Quoted Kind1 with a link. You are displaying the image inside the Quoted Post boundaries. Just do the same for a Quoted kind 1063.
Images look like this in damus 
Not really. open this note: nostr:note16stm29mu3wpv9zu5psphv7nx54r89a028z0d9r5my3muljaml35sre4925
When you have a Quoted kind 1 the image is not edge to edge. You would do the same for kind 1063.
That note has no images in it
Itβs quoting this note which has images. Your change will still break images in damus and every other client, forcing it to use quoted posts to view images. 
But NIP94 is not a direct image. It is a quote event. I would expect to be rendered as such.
Here a post with a quoted image nostr: note1z3dt56fh42r85wf7tu6hq7fcecu9xpnj8kntxeg6zpps3j9gqhxqlh
Right note id nostr:note1z3dt56fh42r85wf7tu6hq7fcecu9xpnj8kntxeg6zpps3j9gqhxqlhhmp6
Having two different ways to display images is too confusing.
A much better and backwards compatible way could be done in either two ways:
1. nevent with internal kind and image url tlv. This would at least allow other clients to use the url if they donβt want to implement the attachment nip.
2. Keep the url and reference the metadata event id in a tag with a url index.
3. Probably many other ways that wouldnβt break anything.
If you really want this to be a file attachment instead of image then you could just keep the original upload method and let users know that clients might not be able to see your image if you use a file attachment.
All up to you, but damus will not be implementing this nip for image uploads, as stated before I think itβs simpler to encode this information into a completely optional small string so that its available on the post itself and so that clients can use the information to do all the hash checking stuff, but when they are ready, not forcing it on them.
Cheers,
Agreed. It could have been done in a backwards compatible way. NIP94 is just way too short.
Maybe in future, have a Q&A section within each NIP with regards to backwards compatibility and apriori event types?
No good reason for this
Could this happen if any country censors void.cat, nostrimg.com or nostr.build ?
I agree. Please create a short tutorial on what the best practice is for building apps on top of nostr, it would greatly benefit the community. Bluesky is tackling this problem with their "Lexicon" system, perhaps nostr could do something similar?
No, if these keeps happening then Amethyst and others who engage in this kind of anti-user interest behavior wonβt last very long.
