Hello, I added http://torrents.doudoulinux.org/announce.php in web seeds tab of my current DDL torrents. We will see the result soon. I uploaded at least 15 gB of DDL img's via torrents already.
Cheers, Sergey -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, October 05, 2011 2:19 AM To: Sergey Komkov Cc: doudoulinux-dev Subject: Re: [Doudoulinux-dev] Torrent files to be tested Hello! Some news about our torrents. I found the server software we were needing: RivetTracker. It provides: * a public, authentication free, announce channel * blocking of non-registered torrents * authentication to register new torrents * mass upload of torrents * http seeds, which complements web seeds (*) * download stats, real-time It is already installed and running (on http://torrents.doudoulinux.org/), and I changed all our torrent files. As a result torrent announcing is much more faster and I saw this evening several Russian clients, leading to 12 CD's fully downloaded as of writing: this works well! I invite all of you to share your local DDL CD's using our announce channel: http://torrents.doudoulinux.org/announce.php If you've never started any DDL torrent, just click on the desired torrent file(s) in our torrent download section: http://download.doudoulinux.org/torrents/ Please activate DHT in your client configuration to share your torrent list with network neighbors. All the best, JM. (*) There are 2 official ways to allow a web server to participate into a torrent. The simplest one, that I introduced this week-end, is to let clients perform a standard download when no seed is available. It just requires the file URL to be written in the torrent file (web seed). The second one is to have a script on the server that can answer torrent requests passed using URL parameters. RivetTracker provides such script (http seeds). Not all Bittorrent client handle both, I even suspect Transmission to not handle any. ----- [email protected] a йcrit : > I'd like to add few explanations for people who would not know the > internals of Bittorrent. > > The standard functioning of the protocol is that clients announce on > servers the files they own and share. People looking for these files > have to connect to the same announce servers and ask for peers owning > the files. Of course if nobody has claimed to be sharing the files, > the peer list is empty and the demander will not receive anything. > Unfortunately there are many torrent sites with as many announce > channels, which decreases the probability to find the stuff. > > As you can see, we need to provide a reduced set of announce servers > in our torrents (torrent files specify the announce URL's) otherwise > people won't reach each other. The ideal situation would even be to > provide only one, but due to possible losses of service, a set of > servers is preferred. Then comes the second issue: public access. If > you provide a channel with restricted or private access, people will > have to register before being able to download, which may be annoying > and surely less easy than a standard download. In our torrents I > selected public channels, but they seem to be frequently overloaded. > This is why I think the best solution is to host our own announce > server in the end. > > JM. > > ----- [email protected] a йcrit : > > > It seems there are a lot of troubles with announce channels. I > tested > > 5 URL's and had 4 ones showing availability issues during the > > week-end! I wonder if we shouldn't rather host our own announce > > server. The main issue is to find a way setup a public channel (no > > authentication, no account) while avoiding people to divert its use, > > especially to share copyrighted contents. > > > > What do you mean by replacing your seeds? You're using alternative > > announce channels? If yes, do you have many downloaders? On > > openbittorrent.com there were few yesterday evening and this night. > > _______________________________________________ > Doudoulinux-dev mailing list > [email protected] > https://mail.gna.org/listinfo/doudoulinux-dev _______________________________________________ Doudoulinux-dev mailing list [email protected] https://mail.gna.org/listinfo/doudoulinux-dev _______________________________________________ Doudoulinux-dev mailing list [email protected] https://mail.gna.org/listinfo/doudoulinux-dev
