Sorry for that! Basic is: it’s fully decentralized, and when anyone starts sharing a file, it joins a unique swarm of seeders. Whereas on Bittorrent, there is one swarm for each torrent, each private tracker for the same file, and also for folders (TV episode; TV season; TV series); this is called “swarm fragmentation” and leads to low speed and dead torrents.
For now it’s only scene releases, so there’s no duplicate (not sure if this is what you mean).
Hi, not sure I get your point. A release has a fixed name and resolution. Regarding genre classification, I estimated if was too complex to determine reliably. And I wanted to avoid storing metadata.
Dates folders are there to reduce directory sizes, similarly to a merkle tree with only one level. This is due to performance limitations with large directories in most filesystems and also in Git. Also it still allows for easy manual search (only the date is required).
Note: there can still be several releases for a single movie (several resolutions and sources, LIMITED/REPACK etc).
I don’t think it would scale for many millions of files.
Hi, yes it definitely sounds similar for the media files database side. Using a DHT crawler, you can identify new torrents matching specific file tree roots (so only works for bittorrent v2, which is not used so much for now), and update swarms statistics (S/L).
First time I hear of it. They say this is for private networking only. Also it’s only a network stack for now (the “BlockStore” storage component is not yet defined). So apparently it’s not for public filesharing. They compare it to Tor but it looks more like an overlay mesh network at first sight.