tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Tuesday, 2 March 2010

Don't Let Social Media Get You Robbed (or Stalked)

Posted on 05:42 by Unknown

If you are one of the millions of people using social media to report where you are, you may have been tuned in to all the buzz lately about the site Please Rob Me. The concept is very simple, when you use applications like Gowalla, Foursquare, Brighkite, Loopt or anything else that broadcasts your location, you run the risk of telling the world that you aren't at home and it's ripe for the picking. You can compound it by advertising to potential stalkers (not much of an issue for me, but certainly if you're popular).

The geolocation features built into these applications not only tell people where you are, but if they have any familiarity with you, the area, or just spend a few minutes reading your history, they can pretty quickly posit for how long you will be away. This isn't limited to just geolocation-broadcasting services — you can just as easily use Twitter or Facebook (among others) to inadvertently tell people you are away from home or at a particular place.

That it took all the press around the Please Rob Me site to cause people to consider this is almost laughable. Granted, the site is pretty overt in how it conveniently aggregates all the data for visitors, but it's not doing anything that an interested party couldn't do on his or her own in a few minutes. All the site does is show all the Tweets from Foursquare users as they check in — not very complex. To quote from its Why page:

The danger is publicly telling people where you are. This is because it leaves one place you're definitely not... home. So here we are; on one end we're leaving lights on when we're going on a holiday, and on the other we're telling everybody on the internet we're not home.

So how can you enjoy social media with geolocation features and still minimize your risk?

Techniques for Safe Check-ins

These are just three options. I employ each of these and find them fairly easy to follow. None of these will stop the old fashioned thief (who doesn't use social media), but they can make it a little harder for those casing you online.

Time Shift

Remember, you don't have to check in to a location as soon as you get there.

Let that sink in for a moment. I see people check in to locations as soon as they walk in the door, but they don't need to. Sure, you may not get the immediate benefit of knowing which of your friends might be nearby, but maybe you should sort that out in advance.

For example, I am known among my friends for posting photos of my meals through Brightkite. What many of them don't realize is that I often check in to a location after I have already left or (if it's near my house) as I am leaving. This has caused a couple awkward moments when a nearby friend is notified of my proximity and comes looking for me.

Hide Your Check-ins

Hide your check-ins from all but your trusted friends. And I don't mean those Facebook friends who you met once while in a mosh pit or that you haven't seen since second grade.

You don't need to Tweet to the entire world where you are. Sure, if it's a major event and you want to brag then go for it, but understand the risk. If you Tweet or check in for every morning visit to the local coffee hut, not only will people know where you are right now, you will be telling them where you are tomorrow or next week. Establishing a pattern of behavior makes it easy for someone to predict your moves.

Consider hiding your Foursquare check-ins and not Tweeting every one; you can still participate in the overall game. Lock down your Facebook profile from the general public. Consider disabling the geotagging from third-party applications that feed to Twitter.

Get a House Sitter

Some of you may be aware that I was just in Houston speaking at a conference. I was more than happy to post my progress via Foursquare check-ins, Brightkite photos, and an assault of Tweets. Anybody could have wandered over to my house for some pillaging, but would have been surprised to find that someone was already there. In fact, I was able to split the duties across two people, so it was better populated than when I am in town.

If you have the luxury of a roommate, house sitter, guard dog, militia, etc., then you may be in good shape already. But consider whether that person at your house is someone you want to put at risk (granted a rather remote risk), or if that person is comfortable with being on watch.

Related articles:

Continue to read up, you may come up with some ideas that work better for you than my suggestions.

  • The dark side of geo: PleaseRobMe.com at CNET.
  • Are We All Asking to Be Robbed? at Mashable.
  • Google Buzz: Privacy nightmare at CNET.
  • Facebook Privacy Complaint Ignites War of Words at PCWorld.
  • Twitter Your Way to Getting Robbed at Mashable.
  • HOW TO: Make Your Small Business Geolocation-Ready at Mashable.
  • How Robbers Did Their Dirty Deeds Before Foursquare at Mashable.
  • Friday Poll: Do Location Check-In Services Freak You Out? at Mashable.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in Brightkite, Facebook, Foursquare, geolocation, privacy, rant, social media, Twitter | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Social Media Day 2011 in Buffalo #smdayBUF
    Last night marked the second Mashable-sponsored Social Media Day here in Buffalo. With 154 RSVPs for the event, the venue, The Eights Bist...
  • Web Accessibility Sorta-Infographic
    WebAIM is a non-profit organization within the Center for Persons with Disabilities at Utah State University. It has a reputation (perhaps o...
  • Now the Mobile Web Is Dead?
    It was barely two years ago that I scoffed when Wired declared the web dead ( Enough about the Death of the Web ). Fast forward to today and...
  • Browser Performance Chart
    Jacob Gube has posted a handy chart over at Six Revisions titled " Performance Comparison of Major Web Browsers ." He tests the c...
  • Facebook, HTML5, and Mis-Reporting
    My Twitter stream and the headlines of sites across the web yesterday lit up with Facebook's CEO blaming its stock price (failure to mee...
  • The Science of Trust in Social Media
    I am one of those people who always needs to see proof of some assertion, evidence to back up a claim. While I can accept anecdotal evidence...
  • ICANN Moves .org Away from VeriSign
    This Saturday, the .org top-level domain (TLD) will no longer be privately managed. With VeriSign's contract with ICANN for management ...
  • Speaking at Mom 2.0 in Houston, TX
    I will be in Houston this week to speak at the Mom 2.0 Summit (Feb. 18-20, 2010, Houston, TX). To make it a little easier to describe, here...
  • Algonquin Studios Gets Local Press
    I'm taking an opportunity to brag a little about my company, Algonquin Studios , being featured today in the Business section of our lo...
  • App Store Meta Tags
    Why yes, Dominos, I'd love to tap again to get your real home page to order a pizza when I could have done it right here, below your ove...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ►  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ►  June (7)
    • ►  May (7)
    • ►  April (8)
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ▼  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ►  July (11)
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ▼  March (10)
      • Mozilla to Modify How CSS :visited Works
      • Google to Let Users Opt Out of Analytics Tracking
      • More Social Media Privacy News
      • Bar Codes as Web Portals
      • FourWhere: The Spawn of Google Maps and Foursquare
      • "Real World Hyperlinks" Article at evolt.org
      • YouTube Opens Auto-Captioning to All
      • W3C Releases 7 HTML-related Documents
      • RIP IE6 (Not Really, But Here's to Hoping)
      • Don't Let Social Media Get You Robbed (or Stalked)
    • ►  February (5)
    • ►  January (11)
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile