nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w nostr.build is you, right? would be cool if you created a new path for files where the hash can also retrieve them not just the nice short names
If you don't rug yourself are you even a nostr dev?
Starting today and for about a week by blossom server cdn.hzrd149.com is going to be down (rugged) which means all of the images I've posted so far will be broken... unless your using a client that is aware of blossom servers π
I just pushed an update to next.nostrudel.ninja so when it detects that an image failed to load and the image has the sha256 hash in the url it will start going down the users blossom server list to find the image
It works something like this
1. Image fails to load
2. Does image have a sha256 hash in the url?
3. Get other users blossom server list (using pubkey in kind 1)
4. Replace the image urls host with the next server on the list
The end result is that anyone using next.nostrudel.ninja will still be able to see my pictures because they are still hosted on cdn.satellite.earth and media-server.slidestr.net
I added a few helper methods to "blossom-client-sdk" for any other clients that want to use the users blossom server list to handle broken images https://github.com/hzrd149/blossom-client-sdk#handling-broken-images
Discussion
Not possible since account images are not deduplicated and one hash can reference and does reference multiple media files. Beto you ask for a reason, given that the storage is private, users may choose to have a duplicate posted in the note and then deleted from the public eye while a copy remains in the storage. So in short, not a good use case for account specific storage. πΆπΎπ«‘
no, the chances of a hash collision from different files is so small as to be practically zero
the hash does not reveal anything unless you know where to find it
and the short codes you already use are way more likely to have a collision than a full 32 byte, 64 character hexadecimal (or shorter bech32) - now, those hashes, yes, they can collide much more easily, but even still they are at least 48 bits by my estimation which is far far less than a full 32 byte, 256 bit hash
I am not sure if I said it clearly, but what I mean is that identical files do coexist in the same account. User uploads same image more than once.πΆπΎπ«‘
if you stored them by hash you could deduplicate them
also, if you mean "how do i have multiple filenames refer to one file" it's called a hard link
yes, in the case where you want the user to be able to change the different named files independently then you can't do this but if they are basically immutable then it doesn't matter