The Elephant in the Room--Chef Patrick and Oversee Breach of Customer Info

[Ms Domainer]

*

I never know with this site

http://domaingang.com/editorial/there-will-be-no-post-about-chef-patrick/​

what's real or fake, but another site also confirms this.

If true, sad day, indeed.

Either way, because it's out there, Chef Patrick needs to address this issue ASAP to either clear his name or apologize.


*

 

[Tippy]

A company has a Duty of Care to it's Clients
An employee has a Duty of Care to it's employer and the employers clients.

Cheers
Corey

Right, and the employee failed thus the company was not able to protect its clients.

 

[Dave_Z]

I've seen Patrick in this thread yesterday. I was hoping he'd leave a post but he didn't.

It's nice if he posts here about it, but...he doesn't really have to. Then again, he already blogged everything he needed and wanted to say.

thus the company was not able to protect its clients.

Only those directly affected by the breach, though I don't blame people for no longer trusting Moniker after finding out what happened. Though Moniker doesn't really have to either, making a public statement and outlining what steps moving forward might...might...help them.

I say might because, rather unfortunately, it's hard to tell if that will make any difference in convincing people not to go whether they do that or not. Not unless some other company did that and has demonstrable results to show, perhaps.

In my ex-registrar life years ago, first-level employees are easily able to see a domain's actual details despite using the WHOIS privacy. They mainly access that to verify who they're communicating with over the phone, ticket or email prior to accommodating them for whatever request.

It was made clear that information is not to be abused for personal gain or shared to third parties for any reason, save for legalities handled by a specific group. Of course, consequences were outlined if ever they're breached.

 

[DU]

In my ex-registrar life years ago, first-level employees are easily able to see a domain's actual details despite using the WHOIS privacy. They mainly access that to verify who they're communicating with over the phone, ticket or email prior to accommodating them for whatever request.

I've been hard on Moniker for allowing access to information under privacy. The reality is that I imagine almost every registrar would fail on the same grounds if it came to looking at how they managed privacy information. I hadn't really thought about it much from a data management perspective.

Why? Because registrars are in the business of managing domains and associating it with an account. The support teams are usually working within both realms. People buy a domain and associate it with a real account that contains their personal information. Then, AFTER defining that relationship, they apply a thin veil of privacy to the external world by changing the whois entry.

There is no technical reason that anyone at a registrar in a support role would ever need to know more about you than the account/pin to manage a domain. There is no technical reason that anyone at a registrar in a support role would ever need to know your domains to manage your account information.

These are separate realms.

For the $1 a year they make on privacy and the $1 a year they make on your domain it's not worth them keeping the data separate. This is the big difference between banks and registrars: money - banks are going to charge you an extra $1 per ATM transaction

So while I still stand by most of what I've said, I've softened a little because I think the real access issue probably exists at most registrars who manage accounts/domains the same way. I've also softened on what Moniker could and shouldn't have done. I don't think they're different than any other registrar on this issue.

At the end of the day, Moniker only had the option of firing CP. I'm not sure that legally it would make sense to comment on a single internal incident as that would likely have violated the privacy of CP... ironic, that.

Privacy was always just a fake money making add on anyway.

Hopefully my last post on this - as it's beating a dead horse and I'm not really in a position to comment accurately on anyone's internal organization. Blah blah...

Perfect opportunity for a registrar to explain how they do it right .... IMHO

 

[GF]

You said that as a TL you see more.

I asked what do you see? I think is a fair question. Do you see PM's for example ? Can you see who is on my ignore list? Can you see when I login ?

You can see IP addresses, e-mail addresses used to register, last login time, and what you're currently viewing on the forum.

It's just standard vBulletin stuff.

You can't see PMs or ignore list.

 

[Vito]

Think about it...
I mean seriously think about it for a minute.

Our reputations mean everything in this business, right?

I still cant believe this but I have people whom I have never ever met in my life, contact me and are not afraid to send me $xxxx w/out escrow at all to buy a domain from me.
That is outrageous...All because of me having a very good reputation.

Would I do the same, sure to someone w/a great reputation also, but to someone I dont know or who has an "iffy" reputation, definitely not!

