I can't tell you how many times I have wanted to right-click on the results tab and see 'Search Again' as an option. Also, could you use a tooltip to show the search category for the tabs? That would be great to know what type of search each one was.

Enable CMD-C copy, CMD-V paste and CMD-A Sellect all. All are needed to keep track of "Upload Names" (on the Monitor Page) in order to create log and keep track of most popular uploads (mp3's etc).

I think there should be a feature to cut-off very slow uploads. often my limewire gets caught with six people uploading at .5k / sec or even 0; this reduces the number of slots for people that can actually get content from my machine quickly.

Slow uploaders don't necessarily waste upload slots. Check out the options in your tools->options->uploads window. LimeWire will initially give out "start upload slots" uploads. Then, as long as there's enough bandwidth, it will continue to give out uploads until it reaches "max upload slots". Be careful not to set "start upload slots" too small, our LimeWire won't be able to tell whether it's you or the downloader that's run out of bandwidth.

Thanks for the tip; my upload slots were a bit low. But i have another question: the people that are constantly uploading at 0 or .5 k/s get their file only after many hours; this is one of the complaints of new users that the gnutella network is slow. Most people usually download from another host if the connection is slow; many people don't. Wouldn't it be a good idea to prevent these slow connections in the first place to encourage people to download only from those who they have a fast connection to? For instance, right now there are two people trying to upload from me at 0 k/s; my concern is that these people will never get their file because they are stuck on my slow upload.

LimeWire tries hard to swarm downloads from multiple sources whenever possible. So one slow download doesn't mean the whole file will be downloaded slowly. Future versions of LimeWire will try even harder to find faster locations.

None of the features you presented. they are all needless in my opinion, except perhaps the remote queuing.

first: HUGE or any other hash-enabling protocol.

second: auto-resuming that actually works.

do you actually enable multisourcing for modem users by now? if not, than that is definitely number three.

Abaris: HUGE is actually one of our top priorities at the moment, and will likely be included in 2.3. (No promises!) "Browse host" is a really easy one, so that will probably be included as well. Remote queueing may or may not be delayed somewhat in response to some skepticism that it will actually help the user experience.

As for resuming: it really does work, if you try to download a file with the exact same name and size. But we understand that this this is not intuitive. In the future, we will likely add the ability to select incomplete files in the library, right-click, and have LW automatically resume, initiating new searches if needed.

Swarming is typically not effective for modem users because their downstream capacity is less than that of most uploaders. This causes modem users to tie up upload slots needlessly. Of course LimeWire has had dynamic upload slot allocations since 1.9, but there are still lots of older clients out there.

I would like to see items 2, 1, 3 implemented.
Thank you for your suppport.
LW221pro user

I like John Blackbelt Jones ideas about blocking hosts except for some subnets / backbones domains or IP.

Would be greate for eg university networks with speeds like 2,5 Gbit/s and 10 Gbit/s (sunet/nordunet), or for better crawling in northern Europe, and to get rid of all american modem users and theirs futile attempts to download iso-files.

/Mutatis mutandis