mleku on Nostr: nostr events are addressed the same way, by the event id, which is a hash it's even ...

nostr events are addressed the same way, by the event id, which is a hash

it's even something i thought about doing - creating a layer 2 that uses blossom with the ids as the ids... the only tricky part is that blossom expects that to be the whole event but the thing that makes the hash is missing the signature, and the signature then has to be added but it can't be part of what is referred to by the content, it has to be attached to it (this is how i implement the event store on realy)

probably a simple extension to blossom could be suggested where you can provide an npub and signature adjunct to the file being identified by the hash, but this is precisely the point you are digging at - what about we just use nostr event format... i mean, can store arbitrary sizes with the small limitation of using 6 bits per byte as base64 encoding, this is a limitation of json

how it's actually stored, can be entirely different, it can be binary encoded, or you can mess with it and use json for the metadata and then attach giant blobs of binary to the end and store that against a key in a key value store