NIP-96 or Blossom?
At first glance I don't like either. Blossom should offer NIP-94 file metadata as HTTP header fields for GET downloads, not just BUD-08 /upload /mirror. Blossom allows delete, but what if two different users upload the same data? NIP-96 OTOH has a complex nip96.json file with weird decisions (e.g. waht if api_url specifies a different hostname? Why have delegated_to_url given that state of affairs? Who is going to understand these complex plan objects?)
Mike Dilger ☑️ /
npub1ac…9p35c
2024-11-09 00:03:14
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cPublished at
2024-11-09 00:03:14Event JSON
{
"id": "0000e75e90dfb25f194d81675a187259fe04b2cb40fa583ba6d7ad55f1df0e3d",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1731110594,
"kind": 1,
"tags": [
[
"nonce",
"14603672391686729615",
"16"
]
],
"content": "NIP-96 or Blossom?\n\nAt first glance I don't like either. Blossom should offer NIP-94 file metadata as HTTP header fields for GET downloads, not just BUD-08 /upload /mirror. Blossom allows delete, but what if two different users upload the same data? NIP-96 OTOH has a complex nip96.json file with weird decisions (e.g. waht if api_url specifies a different hostname? Why have delegated_to_url given that state of affairs? Who is going to understand these complex plan objects?)",
"sig": "8becd99da3259c659404dca08ea75ae605e3c9b735dfd7e44d6f79f1bc36710459b0e796af3a1be71238401a53d59dce0495160f1adaa56c55490ee31bbe5672"
}