4 ms·
Keep it simple. Just post the SHA256 hash on the note and when publishing keep sending the file to some file hosting server (as done today). The file host wil
by nunobrito 3y ago
Keep it simple.
Just post the SHA256 hash on the note and when publishing keep sending the file to some file hosting server (as done today).
The file host will be gone one day, hopefully some other server will have the same hash.
SHA256 is not enough? Just use a tag like file:sha256:blablablabla and you now support better hashes in the future.
Nostr isn't about blockchain nor a crazy fear of losing data. It is intended for sharing notes that someone, somewhere might have interest to piece back together in a few centuries from now.
- jazzyjackson 3y agoWe have the same idea, a sha256 is all you need to construct a magnet link and start peering, my suggestion is for a nostr client to support this use case and webtorrent to replace the hash with the embedded file on the front end. not to make any change to the protocol.
- nunobrito 3y agoso long it remains as standardized hash. The problem with torrent hashes is that it remains specific to torrents. Most common scenario are volunteers setting up large storage space that indexes all files according to SHA256 where anyone can regenerate those hashes again easily if needed. Maybe time for a NIP on this topic?
- evbogue 3y agoI like the idea of simply hashlinking to a blob. Then, ask a random relay if they have it. If we don't want a global scope for blob sharing maybe the relay only responds if we are friends/members of the relay.