SHA256 is already supported

Reply to this note

Please Login to reply.

Discussion

ok so that means that you can store the nodes in events and refer to blobs to fetch them

blossom imo as a protocol is garbage, as it tries to consolidate management (upload/delete/list) with retrieval of blobs

it is a big pain in the ass for scaling, look at any service and you will see cdn domains are separate from upload

blossom also makes no attempt to allow media optimization, and I believe it is an acceptable tradeoff to sacrifice integrity for reduced data usage if you can turn it off as needed

blobs should be identified by nostr event IDs, meaning you get metadata for free, and if a user wants their blob gone, they can issue a delete event and send it to all hosts

rehosting content becomes an explicit action

Well, after Alexandria Gutenberg we're going to work on Aedile SDK for a bit, and we can maybe think up a scheme for Blossom 2.0, while the guys fiddle with C++..

Code name Weed.

the use of nostr as a flexible mechanism of reference is the elephant in the room