Editing Anti Nickthief

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 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]]
@@ Line 1: / Line 1: @@
-Some leecher mods use NickThief, a feature that takes the name of the contacting client, or parts of the name, and sends it back to that client as it's own name in order to exploit it's community boost features, if any are present. eMulePlus is a common example of a community mod. ''Anti NickThief'' detects this behavior in other clients.
+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 purpose of Anti-NickThief is to discover clients using the NickThief feature, and not merely to determine if a client has the same name. Having two clients with the same name is not harmful, though it can be annoying. But a client using NickThief will in most cases employ other [[bad feature]]s against other clients, such as enforcing a very low sessionupload, fake ranks or even no ratio or 0 upload. That's why one probably wants to detect and ban them.
+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.
-Detection of NickThief is simple. AntiNickThief sends a random string to each user, such as "username <nowiki>[abcde]</nowiki>". If the contacted client will adapt that string to its name and send it back, it can safely presume that the client is employing NickThief.
+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.
-Note that there is also an Anti-AntiNickThief [[bad feature]] which attempts to detect clients using AntiNickThief (There is no honor amongst thieves!). Because of this, 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 bans it imposes.
+[[category:features]][[Category:stullemulefeatures]]
-[[Category:Features]][[Category:StulleMule features]]