Hi Harold, Le 30.08.2010 à 20:40, Harold Feit a écrit : > It's technically mike's side that handles torrent generation currently, > not ooodev.org.
Thanks for the insight. > If you have an rsync folder that I can use to automatically load the > .torrent files from your side, it can be set up fairly trivially to have > the torrents authenticated on the depthstrike.com trackers within 2 > hours of generation automatically. [...] > It is currently not a good idea to accept all torrent infohashes without > discrimination, especially for this project. The load spikes are > potentially system crippling. Thanks for the insight. Is there another way of excluding illegitimate access? Like, allowing only torrents with certain names (instead of bt info hashes)? I assume the load spikes would be from illegitimate users, who try to use the trackers for some other stuff? Or how does it happen? Maybe I mentioned it before: there are no .torrent files that might be mirrored; the content served is generated in realtime from a database. The content does not primarily exist in torrent form on disk; torrents are just one thing that can be made of them. And I would like to avoid the overhead of writing torrent files for all files to disk, although that would certainly be possible. Would it help if you mirror the file tree itself? I can provide a script that does this without consuming bandwidth and disk space (Google knows it by its name "null-rsync"); you'd have a seemingly identical copy of the tree, just that the files would be filled with zeroes. Or the process that runs over the file tree and calculates the hashes (including the bt info hash) could issue a HTTP or XMLRPC request to your server to let it know about a btih to be included. That sounds easy, and it would mean that new info hashes end up in your tracker without major delay. Principally, you server could mirror .torrent files by downloading them via HTTP though. But that doesn't sound too attractive (albeit certainly okay for a small number of files. Thanks! Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
