What you mean is... perhaps there is not even a trail of who looked up what at Oversee, so the breach of privacy could have gone undiscovered.Years ago I worked @ AOL in Broadband Support. One of technicians on my team used the AOL internal program (Sherlock) to look up a celebrities address. When it was found out they were fired on the spot.
Indeed :yes:I hope he looked at whois of only ChefPatrickSucks.com , nothing else. And has paid the price.
Who regged it and what was the motive behind it ? It will be interesting to watch out....
Bravo. Each action should require a login with unique identifier. That way, each action can be tracked should an issue or breech arise.I can tell you GD has footprints on everything and they take it very seriously.
I hope he looked at whois of only ChefPatrickSucks.com , nothing else. And has paid the price.
Who regged it and what was the motive behind it ? It will be interesting to watch out....
what would it matter who regged it? What would you do that with info? Nothing you can do...obviously you are a buddy with the chef....Yes....nothing else.....we all know that if your site/name or anybody's site/name for that matter was regged with a sucks.com at the end and re-directed to a gay porn site.....and u worked at a registrar..and had access to see who the f*ck just regged your namesucks.com......you would do the same!!...Slick Rick included!....so....let's just all cut the f*cking bullshit here.......
this is the real root of the issue.....where things get very interesting......anybody wanna play "Guess His Name"??...
what would it matter who regged it? What would you do that with info? Nothing you can do...obviously you are a buddy with the chef.
you wouldnt take a peek to see who the f*ck regged it???.....
A smarter cookie would have has someone unrelated to it look it up.
-=DCG=-
you telling me that if someone regged DomainsIncSucks.com....at the registrar u worked for....and found out that someone regged it...and if you could.... you wouldnt take a peek to see who the f*ck regged it???.....i'm just stating the obvious here......not a buddy with anybody...it doesn't matter.....but answer me this.....when you found out that the person who regged it was supposedly a "friend" of yours.....what would u do with that info???.....i doubt nothing.....and don't BS yourself....
I don't know, I don't think it would bother me. I've been called much worse. Either way, if you used that info they would know exactly how you got the info and could use it against you. He would of been better off doing nothing, the domain would most likely drop next year and be forgotten.
After all this hype, the owner of chefpatricksucks.com should put it up for auction and send all proceeds to the people of Japan.
It will never be worth more than it is today.
-=DCG=-
It wouldn't bother you if you were trying to build a brand....trying to make a name for yourself....trying to start up a cruise conference.....and find out that some assh*le "friend" of yours regs DomainsIncSucks.com and points it to gay porn????.......dude...put yourself in his EXACT shoes....hard to do nothing....i am just curious why Slick Rick....or Rick the Dick...whatever u wanna call him....felt the need to stick his nose into this....and how closely tied in he is to this whole drama.......imo...chef got set up....didnt see it coming....and is catching all the heat for it....
Actually...since we all know that Chef looked up who regged it.....we might as well all know WHO regged it?....no?...fair is fair?..right??.....
It is clear that the Patrick Ruddell or Oversee are not going to give us that information.
-=DCG=-
After all this hype, the owner of chefpatricksucks.com should put it up for auction and send all proceeds to the people of Japan.
It will never be worth more than it is today.
-=DCG=-
*the exceptional businesses of our esteemed moderators