Google did not axe Google Voice today. Sunday’s USA Today column didn’t say it would—it covered Google’s scheduled shutdown, effective today, of a protocol that other Internet-calling apps had used to connect to Google Voice—but many of you thought it did.
My second: “Google, this is your own damn fault for neglecting the service for so long that people now expect the worst.”
My third reaction was a grudging acceptance that I should have foreseen readers skipping over my description of how Google Voice was shutting down the “XMPP” support that had allowed third-party VoIP clients to connect (admit it, you skimmed past that jargon just now) and instead seeing only the words “Google Voice” and “shutting down.”
That realization could have led me to write the column with fault-tolerance in mind: If there’s a way readers could get the wrong idea, throw in a “let me be clear” graf to disabuse them of that incorrect assumption. A little extra defensive writing then would have saved time since spent answering nervous reader e-mails and story comments.
I should know that by now, but apparently I’m still figuring out this writing thing after some 20 years of doing it for a living.
In other news: The Android Hangouts app still can’t place VoIP calls from your GV number (a capability the iOS version has had since October), officially leaving Android users in the lurch. Heck of a job, Google.