Anti Nickthief - Revision history

Omeringen: Undo revision 2855 by 82.160.135.143 (Talk)

2010-06-05T07:03:33Z

Undo revision 2855 by 82.160.135.143 (Talk)

82.160.135.143: QWwsyFFUJDPLgUFz

2010-06-04T16:11:30Z

QWwsyFFUJDPLgUFz

Omeringen at 20:16, 6 May 2010

2010-05-06T20:16:22Z

Dick Manitoba: rewrite

2007-03-31T06:40:45Z

rewrite

Leuk he: new

2007-03-30T12:19:30Z

new

New page

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]]

← Older revision		Revision as of 07:03, 5 June 2010
Line 1:		Line 1:
−	~~phPRPI <~~a ~~href="http://jjphwgrzbblh~~.~~com/~~">~~jjphwgrzbblh~~</a>, ~~[url=http://fzchrvlsoicr~~.~~com/]fzchrvlsoicr~~[~~/url~~], ~~[link=http:~~/~~/sirijhnhutfu~~.~~com/]sirijhnhutfu~~[~~/link~~]~~, http~~:~~//kbtsatimltoe.com/~~	+	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.
		+
		+	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.
		+
		+	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-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:StulleMule features]]

@@ 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.
+phPRPI  <a href="http://jjphwgrzbblh.com/">jjphwgrzbblh</a>, [url=http://fzchrvlsoicr.com/]fzchrvlsoicr[/url], [link=http://sirijhnhutfu.com/]sirijhnhutfu[/link], http://kbtsatimltoe.com/
-−
-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.
-−
-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-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:StulleMule features]]

← Older revision		Revision as of 20:16, 6 May 2010
Line 7:		Line 7:
	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.		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]]