Hello guys. I was just reading the topic about "Blocklist Download Issues" and I am curius. Why not make the the uploads in emule or torrent links? It sure would relief the server a lot wouldn't it?

Yeah I was thinking about trying torrents , the only problem would be getting people to stop sharing lists that are out of date or have errors in them.

In the current system we can fix / update the lists immediately via ftp if we need to..

Thanks for the suggestion though , if enough people are interested in doing that maybe we should try it , with a fixed expiry date on them or something..

I think it would be cool for people to see how many people are downloading the lists,

but, yeah I think we could run into alot of problems with files out there with ranges removed to suit the bad guys needs. This would have to be addressed. Right now, if we put them there, they are our files and that gives me alot of comfort, and should others as well, IMO.

firstaid

You could easily resolve this problem by making a torrent with all the lists. When you update one list even with minimal changes it would change the hash of it and it would solve the problem right?
Just make a note to people to update their lists once every 1-2 days and it would do the job.
The real problem will be with SafePeer at least until a new version is relleased and properly configured to be updated by the torrent system (at least for the novice users).
In the meanwhile why don't give it a try by adding a torrent link for 1-2 months?
By doing so you could see how it works if people are interested in using it and then deside if add it permanently or not!

I am a little curius myself

I didn't get what you mean. Could you explain it? You ment that by the normal download you could find bad guys and ban them permanently on the site and in the lists? If this si the chase then I totally agree

The files have to be peered to a single master controled by bluetack, no matter how it's implemented. If the torrent-engine were an intergrated function of proto and peer there wouldn't be any problem. It could just check a designated site to see if there's an update alert and then download the indicated file. The same way Azureus updates, basically. Torrenting the lists through a standard torrent system would be a very bad idea. The only viable way I can think of would be RSS-ed torrents that downloads to a fixed location on a users drive, and have the users peer-software config point to them.

Yeah also the more I think of it , the privacy issue of anyone being able to track who is downloading the lists through something like bittorrent bothers me. At the moment everything is very private and our users can only be monitored by us, if we need to ... I prefer it to stay that way.

At the moment our 2 new [ temporary ] list servers are doing a great job and we should have another list server up soon.

here are some ideas i was thinking of that may work.

1. use a free email server like yahoo and saving a message with the list as an attachment and modifying the client to log into your mail.yahoo.com account and download the attachment.

the problem i see with that is

1a someone wanting to do harm could login to your account and delete the message then no one gets the lists.

2. use the newsgroups most isps carry the newsgroups.

the only problems i see there is

2a. some isps outsource to premium services like giganews and there are bandwidth limits that can get used up thereby making the list updates not work.

3. get multiple servers and use a round robin selector system to distribute the load by each time the client connects it selects a different server in sequence.


4. modify the client so that it comes with the lists pre loaded and then the updates only contain the differences reducing the bandwidth to a few k insteas of several hundred k.

5. get sourceforge to host the files sourceforge has hundreds maybe thousands of mirrors all around the world to take up the load.

5a the problem there is they have anti bot scripts that cause delays however you may be able to arrange exceptions with sourceforge.

6. modify the client to update at the exact time when installed ( lets say at 6 pm eastern time i installed the client the computer's clock would be read and the time put into a buffer then each day or month or week or when ever at 6 pm the client updates) staggering the updates based on install time.