What feature would YOU like?
 

What features would you like to see in upcoming versions of LimeWire? We're already making good progress on the automatic re-query feature and on better integrating metadata into the result view. (So you can see bitrates next to speeds, etc.) Here are some new ideas:

1. LimeWire used to display an estimate of the number of searchable hosts, as well as the number and total size of searchable files. With protocol changes, this has become harder to do accurately. Leaf nodes are totally incapable of estimating the horizon. This could change if we introduced a new protocol message.

2. LimeWire used to have a feature to browse the contents of another user's computer. So if you liked a search result, you could see other files being shared by that user. We took it out many versions ago because it didn't work right. But we could re-implement properly it with some effort.

3. If a host has no more upload slots, it could queue people requesting the file and service transfers in a fair manner. The host could even give you an estimate of the amount of time until you can download the file. ("There are 3 people ahead of you, with an estimated wait time of 92 minutes.")

4. LimeWire allows you to sort search results by name, size, etc., but it does not do this dynamically. That is, if you sort by name, results added afterwards are not sorted. Dynamic result sorting would be particularly useful for making high-quality search results "float" to the top of the result list.

5. The library could visually organize your shared files by metadata such as file type, artist, genre, etc. Most likely it would show a number of "virtual directories" to do this.

6. LimeWire already has an integrated MP3 player. We could make it play videos and other audio format as well. We could also increase the performance of the player substantially or add other features.

Of course we'd like to implement them all of these features, but we have limited resources. So vote for your favorite and we'll try to implement the most popular ones.

Remote queueing definitely is the best thing to implement right now, since this could give you an idea how long you'd have to wait for popular files (mainly divx-movies).

The LimeWire-mp3-player is not exactly what I would call useful (it does not reach the quality for winamp or xmms, somehow I've always got some 'blips' more than with those two). And I'd rather want to choose the mediaplayers to use myself and save them in some config-file or so....

BTW. will LimeWire implement the HUGE-Proposal? And when will it do so? When you could search for a hash automated researching could be implemented easily, could it not?

PS: I like v2.1.1 a lot. How about a LAN-Version of LimeWire with the ability to block all IPs except for just a subnet or two? We have something like a traffic limit for outside traffic, so you wouldn't have to configure the firewall to connect to a local gnutella network and some clients, which allow outside traffic could as well be connect to the local and the global gnutella network. - It'd make things easier for people running gnutella in some companies (which they certainly shouldn't - but anyway, nobody cares if not too much outside traffic is generated) or campus networks (at least here in Germany).

I think it could work, if you'd allow wild chars (* or so) in the limewire.props file for the Blacklisted-IPs-option, although it would be even easier if you'd add an IPs-allow-option, where you could enter all IPs to be allowed. But that's just my personal wishlist (and I have to admit I am to lazy to do those changes to the LW - Source myself)

Anyway you're doing a great job! Keep on doing what you're doing.

Chris, 3, 1 and 4 in that order. Of course you can already do number 4 by double-clicking the titlebar of the Host column. But that would be great for lazy people. 3 would be cool, but even better is to actually implement "resuming incomplete downloads". 1 is cool to look at.....

Blackbelt Jones: You can have your own local gnutella network. In previous versions of LimeWire they let you edit the conenction string. You can just run another LimeWire using port whatever, force yourself to be an ultrapeer and change the connection string in your limewire.props file to whatever you want to use. But you must remember other clients that wanna connect to you must also have that same connection string. If you edit the connection string, LimeWire shouldnt be able to make connection to the public gnutella netowork.

Yes, but I want some clients to be able to connect to the local and the global network at the same time.

Thanks everyone for the feedback. Keep voting....err...if you haven't done so already.

John: changing the connect string to make private communities doesn't work in LimeWire 1.8 and later, since they use the "Gnutella 0.6" handshaking protocol. However, the bleeding edge code in our CVS repository has some simple authentication code that could be used for this. If you're interested in getting your hands dirty, contact me personally and I'll give you some more info.

Also HUGE is temporarily stalled on the GDF pending the GGEP proposal ("Generic Gnutella Extension Protocol"). Yeah, we'll probably implement whatever is passed.

-Christopher Rohrs

I have a simple request :
An option to disable the built-in MP3 player is already present .
Now I would like to be able to get it of my screen if I want to .
Make an option in the config-menu to hide the player .

Even if you disable the player it still scrolls that stupid line of text .
It makes my LW GUI unresponsive and draws too much CPU power .

heh, no it doesnt.

Yes it does . :D

about 3, what if the host is using another client?

can an auto-retry option be added for these cases?

personally,,I'd like to see a way to save our favortie host so we can try them first when we log on,,alos I like numbers 1,3,4,5,,and I don't use your mp3 player and I doub't if I'd use the movie player eather,,if it affects anything,,eather way,,I love your product and hope to continue useing and enjoying it for years to come;)