So, fast forward to the Chef.
Great Guy....lots of friends, Great Reputation, always very public, never scammed anyone before, etc.

Someone has a beef with him and shortly after that he finds out his name is regged with "SUCKS" added on the end of it, AND on top of that that the domain is forwarded to a gay porn site!!! WTF???

Now put yourself in his shoes...
You have All Access to Whois Privay.
You bet your A$$ you are gonna look up who that scunmbag is that is trying hard to tarnish your reputation.

Then, after you do that..
You find out it is someone who you thought was a very good friend of yours! WTF again!

Frustration turns into betrayal, and serious anger now.

Vengeance is next.
Do you sit back and think before contacting your so called "friend"?

Now the email was definitely the nail in his coffin but seriously everyone,
Look at these circumstances and then say that you yourself would have taken the Mother Theresa approach and honor the privacy that your job requires and just leave that mystery forever unknown.
Yeah Right!

The guy is human, he is positively paying for what he did.
He lost his F-ing job!
Thats HUGE in itself in these awful economic times.
He has to wake up everyday now and remember the dumb move he made while not going to work. That is punishment enough.
Let him be.

and If you're pissed at Moniker still, well be pissed at them for that Halvarez B.S. that was 100x worse. IMO

 

[hawkeye]

Think about it...
I mean seriously think about it for a minute.
...Now put yourself in his shoes...
You have All Access to Whois Privay.
You bet your A$$ you are gonna look up who that scunmbag is that is trying hard to tarnish your reputation.

Then, after you do that..
You find out it is someone who you thought was a very good friend of yours! WTF again!

Frustration turns into betrayal, and serious anger now.

Vengeance is next.
Do you sit back and think before contacting your so called "friend"?

Now the email was definitely the nail in his coffin but seriously everyone,
Look at these circumstances and then say that you yourself would have taken the Mother Theresa approach and honor the privacy that your job requires and just leave that mystery forever unknown.
Yeah Right!
..

So basically, your take is 'the ends justify the means', no matter the situation!? Oh..kay. Just curious, where does one draw the line? Where ever its 'most beneficial' to oneself?? Be interesting to know what would be considered 'justified' if it was something more serious than having an insulting domain regged and pointed to a 'park page', like if an actual 'real threat' was made!? It seems from some, that answer.. may be scary!

 

[firefly]

I have no doubt that Moniker has a lot to answer for with all that has gone on there, but at the end of the day there is always a right and a wrong way to go about things when it comes to individual actions. There are quite clearly two separate issues here; the ongoing problems at Moniker and the unethical actions taken by a single individual regardless of the reasons.

One of my all time favorite quotes is from J.C. Watts and I think it is applicable here:

"Character is doing the right thing when nobody's looking. There are too many people who think that the only thing that's right is to get by, and the only thing that's wrong is to get caught."

As for the mud slinging that is going on now between the two main protagonists; it is only furthering the poor perception of the industry as a whole.

I won't have anymore to say about it because of who that individual is. It saddens me and everything that is going on around this is nothing more than a massive black eye that the industry as a whole, will take a lot of time to recover from. That will only start when one mans up and apologizes properly and the other one shuts up and stops stoking the fire. JMO

 

[silentg]

We won't get any answers from Moniker / Oversee regarding this at all. Only solution I see is moving the domains to another registrar.

 

[Archangel]

I've never once liked Moniker. Ever. Why not just go to GoDaddy or something? We all have our thing but I can't say this any nicer: If you have a beef w/ Moniker, just leave them. They'll never be another Registerfly but iif ya don't like Moniker, move somewhere else.

 

[Michelle]

You can see IP addresses, e-mail addresses used to register, last login time, and what you're currently viewing on the forum.

It's just standard vBulletin stuff.

You can't see PMs or ignore list.

Thanks for this.. sorry was awol for some hours ..

 

[GF]

AND on top of that that the domain is forwarded to a gay porn site!!! WTF???

The domain was not pointed to a gay porn site.

The domain was parked, and the parked page had gay porn links on it.

With a domain that includes "Patrick" and "Sucks" - do the math, it'll auto-populate with links to gay porn.

 

[Vito]

The domain was not pointed to a gay porn site.

