Looking for Vuze (aka Azureus) Feedback for Upcoming Meet With Developer

[Jared Moya]

Have a meeting with some of the people behind Vuze (formerly Azureus) and they are looking for some of my "ideas, comments,and suggestions" being that I write and work regularly about and with the BitTorrent client.

It's a chance for some of you to vent any frustrations and propose new ideas for them to consider.

THX in advance

Jared
You can also e-mail me > [email protected]

[Xtripit]

They should put the option to disable DHT/Distributed Database back. They removed it for some stupid reason and now the only way is to set Azureus to not load the plugins needed for it. Result is that the whole time I have Azureus/Vuse running, it says DHT initializing forever, instead of just being disabled. Just a guess, but it probably has a detrimental effect on performance as well as being annoying.

Tracker specific rules would be great. Like e.g. the option to concentrate all traffic on one tracker, even though other loaded torrents are more in need of peers.

[Potato]

Why do you need two threads for this?

[thelastfreeman]

They need to take the Vuze out and make it more like Az 2.5.0.4 instead of trying to fit a goddamn media center in it. The fact that it has been allowed to turn to bloatware made me switch to uTorrent.

[gost]

first problem. JAVA.

[kippies]

tell em to look at utorrent and do likewise....

Id agree ditch media centre jobbie-

Strip out the bloat and give us a client that works well instead of just getting by- I was a big AZ fan back in the day but migrated to Utorrent and any time I revisited AZ ive confirmed it was the right decision

In fact many of utorrents features are surplus too- what Id really like is the smallest possible memory footprint client with the ability to prioritize pieces and a peer ban for the bitlord freaks...

encryptions a must and why must the client allow the user to see the ip addy of a peer, just makes it easy for the MPAA etc- probably thats a tracker side issue as well

Couldnt they split the clients requests across several (or hundreds) of ports to side step port blocking?

[Xtripit]

yeah blocking specific clients would be nice too. Not really an issue on private trackers, but on the public ones it would be nice to be able to ban the likes of BitLord and BitComet etc. People that use these clients tend to be quite selfish and delete the torrent as soon as they get what they need.

If you look at what clients majority of the seeds use, it will be mainly Azureus, uTorrent and Transmission.