Diary of a Network Geek

The trials and tribulations of a Certified Novell Engineer who's been stranded in Houston, Texas.

2/29/2012

On-Line Dating Security

Filed under: Advice from your Uncle Jim,Bavarian Death Cake of Love,Geek Work,News and Current Events — Posted by the Network Geek during the Hour of the Horse which is around lunchtime or 12:39 pm for you boring, normal people.
The moon is Waning Gibbous

I’m pretty sure I was propositioned by a prostitute on Match.com this morning.

I could be wrong, of course, but when a 27-year-old woman who’s profile says she’s “almost divorced” and looking for people in the age range between 35 and 37 sends an email to a 43-year-old man (ie. me) asking if he’s interested in a “one-nighter”, it seems suspicious to me.  Maybe I’m just cynical.
She started off sending me a short note that was a little vague, but at least sounded like she might have possibly read my profile.  Well, except for the part where I was 43.  But, most people I bump into out in the world aren’t very detail oriented, so I gave her the benefit of the doubt and  suggested that I might be a little old for her.  I went on to explain that I wasn’t comfortable dating someone who hadn’t started school yet when I would have graduated from college.  What I didn’t say was that it would make me feel like a pervert to dating someone potentially young enough to be my daughter, but, that’s what I was trying to get at, in a polite way.  Then I wished her good luck in her search and went on my merry way.
This morning, I got a note back asking if I was interested in a “one-nighter”.  And, then she gave me an e-mail address at Hotmail.com.  That raised two, giant red flags for me.  First of all, while I am a wizard in the sack, there’s nothing about my Match.com profile that would indicate that to the casual observer.  And, frankly, while many women find me absolutely adorable, I think that’s more based on my personality and sense of humor than my rugged good looks.  It’s been years since I was pretty.
So, sure, maybe she’s just a messed up kid trying to work out her “daddy issues” and not a hooker, but I suspect that she’s looking for an entirely different kind of “daddy”.  Either way, I don’t need that particular flavor of drama at this point in my life.  Seriously.

But, oddly enough, earlier in the week, I was reading a security blog at TechRepublic by Michael Kassner.  The entry was titled “Online Dating Services Risking More Than a Broken Heart” and was all about the potential security issues related to on-line dating.  Now, I work in the industry and I maintain pretty decent security, even at home, but I know not everyone is quite as paranoid as I am.  And, that’s just within the IT industry!  I cannot imagine the wild and wooly dangers faced by people foolish enough, or desperate enough, to contact someone who seems to good to be true through their own, personal e-mail address!  Not to mention how much data you put up on a profile that may be active indefinitely on a dating site.
So, go read his article and think about what you put out there, where you put it and who might be reading it.

Oh, and one last bit of dating advice from your Uncle Jim, if she seems too good to be true, she probably is!


Advice from your Uncle Jim:
"Laughter is a tranquilizer with no side effects."
   --Arnold Glasgow

3 Comments

  1. It’s obviously not out of the realm of possibility, but I don’t think it was a prostitute or even someone trying to lure you into physical harm. In my experience, it’s probably just a rather benign email address harvester. Wherever there are desperate people (and I don’t just mean desperate for love and affection, or that you are among them) there are those who would prey on them.

    Comment by tinyhands — 2/29/2012 @ 3:47 pm

  2. PS: I got the following errors after posting the above comment, although it appears to have posted just fine…

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘SET comment_status = ‘closed’ WHERE post_date < '2012-01-01' AND post_status = '' at line 1]
    UPDATE SET comment_status = 'closed' WHERE post_date < '2012-01-01' AND post_status = 'publish'

    WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SET comment_status = 'closed' WHERE post_date < '2012-01-01' AND post_status = '' at line 1]
    UPDATE SET comment_status = 'closed' WHERE post_date < '2012-01-01' AND post_status = 'publish'

    Comment by tinyhands — 2/29/2012 @ 3:48 pm

  3. That error was probably generated because you were posting that comment as I was updating a post in the queue for Friday or next week.

    Oh, and that malcontent’s profile on Match.com was deactivated shortly after this got posted, but not due to anything I did. I didn’t report it, but someone else must have. Pretty sure from the responses, there was a person at the other end. They replied to specific questions or statements I made. Either that, or ‘bot programming technology has gotten pretty damn sophisticated in the past six months or so!

    Comment by the Network Geek — 2/29/2012 @ 3:53 pm

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.


Powered by WordPress
Any links to sites selling any reviewed item, including but not limited to Amazon, may be affiliate links which will pay me some tiny bit of money if used to purchase the item, but this site does no paid reviews and all opinions are my own.