1. Double click file in upload window to play it
2. Right click menu in uploads window to block an IP so I can quickly stop the leeches that try to download dozens of files at once
3. Auto sorting of search results, maybe download and upload windows too
4. Search results, download and upload windows should all have complete customizing that is saved and restored after launching the program again, i.e. which columns are visible, column width, column position, and sort order.
5. Instead of scanning ALL my files EVERY time LimeWire is launched, which bogs down the CPU and thrashes the disk for far too long, store a database on the disk with the file path, file size, last modified time, checksum and bitrate for MP3 files. Then just compare the database to the files and only scan the files that have changed. This seems to be what the AudioGalaxy Satellite does, and it is very efficient.
6. Every time I launch LimeWire, I have to click the divider to hide the incoming searches window. It should save the position across launches.
7. Separate auto-clear settings for both successful and failed uploads.
8. Ability to refresh an individual directory in the library instead of scanning every shared directory.
9. The anti-freeloader preferencing feature that requires a minimum number of shared files doesn't seem to work. I set it to thousands and I still got tons of hits. I also want the slider to go down to Never instead of just Rarely (10%).
10. I want to be able to disable people being able to browse my shared files. Too often I see people cherry picking a *whole* bunch of my files.
11. A customizable filter with wildcards to eliminate IPs like 10.*, 192.168.*, 0.0.0.0 etc. from search results.
12. A comment field for the banned IPs in the filter hosts list so I can describe why an IP is banned.
13. Fix the number of connections setting so it honors the 6 that I tell it to connect to. It insists on always connecting to 3 at startup.
14. Minimum and maximum file size filters for search.
15. Better detection of a download that's dropped to 0 KB/s.
16. There's a bug sometimes when LimeWire unsuccessfully attempts to connect to someone for a long time and when I cancel it and try to start it again. It will incorrectly claim that I'm all ready downloading that file, even though I cancelled it and it's not in the download window anymore.
17. An anti-leech feature that automatically blocks an IP that tries to request more than a user-specified number of files in a user-specified length of time.
18. Option to automatically cancel uploads slower than X KB/s.
19. Since I upgrade to JRE 1.4, LimeWire will sometimes freeze when I close the preferences window and I have to terminate it.
20. A column that displays estimated time remaining for downloads and uploads.
21. A quick way to turn on and off sharing from the main window.

That's all I can think of for now. I apologize if any of these things have all ready been implemented in newer versions of LimeWire or even in older versions and I haven't noticed them.

I suppose #10 doesn't make too much sense if LimeWire can't currently browse someone's files. So I guess I have to request the file browsing option be added to LimeWire as well as the ability to disable someone else using it.

Another request I thought of is reverse DNS lookups on IP addresses. A domain name tells me a lot more about someone than an IP.

A couple other ideas include:

Showing the bitrate of MP3 files on the Library tab.

Using standard HTTP gzip encoding for search results or other traffic that could be compressed to save bandwidth. Web browsers send an "Accept-encoding: gzip" header to a server to tell it it's OK to send a compressed response. The server will optionally send a "Content-encoding: gzip" header in the response if the response is compressed.

The ability to edit the text string I've searched for if I typo something. I think my only option currently is to close the fscked up search tab and type it in again.

1. Playing incomplete files is not that simple. In many cases you have to wait, till the download is finished. However you can try right-click and choose 'launch', this works for mp3s for example.

2. How do you know people downloading from you are leechers? You can Options/Uploads/Slots/UploadsPerPerson to a lower value, if you like.

3. What's wrong with sorting as it is now?

4. Might be worth doing some time in the future. It's already possible for Search Results.

5. & 6. Could be done, I think.

7. Why?

8. No need to do that if 5. is implemented.

9. You can set it to never by setting the FREELOADER_ALLOWED value in your limewire.props to zero. However you should think of people who just downloaded LimeWire and don't have files to share yet.

10. Browsing files will be enabled again, soon. Why would you want to be so restrictive?

11. I don't think that's wise, 10.0.0.1 could be a firewalled host, for example, you could download from it, if you aren't firewalled, too.

12. You'd have to change the gnutella protocol to do that.

13. The number of ultrapeers to connect to isn't unlimited throughout the network. You'd take away too many incoming connection slots and cause more fragmentation which would reduce other people's search horizon.

14. You can sort files according to file size. But additional filters for search results is not a bad idea in general.

15. 0k doesn't mean an uploading host is dead. Maybe it's just uploading very, very slowly. But limewire would keep looking for further hosts to download from anyway.

16. I didn't have that problem anymore since LimeWire 2.3.1. I don't know whether it's still there.

17. Why? If a user is trying multiple files from you doesn't mean he's not sharing many files himself.

18. Better download with Xk per second than not at all.

19. That's Sun's fault, maybe it's fixed in JRE 1.4.1

20. That wouldn't be even near accurate anyway.

21. You mean an "I WANT TO FREELOAD"-button? Definitely not!

20.

