On Phex you can BAN hosts, but most of these hosts don't know that they download (and share) fake-files!
I think it would be better to BAN (SHA1 code of) fake-files, see this image (i was searching for 'thisfileisveryfakeohyeah':



Just search for ANY name, even names that don't excist... you will see alot of fake-files, and even more hosts.

You can BAN hosts, but the fake-files will still appear in your search-results from other hosts... you can BAN fake-files (SHA1 code) and then these files will not appear anymore in your search-results, no matter how many hosts are sharing these fake-files!

Banning fake-files will be more efficient then banning hosts if you ask me... but i'm not an expert so maybe i'm completely wrong...

__________________

Phex - The best Gnutella client!

I'd guess it would too; great suggestion. Since spammers can change ip addresses frequently. Eventually some innocent good gnutella sharers may be blocked via your ban list if ip's are banned.

How do we ban the specific SHA1 file code?

Well unfortunately banning SHA1 is not as comfortable as banning hosts. But you can build yourself a search file rule like this:

When receiving search results
with 'urn:sha1:ABC...' or 'urn:sha1:XYZ...' as file urns

Choose one of:
ban their source (for 7 days)
delete them
hide them

And enable the rule permanently.

When you find a new SHA1 you need to add it manually.


I know this is not the ideal solution... but its the only think I can offer right now.
To help a little the search table supports row based Copy&Paste by shortcut keys. On Windows CTRL-C. Just copy the line, paste it into some editor and extract the SHA1.

Hope that helps at least a little....

__________________

I second this request! This feature would be the cherry on top of the whipped cream! I do the manual procedure but if there were only one button that did the same thing that would speed up the process by the speed of light //jofan

The hash of files banning is already starting to be introduced into gnutella apps. Time for Phex to add the 'known' such files to their filters.

Filtering out _ .snd __ .au __ .wma _ are a start for anyone to limit a large number of spam files. Also Direct instructions to eliminate porn & other marketing junk from results which applies to all gnutella programs.

the hashes change every time you make a new search.. the sha1 hashes used one week will be different in the week to come. I know bitzi are trying their best to keep up with the flooding of spam and fake files but I think it's a lost cause. Perhaps 1 out of 8 files I look up in their library are known - the rest are new but the file is still shared by 54 different peers. Still this function would be gold! //jofan

Would it be possible to add a default system-junk filter which gets updated when people click on a "ban file" or "mark as spam" button?

It would mean to automate the process for adding a sha1 to a rule.

__________________

-> put this banner into your own signature! <-
--
Erst im Spiel lebt der Mensch.
Nur ludantaj homoj vivas.
GnuFU.net - Gnutella For Users
Draketo.de - Shortstories, Poems, Music and strange Ideas.

You would need to establish a trust concept to do this. You cant just accept every added sha1 from anyone.

__________________

It feel better if it was kept local and personal. We have the junk file problem because "others" are not trustworthy...

//jofan

I don't mean a networked junk list, but just a filter rule like the ones we already have. It would only be a convenience function which adapts the filter rule.

Currently we'd have to open the rules wizard, select the rule, add a sha1 and save.

To make that easier, there could be a button which does these steps in one click, using a default rule.

__________________

-> put this banner into your own signature! <-
--
Erst im Spiel lebt der Mensch.
Nur ludantaj homoj vivas.
GnuFU.net - Gnutella For Users
Draketo.de - Shortstories, Poems, Music and strange Ideas.