Hashes should just be bech32 encoded with ”file” prefix so the client knows it’s a content hash.
Discussion
Sure, but not everyone uses nostr.build and I don't see a path all other image servers implement something similar.
You could also add the content hash to the url as a query string or anchor tag.
Website admins will get confused and scared, so name it something like `?nostrbooboo=` 😄
Yep, but that makes an Amethyst solution. Not an all clients solution. Way less ideal
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.
What's the other possibilities for benefits? Does it decrease file size for relays? Does it have any security improvements?