Even rougher, but yes.
Discussion
I actually love when one of you implements a cool NIP and everyone else has to follow or figure out an alternative, feels like the right kind of innovation π«‘
Wrong, that's horrible and stupid and is breaking the protocol.
DAMN, so.. Iβm guessing the right thing is to support the agreed upon NIP design ? Not introduce an alternative.. idk enough about this Iβm willing to change my mind
But seems like a backwards compatible solution could fix the current broken thing, but is it sorta like a bandage ?
Can we atleast make it backward compatible. It's broken right now.
It's not broken. That's the way we add any other content to posts in Nostr. I am just adding a NIP94 event.
Ahhh okayyy π«‘
This is superior in many ways I understand but experience is broken.
Only because some clients have yet to implement NIP-94. That's ok. We saw the same things with zaps, long form contents, polls, which other apps also don't see.
In all other cases damus can ignore them, but breaking images is an insanely bad experience for all other nostr users. Why do this?
Because we are pushing forward. NIP-94 is a better way to link to a static file and we would love to see all clients implementing it at least to view URLs.
And it's ok to cause issues for APK users. They are the ones pushing Amethyst forward anyway.
PS: You don't need to write NIP-94 events if you don't want to. But reading them will be a must sooner or later.
Is it possible to maintain backward compatibility without breaking the user experience while also implementing new cutting-edge features
I mean take a example of this post. On Amethyst it seems like Will posted this picture.
If I Quote a Poll or a Long Form Content, Damus users will not see it as well.
Those are not fundamental things. I can hide that easily. Images are pretty core to nostr at this point and urls are the gold standard. If you want the extra goodies provided in that nip you can achieve the same things in a backwards compatible way.