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

Reply via email to