1. This is for the UPLOAD window. These are my files that I have shared that people are downloading from me.
2. I call the people leeches who queue up all the files I have by an artist or even multiple artists. It ****** me off to see my upload window scrolling like crazy and I block them. I don't care how many files they have shared, they're greedy.
3. I'm using 2.2.0 and there's no dynamic sorting when search results are coming in.
7. I like to only see completed uploads and I don't care about failed ones most of the time.
9. I all ready edited the file to zero, but I shouldn't have to do that. I don't think this feature works anyway since I think 80-90% of people on the network are sharing few or no files, yet I get buried with more requests than I can handle.
10. I just don't like people snooping, especially RIAA, NetPD or Media Enforcer bots that might be cataloging file libraries.
11. Responses to push requests from firewalled people seem pretty rare for me.
12. The comment is only a description that's associated with the IP, for my info only. It's easy to store a description along with an IP in a config file.
13. In the edit box at the bottom of the Connection tab, I have it set to 6 connections. LimeWire always connects to 3 at startup unless I type 6 in the box again. This is a bug to me.
15. It bugs me when a download's zipping along and then suddenly hits a brick wall and stops for a long, long time. It sits for too long before trying someone else.
16. See response to #2
18. People uploading at near 0 KB/s are wasting an upload slot and I want to boot them. They're probably trying to download too many files at once.
19. I didn't know JRE 1.4.1 was out.
20. Mozilla and Netscape have time remaining and it's fairly accurate
21. I want to turn off sharing temporarily so I can let the remaining uploads finish without new ones coming in so I can shut down LimeWire. Currently, I block incoming connections with my firewall to do this.

FYI, here's a study that concludes:

"Specifically, we found that nearly 70% of Gnutella users share no files, and nearly 50% of all responses are returned by the top 1% of sharing hosts"

http://www.firstmonday.dk/issues/issue5_10/adar/

I'd like to see these measurements done again now. I'm betting it's not much different.

No you wouldn't.
Actually, I've noticed the bug he's talking about and it's a bug as far as I'm concerned also. After upgrading to 2.3.2 (and then to 2.3.3 later), it seems to have been fixed.
It does to me... if something is sitting at 0 Kbps for more than a minute, it's dead and should be eliminated automatically.
Agreed.
Personally, I'm not looking for accuracy.... just a ballpark number would do. And how do other clients do it if it's supposedly so innacurate?
First off, I think it would be a handy feature. Not everyone shares your views on freeloaders and I think it necessary for Gnutella client developers to accommodate both sides of the issue. I think every freeloader has to start somewhere. Besides that, I know I personally have a monthly bandwidth limitation (as I'm sure many others do as well)... I'll be the judge of how I'm willing to spend that bandwidth. If I can't afford to have an uploader using my bandwidth at a given time, I wouldn't mind an easy way to turn off sharing. I don't freeload if I don't have to, but there are times that I have to.

You can hide your upload window, if it bugs you...

The LimeWire Code is at limewire.org, it's a simple change. So you can customize your own version. I did it, too.

That feature works perfectly well, - it removes connections to hosts that share less a specified number of files. They are allowed to download from you, however, since a servent doesn't tell you how many files he's sharing when sending you a HTTP - GET.

They don't have to do that, they are seeing all the QueryReplies you send to the network. After a while they will know perfectly well, which files you have, without bothering to connect to you.

So what? Sometimes they do respond, and they usually are pretty fast.

Sorry, I thought you wanted the other host to see that description. This however is pretty useless in the age of dynamic IPs.

LimeWire keeps trying someone else until it's downloading from 4 hosts in case of a CABLE/DSL/T1 connection. If one download pauses, but isn't stopped, only modem users face the problem that LimeWire doesn't try new hosts.

The uploadslot isn't wasted since LimeWire can dynamically set the number of upload slots, that's why you should the number of MAX_UPLOADS to a high value (e.g. 20)

It isn't.

But they are usually downloading from servers which are quite stable. Gnutella clients however often stop uploads for no apparent reason, LimeWire constantly keeps looking for other hosts to download from, so there are to many unknown variables in a calculation of remaining time. It's useless eye-candy.

ShutdownAfterTransfers works, unless you click on that limewire icon in your systemtray again, since that would cancel the shutdown.

Dude... you suck. 'nuff said.

There's already a "Upload Slots per User" feature. Why is it a problem that someone finds multiple files from you that they want to download? Set max uploads per person to 1, and let them get whatever they can get.

You're coming across as a whiner who wants to be able to download everything that he wants, but not let anyone else get anything. Why is someone a leacher because they want to download more than one file from you?

If I'm downloading something from someone and get amazingly fast connection, I tend to try to download from them more. And if you're that jerk who kills my downloads for absolutely no reason, then I hate you. If you don't want to share (unlike the rest of us) than don't. But there's no need to come to an online forum to announce that you don't want to share.

Zed

I have max uploads set to 1 and people still insist on trying to download an entire album or multiple albums at once. The upload window scrolls endlessly with someone trying to grab many, many files. Not a pretty sight to me. It's a matter of courtesy. If you try to queue more than 2 files from me, I will block your IP. If you do it more than once, your IP will stay permanently blocked.

I am not someone who only wants to download. I have thousands of files shared because I'm a nice person who likes being generous. All 10 of my upload slots are almost always full. I have probably uploaded 10 or more times as many files as I've downloaded. My AudioGalaxy stats are sent: 19,542.09 MB / recv: 1,241.80 MB. You have no right to call me someone who doesn't want to share.

I just want more control to deal with people I consider greedy or lazy for not queuing up fewer files at a time.