(Continued from page 1)

• Typos on the menu. They send the wrong message.

• Dirty glasses and silverware.

• No partial-group seating. Customers can’t understand why you won’t seat them until all members of the party have arrived.

• Wordy menus. Foodies aside, many customers think they’re given way too much information about ingredients and preparation methods.

• Weak drinks. Even in the age of mixology and craft cocktails a lot of customers apparently just want a stiff drink.

• “Can I get...?” Customers don’t like having to request items they’re used to seeing on tabletops. They cite silverware, napkins, salt and pepper shakers, bread and water.

But while we’re listing complaints about dining room behavior, let’s look at one that’s brand new: customers who wear Google Glass. Not only do the tech elite who own these wearable computers make their fellow diners uneasy, in part because of the device’s creepy live streaming capability.

They also offend restaurant operators. The latest Google Glass incident took place last month at New York City restaurant Feast. When the restaurant’s manager asked a Glass-wearing customer to please take off the device while eating due to privacy concerns of other patrons, the customer said “no” and left. A nasty online review soon followed—fair enough—immediately followed by 13 additional equally nasty one-star reviews from alleged patrons whom management thinks have never been in the restaurant.

There have been similar incidents elsewhere. 

The message to operators: if you value your restaurant’s online reputation, don’t cross a member of the Google Glass community. Many restaurants already have no-cell-phone policies in place—perhaps not enough, according to Urbanspoon’s list of dining room pet peeves. Your customers may thank you if your restaurant has a Google Glass ban in place—as some already do—before the devices become more widespread.

On the other hand, at least one chef, L.A.’s Kogi BBQ Taco Truck founder Roy Choi, has embraced Google Glass. He explains the upside here: