Editing Anti Nickthief
From EMule Wiki
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to cut-n-paste the text into a text file and save it for later.
The administrator who locked it offered this explanation: site maintenance
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | Some | + | Some leechers use NickThief - this feature takes the name (or parts of the name) of other clients and sends them back to use their community boost, if present at all (eMulePlus is a common example of a community mod). ''Anti nickthief'' detects this |
− | The | + | The whole Anti-NickThief feature is not about detecting clients with the same name but clients using a nickthief. Though it is annoying, this is not harmful in any way to have cleints that have the same nick. But clients using a nickthief will for 99% also use other [[bad feature]]s like a very low sessionupload, fakeranks or even no ratio/0 UL. That's why one probably wants to detect (and ban) them. the nickthief is very easy to detect. The AntiNickThief sends a random string to each user like "username <nowiki>[abcde]</nowiki>", if the user will adapt that string to his name and sends it back, we can (safely) ban him. |
− | + | Note that there is also an anti-anti-nickthief [[Bad feature]] that tries to detect this naming convention. There is no honor amongst thieves. Though, newer versions of the Anti-NickThief send 2 tags and/or tags of random length to make it as hard as possible to escape the ban. | |
− | + | [[category:features]][[Category:stullemulefeatures]] | |
− | + | ||
− | + |