Actually no, that is clearly not what he's saying with that sentence, it's what you're intoning from his subsequent comments and knowing him to be a person with a tenuous grasp of the English language.
And yes, I obviously know what he's trying vainly to say, but that's not what I'm talking about. Maybe I'm making my point too bluntly here, but I read Rick on Twitter daily... and let's just leave it at that.
Well there's the problem, you care too much what Rick or anyone else has to say. Rick often has valid points specific to his type of portfolio. But there are different ways to make money from domains and everyone has to decide for themselves what works for them, their lifestyle, their abilities, the amount of effort they want to put in, their level of paranoia, their TLDs, even the specific types/categories of domains should influence what you do with them.
What really bugs me about this type of conversation is that everyone seems to be looking for the "magic secret" to selling domains, constantly asking "which lander is best?", "what marketplace should I list on?", "should I use BIN, Make Offer or Request Price?" etc., etc. and it's all BS - there is no secret, just buy what you think are good names and if someone really wants to buy, they will beat a path to your door. If not, then all the wasted time & effort in the world won't sell crap.
Of course not, there is no one magic secret, I know you know that so don't let it bug you what Rick or anyone else is preaching. Rick preaches what works for him, and that's it, he only has his perspective. I wouldn't want there to be one magic secret anyways because then it'd be too easy for anyone else.
Plus, there are huge risks for posting personal WHOIS data for the world to see, especially if you don't have a ironclad business to hide behind. The first second you go public, you will be attacked by 3rd World scammers, who will call your phone incessantly, fill your email box up to the brim, and use any address, name or phone info to try and social engineer virtually all bank, crypto and payment services. hoping to hit one you use.
When was the last time you heard of a .ca that actually got hijacked? Call me foolish for public whois, but I'm not concerned. With thousands of domains in public whois I have no more problems with spam on that email account than on any other email account. I've always just presumed that people use the spam argument as a cover for their real motivations, to hide from CRA, an ex-wife, a business partner they screwed over, dog the bounty hunter or whatever boogeyman is out to get them.
As for the phone # in whois, I use a $35/yr magic jack number. My home # gets a spam call every day, if not multiple. My magic jack number never gets a spam call, despite being published in whois. It does get the occasional buyer to call though. I never answer it, it goes to voicemail and I get the voicemail as an email attachment - which is nice.
So the spam argument is entirely baloney in my experience. So what really bugs me is when people use that as their privacy argument. They should just say the real answer is "I'm hiding from <insert here> and that's why I don't like public whois".
The only valid whois privacy argument for me personally is the one about hiding my domain investment & acquisition strategies. So it has become a small compromise for me to start with privacy for TBR purchases, then switch over to my primary company profile when I consolidate the domains to my main registrar.
I believe Richard has perviously said there were none that he knew of, but just for the record,
@richard.schreier - how often has CIRA been aware of or was asked to intervene in a .CA hijacking case? Does CIRA have any policy regarding what CIRA would do in the event of a hijacking case? What course of action would CIRA recommend to the disputed owners?
Naturally these scammers will also try to use any personal info to steal your domains (it's easy to run a WHOIS report), so be very careful with what personal data you share with everyone, as these 3rd Worlders are voracious and will hit all the popular service providers 24/7 hoping to hit a bullseye.
And they just need to find one dumb company rep to win.
And let's not get into the UDRP/CDRP ramifications, as I've read lots of rulings where the Complainant gained favor by displaying WHOIS reports based on the Respondent's publicly-available WHOIS personal info showing that "this domain squatter owns thousands of domains, therefore we win!". And a lot of panelists use this spurious data as "clear evidence" of squatting.
I've found panelists to be fairly logical, and when you don't respond, that's when I've seen some stretch by panelists being made. So if you don't defend yourself, that's your own fault. But if you respond semi-intelligently, panelists are pretty good at seeing through the hyperbole used by complainants. And your pattern of registrations can help you too, you set the pattern and you can use it to defend yourself. I don't see you infringing with blatant TM domains so you really shouldn't be so worried about it. Any decent one-word domains are pretty much guaranteed to have multiple trademarks existing, but without actual infringement, it is meaningless. And I promise you, having public whois means they need to contact you first, and it is ALWAYS better to have that discussion with them prior to CDRP. I promise you, that alone is worth any other perceived hassle of public whois. If they think you're some rando with a domain, they may think they can get away with a quick an easy CDRP. But if they realize you know what your doing, they are going to be much less willing to just wing it.
Little side story: I once had a 1-word dictionary .ca which was also a major shoe brand. They caught me with PPC ads on it, which was mostly inadvertent and stupid on my part. But I owned the mistake, said they were right, and I simply gave them the domain. There's no better lesson than learning the hard way... And I'd rather own my mistake privately than to have it enshrined in CDRP. As mentioned, it is probably the best reason of all to have public whois.