Oddbean new post about login | logout Torrent is the most decentralized, but is up to the people to host, making it not extremely reliable. nostr.build (like most other media hosts) is centralized, very reliable with backups, but if the FED knocks on our door saying we are hosting illegal content that needs to be removed, we’re likely removing it 🫡
Thank you.
pear and keet is a more modern form of torrent
How about something lije UUE encoded Nostr notes that embed the video binary content across hundreds of Nostr notes like it has been done on usenet newsgroups? There could be something like an NZB (Newzbin) file that points to all the notes, similar to how movies are shared across usenet. This could bring decentralized video and media to Nostr notes, and spread them across multiple relays. @Derek Ross @hodlbod @ODELL @Vitor Pamplona
It's been discussed, I personally think blossom is the best way to handle that
it's kinda silly also, we don't have the limitations from those times of mime/uuencode email attachments also, http can serve binary, and http can serve video just fine, the browsers all have preloading cache players built in now for several formats, mp4, vp8, etc
I didn't mean UUE encoding per say, but something that works decentralized like that upgraded for modern tech. I'll have to do a deep dive into blossom to see how that works.
blossom is definitely a better way to do it, it's simple to add naive propagation mechanisms like forwarding queries to other blossom servers that are storing the same type of data, and then caching them actually, after i get done with making an actually stable relay i need to write a blossom server
why not just use a p2p platform? clients can then load files via multiple servers at once, can use index and dht lookups, anyone can add servers
DHT does not scale well
scales fine just depends how you use it 'the concurrent number of users of Mainline DHT is from 16 million to 28 million' https://wikipedia.org/wiki/Mainline_DHT
SHA1 haha lol, man this tech is so old... i mean, it works but SHA1 is broken
also still used for git commit hashes... they really should do something about that
bittorrent is sha256 now
i would hope so!
but git is still SHA1
not really, there's a transition plan in place, and places like gitlab accept it already https://about.gitlab.com/blog/2023/08/28/sha256-support-in-gitaly/
its way too complicated to be distributing files via many notes, usenet is way obsolete, many p2p systems since replaced it, bittorrent is the most used and stable currently, pear is an evolution of bittorrent and could be used for all nostr content files and text, blossom is not even using a merkle hash
you can still have dedicated hosts for torrents, called seedboxes, deploying additional 'servers' is very easy in a p2p network, you dont need domains or relays
