Skip to main content

Why Caller ID Blocking is Dumb

Does this sound familar? You are in the middle of a great movie. Your cellphone or landline rings. Your muscle memory kicks in, you glance at the screen to see who's calling, and observe the following:

"Private"

Quickly, you think to yourself, "My God, it could be anyone!" Your reaction to this paltry dilemma will most likely be:

A. "Wow, someone who doesn't want me to know their number. It could be important! I'll take the call."

B. "It could be a telemarketer, or someone I really don't want to talk to. I'll err on the side of caution and let it go. Besides, they can leave a voicemail, and if it's important, I'll call them back after the movie is over."

C. "There's a 'special place' in my heart for people who have the nerve to use caller ID blocking.... And it's not the one that encourages me to answer calls."

If you ask most people, the answer will NOT be A. If you choose to employ caller ID blocking on your outgoing phone calls, you should be aware that, in today's society, you are basically signing up for what amounts to "voluntary call blacklisting." Here's some of the things you can look forward to dealing with, in exchange for a supposed measure of added privacy:

  • Be prepared to, at least, go to voicemail a measurable percentage more often than everyone else. At most, you may just plain not be able to reach people.
  • Get used to writing down your phone number for your friends, as they will have to manually enter your number into their phones.
It's possible to make the argument that your circle of friends will know that it's you calling (since so few people choose to add this "feature" to their lines). However, the reality is that there is a chance someone else they receive calls from has a line with blocking, and unless you both happen to be that person's favorite callers, you can bet that they won't be answering your calls. A lot.

Comments

Peter said…
This comment has been removed by the author.
Peter said…
This dovetails nicely with a post on why I am very hard to reach on my own blog from a couple years back.

Popular posts from this blog

Reaper, Linux, and the Behringer X-Air - Complete Studio Solution, Part 1

Introduction and Rationale This is part one of a major effort to document my experiences with recreating my home studio, entirely using Linux.  Without getting into too many of the specifics, a few months ago I decided that I was unhappy with Windows' shenanigans - to the point that I was ready to make a serious attempt to leave it behind.  For most in this situation, the obvious choice is to switch to Mac OS.  With its proven track record, support, and options for multimedia production, it is naturally the first alternative to consider if your goal is to simply use something other than Windows. For me the choice was not so simple. I despise Mac OS and, in general, the goals and philosophies put forth by Apple in an effort to ostensibly provide users with an "easy" working environment.  It does not help that I have also failed to find any aspect of the Mac OS UI intuitive, but I realize that this is a subjective matter. With my IT background and user-control* favori

An Alternative Take on AI Doom and Gloom

 I've purposely held my tongue until now on commenting about "AI" (or, more specifically as has come to be known, GAN or Generative Adversarial Networks).  It seems like it is very in-style to complain about how it has made a real mess of things, it is displacing jobs, the product it creates lacks soul, it's going to get smart and kill us all, etc. etc.  But I'm not here to do any of that. Rather I am going to remind everyone of how amazing a phenomenon it is to watch a disruptive technology becoming democratized From the time of its (seeming) introduction to the public at large, around November of 2022, to late 2023, the growth and adoption rate has been nothing short of explosive. It features the fastest adoption rate of any new technology ever, by a broad margin.  To give a reference, the adoption rate for AI image and text generation, real-world uses, in just 12 months is comparable to all of that of the another disruptive technology, the World Wide Web, takin

RANT TIME: Why do replies to a message I sent go to my spam folder?

Despite what one would think/hope, sending a message to a given address does not inherently give Google a high confidence that a reply from this address is expected (and, for example, that it should bypass spam checks). I have confirmed with Google's tech support that there is no way to automatically have this happen. The user can do the following: 1. Add the address to your contacts list in Gmail. 2. Check spam folder for replies, and mark it as "not spam" if something ends up there, which should influence the fate of future replies received. I can also approve an address at the domain level, i.e. if it is a big vendor or similar. I've had to do this with several of our Chinese vendors. I regularly ask engineering and purchasing to give me a list of the supplies we deal with, so I can approve them as a preventative measure. For what it's worth, all of the false positive instances of reply -> spam we have experienced have involved the sender's email server