It would have been insanely easy for him to make this backwards compatible. Instead he opted to build this on a deprecated mention spec with no url hint to make it maximally backwards *incompatible*. Bcash vibes.

If that's the case the only solution may be to put dasmus on Android and let the users decide.

The point is that NIP-94 wasn't meant to be for embedded images in kind:1 notes. If someone really wants to reference a kind:1063 they should be able to, paste a nevent code and that's fine, but they shouldn't expect other social clients to be able to understand these events, so it makes no sense to make that the default way of loading images. The best way to ensure that the protocol is kept simple is to not assume other clients will implement whatever NIP you think it's cool -- you can implement anything you want, but you should still make it so the experience works for others that don't.

If(response.type == nip-94){ //do nips } else{ //no nips :( }

Just a Nostr pleb here but isn't that setting completely subjective standards and therefore adding politics into it? How can we have clients competing for the best experience and most features, within the rules of the NIPs, while at the same time asking for all-vs-all compatibility?

If users can't all connect on the very basics of social media like text & images, it seems to me this presents a potential hurdle of unintended censorship.