As an alternative to that (and I think the compression alternative is very cool too) I'd consider a mathematical analysis of compiled information on visitor behavior between two suspected identities. Variables to analyze could include:
Technical
- Click trails
- Refering documents
- IP (of course)
- HTTP User Agent
- Times of visits
- email activity
- account preference settings
- passwords (you are the admin are you not)
Psycological
- topics of interest, forums/discussions of interest
- social interaction with similar cliques, without regard to positive or negative tone. (criminal returns to the scene of the crime...)
- takes the same kind of "flame bait"
- takes the same stance on clear cut political / moral issues (abortion, death penalty, trees, the trinity, birth control, etc.)
Just a few ideas among many. In situations such as yours, I couldn't justify throwing so much effort away on garbage like this troll, but I'd try to K.I.S.S. as much as possible. It's more fun to foil with less force. That's why Perl is so cool, and so endearing to the lazy punmiester who'd like to brag (hubris) about how easy it was to triumphantly trounce the troll.
--
Tommy Butler, a.k.a. TOMMY
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
