recommended reading

Google Tells Glass Users Not to Be 'Creepy or Rude'

Engineer Ian McKellar wears a pair of Google Glass at a booth at Google I/O 2013 in San Francisco.

Engineer Ian McKellar wears a pair of Google Glass at a booth at Google I/O 2013 in San Francisco. // Jeff Chiu/AP

So it has come to this: this week, Google posted some Dos and Don'ts for its wearable tech, Google Glass. The etiquette guidelines, and the fact that Google felt the need to make them explicit, highlight the ongoing debate around privacy and their technology.

The Dos start off simply enough: have fun with it, lock your device, be an active member of the pilot program. They also include the advice to "Ask for permission."

Ask for permission. Standing alone in the corner of a room staring at people while recording them through Glass is not going to win you any friends (see Don’ts #4). The Glass camera function is no different from a cell phone so behave as you would with your phone and ask permission before taking photos or videos of others.

That's a pretty good tip. It's admittedly not a rule that even people with cameraphones strictly adhere to, but with those it's pretty easy to tell when someone might be taking a picture. (Hint: they'll probably be holding their phone and pointing it at you or in your general direction.)

Google explained the privacy stuff further later in the guide, in the aforementioned Don'ts #4.

[Don't] Be creepy or rude (aka, a “Glasshole”). Respect others and if they have questions about Glass don’t get snappy. Be polite and explain what Glass does and remember, a quick demo can go a long way. In places where cell phone cameras aren’t allowed, the same rules will apply to Glass. If you’re asked to turn your phone off, turn Glass off as well. Breaking the rules or being rude will not get businesses excited about Glass and will ruin it for other Explorers.

Read more at The Wire

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats

JOIN THE DISCUSSION

Close [ x ] More from Nextgov
 
 

Thank you for subscribing to newsletters from Nextgov.com.
We think these reports might interest you:

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

    Download
  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

    Download
  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

    Download
  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

    Download
  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download

When you download a report, your information may be shared with the underwriters of that document.