Statement about the recent "mywifeisababe.com" fiasco:
18-Apr-16 00:10
Recently, I became aware of some serious member discontent via a 300+ post status thread that was making false accusations that suggested NewbieNudes was operating under other names without the knowledge of you the members.
Many members were upset and were of the view that this was dishonest and that somehow their trust was breached and therefore considered deleting their account.
I only became aware of the whole matter when I was checking on support chat logs early on Saturday morning. I was obviously very concerned and so immediately investigated.
Mywifeisababe.com turned out to be a site that was opening NewbieNudes.com within an iframe. This means that the site you were seeing was in fact NewbieNudes, but it had the appearance it was opening at mywifeisababe.com
We had no knowledge of this and on subsequent discussions on status and via PMs we were advised that there were a few other examples of this happening under other domains.
I immediately actioned the tech team to write and deploy some code on NewbieNudes that checks that it is not being opened in an iframe, which was successful and solved the problem immediately.
Some users referred to the domain "beachbods.com" which is a domain that we do own, as being another example. It appeared to be the same situation, but in the case of beachbods.com, it was a 10+ year old site that we turned off and simply pointed it at NN to recover whatever traffic might have been visiting beachbods.com at the time. The way this was done was not ideal in that if you went to beachbods.com, then it also looked like NewbieNudes was operating at that domain. We have made corrections to this and now you will see that if you type in beachbods.com you will end up with "NewbieNudes.com" as your final destination.
So, in summary:
1) We had no knowledge of "mywifeisababe.com"
2) As soon as we were made aware of it we made changes to the site so it can't be opened within another domain
3) What you were seeing at mywifeisababe.com was always the real NewbieNudes.com, it was not a clone of NN and your data was never compromised.
4) Beachbods.com - I agree added to the confusion and it has been updated to redirect to NewbieNudes.com so that now you should never see NewbieNudes under any domain that doesn't have "NewbieNudes" in it.
One final note, there was a miss-communication between a moderator and support that meant the moderator incorrectly formed the opinion (and made it public) that NewbieNudes somehow had a hand in the mywifeisababe.com operation. The blame lies with the support staff member for effectively verifying something without clarifying what it was they were verifying, but please - if something is causing so much concern in status, forums or PMs, immediately notify me by PM. No one contacted me and the whole thing would have been a lot less damaging had it been addressed by me sooner. My PM box is always open to all of you.
I hope that clears up any questions you may have had.
Thanks for being here and rest assured, we are most certainly not of the character that was implied in that 300+ long status post.
Cheers,
NN
Many members were upset and were of the view that this was dishonest and that somehow their trust was breached and therefore considered deleting their account.
I only became aware of the whole matter when I was checking on support chat logs early on Saturday morning. I was obviously very concerned and so immediately investigated.
Mywifeisababe.com turned out to be a site that was opening NewbieNudes.com within an iframe. This means that the site you were seeing was in fact NewbieNudes, but it had the appearance it was opening at mywifeisababe.com
We had no knowledge of this and on subsequent discussions on status and via PMs we were advised that there were a few other examples of this happening under other domains.
I immediately actioned the tech team to write and deploy some code on NewbieNudes that checks that it is not being opened in an iframe, which was successful and solved the problem immediately.
Some users referred to the domain "beachbods.com" which is a domain that we do own, as being another example. It appeared to be the same situation, but in the case of beachbods.com, it was a 10+ year old site that we turned off and simply pointed it at NN to recover whatever traffic might have been visiting beachbods.com at the time. The way this was done was not ideal in that if you went to beachbods.com, then it also looked like NewbieNudes was operating at that domain. We have made corrections to this and now you will see that if you type in beachbods.com you will end up with "NewbieNudes.com" as your final destination.
So, in summary:
1) We had no knowledge of "mywifeisababe.com"
2) As soon as we were made aware of it we made changes to the site so it can't be opened within another domain
3) What you were seeing at mywifeisababe.com was always the real NewbieNudes.com, it was not a clone of NN and your data was never compromised.
4) Beachbods.com - I agree added to the confusion and it has been updated to redirect to NewbieNudes.com so that now you should never see NewbieNudes under any domain that doesn't have "NewbieNudes" in it.
One final note, there was a miss-communication between a moderator and support that meant the moderator incorrectly formed the opinion (and made it public) that NewbieNudes somehow had a hand in the mywifeisababe.com operation. The blame lies with the support staff member for effectively verifying something without clarifying what it was they were verifying, but please - if something is causing so much concern in status, forums or PMs, immediately notify me by PM. No one contacted me and the whole thing would have been a lot less damaging had it been addressed by me sooner. My PM box is always open to all of you.
I hope that clears up any questions you may have had.
Thanks for being here and rest assured, we are most certainly not of the character that was implied in that 300+ long status post.
Cheers,
NN
If this thread breaks our
rules please