The domain was parked, and the parked page had gay porn links on it.

With a domain that includes "Patrick" and "Sucks" - do the math, it'll auto-populate with links to gay porn.

You're right, My bad. I do remember reading that on the blog.

With his feelings of betrayal from an assumed friend...The principle of my post is still the same.

 

[silentg]

sucks domain points to Chef's blog now. They got it resolved among themselves. Heated debate is hot on NP and DNF.

 

[DU]

sucks domain points to Chef's blog now.

Some would say that's appropriate... :p

 

[labrocca]

Look at these circumstances and then say that you yourself would have taken the Mother Theresa approach and honor the privacy that your job requires and just leave that mystery forever unknown.

I've had much worse done to me and I don't break my privacy policy. It was obvious he acted out of anger and vengeance and that's where he went so very wrong. The whole "guy is human" thing is fine but so is "sorry but policy is policy...you're fired".

I don't see this as a reason to dislike Patrick but it's a reason not to trust him. You do need to act professionally when it's expected of you in a professional environment. If he's going to try to pass himself off as a professional in this industry then you need to act like it. He's still not imho made a proper public apology but I personally don't care. I have no real vested interest in this story beyond a nice thread at NP.

We won't get any answers from Moniker / Oversee regarding this at all. Only solution I see is moving the domains to another registrar.

Not sure what you think they're going to say. This was brought public by a 3rd party (Rick). For all we know the person who was exposed has dealt with this appropriately with Moniker. They are not obligated imho to make a public announcement over one account effected by one employee. That's not how corporations work.

The domain was not pointed to a gay porn site.

The domain was parked, and the parked page had gay porn links on it.

That made me laugh since Patrick should have taken 10 seconds to do a whois and see the DNS for a parking company and put 2 and 2 together. Instead he acted like a noob. Seriously. He dun goofed.

ChefPatrickSucks.com should point to this thread imho.

 

[GF]

He dun goofed.

The consequences will never be the same!

 

[ODST.com]

sad day indeed for chefpatrick and to think i used to read his blog:S

 

[carob]

Frustration turns into betrayal, and serious anger now.

Vengeance is next.
Do you sit back and think before contacting your so called "friend"?

Yes, you do.

 

[enlytend]

Yes, you do.

:tu:

CP behaved unprofessionally - misused access to privileged data and lost his job as a consequence. Hopefully he learned a valuable life lesson.

I haven't read Moniker's privacy T&C lately, but I'm sure the only way the law and courts could get involved would be if the OP wanted to sue for damages (which apparently, they don't.)

Whois Privacy is just that: It fends off most spammers, would-be stalkers, and nosy people. It's not guaranteed anonymity. (If you want someone to implement THAT, expect to pay a LOT more than $1/domain.)

IMO, it's time for everybody, especially RS, put this to rest and move on.

 

[biggie]

dude sucked long before the domain got regged and this issue came to light


it's just that most didn't know, until now

quit worshipping false idols and you won't get let down in the future


imo...

 

[Blake]

Quite honestly I have had a few business deals with CP "few domain sales" and he was professional and things went as planned. I really don't do the whole reading domain blogs routine and thus CP was never on my radar for anything more then someone who I have purchased a few domains from.

This issue brings up a core problem that I feel will haunt CP for many years to come and that's trust. It literally takes years to gain the trust of the people around you and seconds to lose that exact same trust. Now in all honestly I don't wish for anyone to lose there job or have private matters brought to the public spectrum. On the flip side once CP crossed that line of professionalism and broke protocol he decided his own fate.

It's a very scary thing that someone with emotions set on high can decide to jump in and break through privacy barriers. The same barriers that are suppose to do a job..keep things private. Now I wish CP and his family all the best but from now on out there will always be that little voice in my head about this situation.

Truly a sad day but with time wounds can heal and trust can be regained.

 

[Erdy]

The problem is not only with Chef Patrick but with snapnames management. Any personnel of a company is representing the company in his relations with clients. In this case obviously Chef Patrick din't feel like he was representing snapnames.

He probably felt like somebody doing some freelance work for an employer. To me it looks like his brokering job was more like a freelancer job. He should have never been given access to client information. I'm wondering if he was working from home.