Google changes policy in a move that restrict and eliminates clothes free blogs.
A long time ago when this site was in its infancy we had an alternate account on blogger. It was not separately maintained but we sent links of posts from this site to that blog. Today we received this email.
Dear Blogger User,
We’re writing to tell you about an upcoming change to the Blogger Content
Policy that may affect your account.
In the coming weeks, we’ll no longer allow blogs that contain sexually
explicit or graphic nude images or video. We’ll still allow nudity
presented in artistic, educational, documentary, or scientific contexts, or
where there are other substantial benefits to the public from not taking
action on the content.
The new policy will go into effect on the 23rd of March 2015. After this
policy goes into effect, Google will restrict access to any blog identified
as being in violation of our revised policy. No content will be deleted,
but only blog authors and those with whom they have expressly shared the
blog will be able to see the content we’ve made private.
Our records indicate that your account may be affected by this policy
change. Please refrain from creating new content that would violate this
policy. Also, we ask that you make any necessary changes to your existing
blog to comply as soon as possible, so that you won’t experience any
interruptions in service. You may also choose to create an archive of your
content via Google Takeout
For more information, please read here
The Blogger Team
This seems to be a part of recent public moves by Google to “refine their focus”. Needless to say we have deleted our blog there as it was just a placeholder blog. However the many clothes free blogger who had their blogs there will now have to find new homes for them and recreate then elsewhere. Tough deal.
Are you a clothes free blogger affected by this change let is know!
Get more stuff like this
in your inbox
Subscribe to our mailing list and get interesting stuff and updates to your email inbox.
Thank you for subscribing.
Something went wrong.