It's already possible to filter out certain words, but not for a specific search -- you set it up in Options to exclude stuff (e.g. if you're looking for porn, you probably want to filter out any results that claim to be "illegal", "preteen", etc. -- yuk) ... also, it's my understanding (and observation) that Gnutella queries do match on shared subdirectory names. If someone's sharing a file named shared/foo/bar.mp3, a search for "foo mp3" will generally turn it up. I think it also matches metadata sometimes -- title info in a file for example. I've had a jpeg with a bogus-looking alphanumeric code turn up as a search hit, which when downloaded proved to be relevant, and had metadata (e.g. camera model, date picture taken, title) containing the search term.

Maybe its time for a better rating system. Instead of scoring a file just based on speed (three stars, four stars, etc) include with it an ability for users to downgrade the score if they find out its a virus, spyware or just a bad copy. You could allow only one 'vote' per IP as to deter one person skewing the rating too much. This could possibly help people filter out bad files when used in conjunction with the minimum rating feature. You might also do this by host, but that could be more complicated.

Ya, I just discovered you can set up a general filter, but per search would be nice.

The big one is being able to set a max number of words per file, that really cuts out the spam.

The ipod spams have as many words in the file name as you used in your query -- no more, no less.

The very important is be able to share and download folders like in Direct Connect (DC++) because many files belongs together E.G. movie+subtitle, music cd, etc. Is this so big problem or is it due gnutella network disabilty?

These spammers are really annoying and ruin the network. I don't know how hard it would be to incorporate, but there are two features that woulf fix all this:

1) There should be a "<, <=, >, >= File Size Filter". This way if you are looking for a 1GB file, you don't get 300 search results for a 36.4Kb FREE IPOD file, because you would have the option to search for a file that is >= 800MB. Conversely, you could download that 5MB song and NOT download that 20MB.mp3 of Silence.

2) Secondly, we shouldn't have to block by host IP's. That can block GOOD users who have been victim of bad files. It also doesn't work, because for every one bad IP blocked there's 100 in line to pick up the slack. So the solution is that when search results come back and we KNOW it's a bogus file already (like those lame S_P_A_M files) we should just be able to block results for those exact files altogether. Right click on the result, and say BLOCK THIS FILE FOR THIS SEARCH. Limewire should just ignore any future results and move on to the real file that is out there.

Thank you for your work Limewire. I would purchase PRO if I had money and definitely would sell some blood if it had these features. Without these 2 features, spammers and the RIAA have ruined Limewire.

Kill, push & resume needs to come back! why they were taken away is beyond me.

they are still there, they were never removed..... you must seriously be having problems lmao.

Here's a strange one.

If a file finishes downloading, recent versions of limewire freeze for a bit; if you cancel a download, likewise. If you clear inactive or cancel a lot of downloads it completely locks up solid.

But if you go to the library tab, incompletes, and resume something (even a file already downloading) from there, this problem goes away for the rest of the session until you restart limewire -- if a file finishes downloading or you cancel a file it doesn't freeze, and if you cancel a bunch or clear inactive, it freezes for a short time instead of locking up.

So here's a feature request -- whatever changes when you resume from incompletes, make it happen automatically at startup. It shouldn't be too difficult -- it can just pretend the user flipped to the library tab, clicked the first item already in the downloads tab, and then hit resume and switched back, without of course actually visibly jumping around in the gui. This should remove those annoying freezes and hangs.

There was an unnecessary amount of locking that was going on. We've greatly improved / eliminated the freeze... you should notice the difference for the next update.

Thanks for the help!!