Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Excellent question!
Unfortunately, as far as linguistic analysis goes, I can't offer any better solution to those above. However it would be possible to give his ISP two IP numbers along with timestamps and ask if they're the same person. You could explain the reason and point out that you're not asking who the person is, only if they're the same person. The might - they might not.

In order to stop it happening again (without going through the ISP), you could try the cookie idea .. but I'm not too sure it will work. If he really wanted to, he could find the cookie.

Instead, you might consider that if he is so desparate to be a part of the community, he'd should be willing to reform. Thus I'd suggest emailing him and letting him think you've done some sort of analysis and thus you "know" its him. Tell him why he was banned in the first place and that he's on a very short leash. If this annoys him to the point where he leaves, then is it any loss? If he re-offends then consider just banning his ISP. If he switches ISP just to get into your community, then let me know what your community is: coz I figure if it's that good, then I want to be in it too!


In reply to Re: Text Analysis Tools to compare Slinker and Stinker? by BigLug
in thread Text Analysis Tools to compare Slinker and Stinker? by Cody Pendant

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others learning in the Monastery: (4)
As of 2024-04-16 23:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found