GIS user technology news

News, Business, AI, Technology, IOS, Android, Google, Mobile, GIS, Crypto Currency, Economics

  • Advertising & Sponsored Posts
    • Advertising & Sponsored Posts
    • Submit Press
  • PRESS
    • Submit PR
    • Top Press
    • Business
    • Software
    • Hardware
    • UAV News
    • Mobile Technology
  • FEATURES
    • Around the Web
    • Social Media Features
    • EXPERTS & Guests
    • Tips
    • Infographics
  • Blog
  • Events
  • Shop
  • Tradepubs
  • CAREERS
You are here: Home / *FEATURES / THE EDITOR / Lessons in Location Privacy and Twitter – Sharing Who, Where, and When Gets creepy for baseball fans

Lessons in Location Privacy and Twitter – Sharing Who, Where, and When Gets creepy for baseball fans

July 25, 2013 By Editor

Would you post a tweet that read “I’m going to be at XXX place on 4th Ave.  in the corner table at 6:15 PM tonight”... I doubt you would, however, contests on Twitter are encouraging people to do exactly that!

Privacy and social media seem to be on the minds of many, however, for the most part, nobody really seems to care or really be going to any effort to protect their privacy – perhaps to many it simply isn’t a big concern. I suppose, privacy and safeguarding one’s privacy is just not that big of a deal, until something scary or creepy happens! It really is much like the old “backing up your data” issue where most of us admit that we really should be protecting ourselves and be regularly backing up that valuable data, however, how often do we really do it? Eventually, not backing up your data will bite you in the butt!

So where is the inspiration for this post coming from? Well, those of you who know or follow me are aware that I really like baseball and I’m also a Rockies fan. Recently I noticed a contest on Twitter being run by the @Rockies official account. The idea here is for fans that are planning on attending a game later on a particular day, they tweet their seat number and a special hashtag (#Roxpromo) for a chance to be selected to take part in special between inning activities and competitions. Obviously you can see where I’m going here.  A browse of the hashtag on Twitter (which is open to all) reveals a lengthy list of fans who have just made public the time and location of where they will be located in Coor’s Field. Think about it… kinda creepy isn’t it? Just another little privacy concern that  those who tweet should be aware of. What’s even more disturbing about this example is that many of the people tweeting for this are young fans – would you want your daughter sharing such information??

 

 

Filed Under: THE EDITOR Tagged With: and When Gets creepy for baseball fans, Experts, Glenn Letham, Lessons in Location Privacy and Twitter – Sharing Who, Where

Editor’s Picks

GIS and History: Using the Past to Inform the Present

Reading – Reduce Your Open Source Security Risk

HxGN LIVE 2015 – Great Stories Continue with the Hexagon Geosystems Track

Esri Helps Developers Add Geo to Apps at TechCrunch Disrupt NY 2016

See More Editor's Picks...

About Editor

Glenn is a geographer and a GIS professional with over 20 years experience in the industry. He's the co-founder of GISuser and several other technology web publications.

Recent Industry News

The Drift Between Early Notes and Final Case Files in Abuse-Related Legal Support

April 29, 2026 By GISuser

Aerial Surveys Int’l and Global Marketing Insights to Present GEOINT 2026 Workshop on Multi-Domain Geospatial Fusion for Automated Infrastructure Monitoring

April 24, 2026 By GISuser

Why Timing Matters More Than You Think With Spray Seal (And Why People Often Get It Slightly Wrong)

April 22, 2026 By GISuser

The Quiet Planning Stage Most People Don’t See When Building a Pool in Brisbane

April 22, 2026 By GISuser

Hot News

State of Data Science Report – AI and Open Source at Work

HERE and AWS Collaborate on New HERE AI Mapping Solutions

Virtual Surveyor Adds Productivity Tools to Mid-Level Smart Drone Surveying Software Plan

Categories

Copyright gletham Communications 2015 - 2026

Go to mobile version