Exactly… NIP96 always uses the original file’s hash in the url even when the content was transformed, I.e. then the content returned does not match the hash in the url. Mirroring/Reupload with the same hash is therefore impossible.
When transforms are disabled (there is an option) then NIP96 behaves very similar to blossom in terms of hash usage (except for paths and auth events).
Kieran nudged me to implement both on bouquet.slidestr.net and they play along nicely when not using server side transformations.
florian
npub1kl…27gxc
2024-09-20 18:58:25
in reply to nevent1q…za6y
Author Public Key
npub1klr0dy2ul2dx9llk58czvpx73rprcmrvd5dc7ck8esg8f8es06qs427gxcPublished at
2024-09-20 18:58:25Event JSON
{
"id": "5135205f1e8c80b6e70140384f61a4fb5908838b3f46f0189c0c322ce62da4a2",
"pubkey": "b7c6f6915cfa9a62fff6a1f02604de88c23c6c6c6d1b8f62c7cc10749f307e81",
"created_at": 1726858705,
"kind": 1,
"tags": [
[
"e",
"cc6b04a37fb51d07298ed890dffb18495deca1d5ad208b3707e6c9f48531d237",
"wss://relay.nostr.band/",
"root"
],
[
"e",
"5fd48e7aa228b1e543f3d27bc9dd21d9f24d38bfa08b650bf22c4b93a7aedbcf",
"",
"reply"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
]
],
"content": "Exactly… NIP96 always uses the original file’s hash in the url even when the content was transformed, I.e. then the content returned does not match the hash in the url. Mirroring/Reupload with the same hash is therefore impossible.\n\nWhen transforms are disabled (there is an option) then NIP96 behaves very similar to blossom in terms of hash usage (except for paths and auth events). \n\nKieran nudged me to implement both on bouquet.slidestr.net and they play along nicely when not using server side transformations.",
"sig": "69f4072da90c7f988204a79c4e1878262b415c20e02e9075b314e9bac17709d3c986a8babcdebf76489c202f62060461fd5760c4f1822267f5323106b704ea55"
}