Reverse Enginer WinMx

[achilles]

Hans, thanks for the results on your survey! Did you receive a lot of private messages or did you post this survey on other sites as well? I was thinking that maybe if you had some ideals about features or improvements you would like to see in the new client then maybe you could talk it over with the development team, and offer some code that could be integrated into the new client. I think that would be a sure way to earn trust with the development team. That is if you have the time to spare. I know that may be asking for a lot but If I had your abilities then I would be willing to contribute in any way I could with the time I had to spare. I know you would be a hero in the eyes of many as would anyone else that has or is contributing their coding abilities towards this project. Anyways, I would like to say thank you to everyone that has been putting in many hours of hard work on this project! I hope someday I will be in a position that I can give back more to the community!

[Hans-Linux]

 

Hans, thanks for the results on your survey! Did you receive a lot of private messages or did you post this survey on other sites as well? I was thinking that maybe if you had some ideals about features or improvements you would like to see in the new client then maybe you could talk it over with the development team, and offer some code that could be integrated into the new client.

The survey was posted on this side and send to people who I know they are using WinMX. Most of the replies where by private e-mail.

The only improvements I can think of are:
1.) Making it impossible for the up and down loader to identify the IP or their counterpart.
2.) File size limit to be increased.
3.) Distributed File Directory that shows ALL files that are at present and where available during the past 60 days or so for download .
4.) Swarm downloading with the option to let a user specify the number of bytes or percentage first downloaded from the beginning of the file. (Like various bit-torrent clients do). 
4.) Prevention or warning regarding downloading of files already stored on the user's system.
I am currently working on an GPL licence open source MX specific version of my CLEANER Command Line Utility. This can be integrated into a GPL licence open source version of WinMX.

I don't use WinMx Chat and can't comment. I occasionally use Skype for Audio and Text Chat and file transfer.

Hans   

[Hans-Linux]

Hans, thanks for the results on your survey! Did you receive a lot of private messages or did you post this survey on other sites as well? I was thinking that maybe if you had some ideals about features or improvements you would like to see in the new client then maybe you could talk it over with the development team, and offer some code that could be integrated into the new client.

The survey was posted on this side and send to people who I know they are using WinMX. Most of the replies where by private e-mail.

The only improvements I can think of are:
1.) Making it impossible for the up and down loader to identify the IP or their counterpart.
2.) File size limit to be increased.
3.) Distributed File Directory that shows ALL files that are at present and where available during the past 60 days or so for download .
4.) Swarm downloading with the option to let a user specify the number of bytes or percentage first downloaded from the beginning of the file. (Like various bit-torrent clients do).
4.) Prevention or warning regarding downloading of files already stored on the user's system.
I am currently working on an GPL licence open source MX specific version of my CLEANER Command Line Utility. This can be integrated into a GPL licence open source version of WinMX.

I don't use WinMx Chat and can't comment. I occasionally use Skype for Audio and Text Chat and file transfer.

Hans   

[achilles]

The only improvements I can think of are:
1.) Making it impossible for the up and down loader to identify the IP or their counterpart.
Since there is a new client near completion I think the drastic protocol changes in the network in order to make this work would be too risky in it's current stage of development.  I would definitely like to see these capabilities added to the network when we have a solid foundation to build upon.

2.) File size limit to be increased.
I don't know what the primary protocols are going to be with the new client, but  I hope this will be feasible to do in the near future. This may be something you could start working on now if you coordinate with the developers. Then it could be implemented into the client when the timing is right.

3.) Distributed File Directory that shows ALL files that are at present and where available during the past 60 days or so for download .  Is this what the KAD or e-mule network uses? I'm not exactly sure how this works. Can this be done without centralized servers? I think it is extremely important that the network is a decentralized network. If the primary protocols are of a centralized nature then one point of attack could bring the entire network down. It would also encourage outside groups to pressure those in control of the network to shut her down.

4.) Swarm downloading with the option to let a user specify the number of bytes or percentage first downloaded from the beginning of the file. (Like various bit-torrent clients do).
This would definitely make downloading of large files much faster, and it would be a more efficient file transfer system than we currently use.  I believe it would mean drastic protocols changes to the network so i'm not sure when it would be feasible to implement this.

4.) Prevention or warning regarding downloading of files already stored on the user's system.
This is something else you may be able to assist the development team with. I hope to see this functionality added to the client soon.