Yep, but that makes an Amethyst solution. Not an all clients solution. Way less ideal
Discussion
Why not all clients? They can do the same, no?
It would be similar to the mess with ln services before the wallet connect nip: UX Inconsistency everywhere.
Plus, we can always use the blurhash for loading and content descriptors dor accessibility.
I’d like a hash addressable content approach if we can find a solid approach. Swapping out referenced content, without easily being identified as changed/different, isn’t a property we should build toward.