nostr.build on Nostr: nostr.build needs to implement a hash based naming scheme to all files. This takes ...
nostr.build needs to implement a hash based naming scheme to all files.
This takes the unique hash of each file, Nantes the file that, and uses it to prevent multiple of the same image uploads and broken links.
The question for everyone is, I can implement a sha-256 hash which obviously aligns to Bitcoin, but has a huge file name, and will look bad in some viewers…
Or I can implement another hash, md5, sha1, etc. that would have a much shorter name….
(Sha-256 would be very good at preventing duplicate or incorrect files, and very Bitcoin cool, but loooooooong…)
ex. Sha256 names:
288fa930ec08fbb655872fccfdcf478f94ce127599942477d233f7e76f7ba9e2.jpeg
baf03e5d4d1b94bbc35b73657c82e373cc473c823973833e983fbd0795025f8f.jpeg
Thoughts?
This takes the unique hash of each file, Nantes the file that, and uses it to prevent multiple of the same image uploads and broken links.
The question for everyone is, I can implement a sha-256 hash which obviously aligns to Bitcoin, but has a huge file name, and will look bad in some viewers…
Or I can implement another hash, md5, sha1, etc. that would have a much shorter name….
(Sha-256 would be very good at preventing duplicate or incorrect files, and very Bitcoin cool, but loooooooong…)
ex. Sha256 names:
288fa930ec08fbb655872fccfdcf478f94ce127599942477d233f7e76f7ba9e2.jpeg
baf03e5d4d1b94bbc35b73657c82e373cc473c823973833e983fbd0795025f8f.jpeg
Thoughts?