Hey, can you be more specific in your Facebook/Google greetings?

What’s a three-letter word for “I want to converse in real-time on a social network, and I will leave it to you to guess what about”?

Hey intro“Hey.”

Somehow, a message consisting only of that vague salutation has become a standard greeting from pals looking to kick off a conversation over Facebook messages or Google+ Hangouts. I wish that were not so.

As conversation-starters go, this is a nonstarter. It tells me nothing about what’s on your mind or the urgency of your request–unless typing it in lower case should be read as indicating a lower priority.

It’s also unoriginal. If you tried to grab my attention with the equally content-free “Ahoy,” at least I’d be thinking “ah, the salutation Alexander Graham Bell wanted us to use on the phone.”

Instead, why not just get to the point and state your question, compliment, complaint or humblebrag? You were going to do that in your next message anyway; why wait? Don’t let me hold you back!

That more direct practice seems to be how we–even those who “hey” me on Facebook or Google–have settled on using Twitter direct messages, like plain old text messaging before them.

At the same time, I have to recognize that these meaningless greetings come from friends who mean well, and that most lead to chats I appreciate. And things could be worse: I could have people trying to get my attention by saying “Yo.”

Advertisement

Reader suggestions for fixing an iMessage mess

Sunday’s USA Today Q&A about getting one’s mobile number untangled from Apple’s iMessage service looks to be one of the most-read columns I’ve done there. It’s also drawn more than the usual amount of reader feedback–including two reports of remedies that I had not discovered during the week or so I spent digging into this issue.

iPhone Messages settingsOne came from an AT&T subscriber in Minnesota:

A few days before the article I had the same problem and called AT&T.  They had me text the word ‘stop’ to 48369, to which I got the response: “FREE MSG: Apple iCloud ID Verification: You have been unsubscribed and will no longer receive messages. 1-800-275-2273”

I’ve since found one confirmation of that fix in a Reddit comment and a posting on Apple’s tech-support forum. There’s also an Apple tech support notice… which only describes this procedure as a way to stop Apple from sending AppleCare identity-verification messages to a wrong number.

A reader in Washington who said he works “at a major phone retailer” sent in a different suggestion that he said “always” works: Reset your Apple ID password.

Go to https://iforgot.apple.com/password/verify/appleid Enter your Apple ID in the space and just reset your Apple ID password. Even if you don’t have access to that email or security questions, it will remove all Apple registered devices from iMessage instantly.

In case you were wondering: Neither suggestion came up in the background conversations I had with Apple PR, even though one is allegedly endorsed by Apple support.
But that’s not nearly as important as whether either cure can earn an endorsement from you. If you’ve found either one successfully exfiltrated a number from iMessage–or if you have a different fix to share–please leave a comment with the details.