Google has decided to reverse a decision that the company had made earlier in the week to ban sexually explicit content – like images and videos on its Blogger platform. The move was one that initially caught users off-guard and really took the Internet by storm. However, the movement around opposing the new rule – was light in relation to some of the other things the company is facing right now.
This is why it was even more intriguing that the company decided to walk that policy back and make a complete U-turn on sexually explicit content. Originally, the rule would have impacted any content that was previously shared, and would have made any and all of the posts which were impacted by this explicit material private until the content was removed. The flagging of previously appropriate material – according to the rules of Google’s blogging platform though, are ultimately what drove the tech giant to reverse its course.
The company noted that unfortunately “retroactive enforcement of the new policy” would ultimately stand in the way of protecting and holding valuable the content that was put on Blogger as many as 10 years ago. Now though, the company has said that they will boost enforcement of current rules, and ensure that any even mild infringement on those rules sees swift punishment.
The changes in enforcement will primarily mean that commercialized porn will not be allowed on the platform and that this will be the area at which Google works hard to ensure that remains policed appropriately. The company also noted that users who run “adult” rated blogs should continue to mark their blogs and postings as such to ensure that the wrong people do not see the images that might otherwise be exclusively for an older audience. This is the first time that Google has taken a stance like this, and really, it’s the first time that a company like Google has seen a harsh reaction when it comes to the opposition of such a new rule. Now though, it will be interesting to see how it plays out in the long run, and how this flip-flopping in policy works out for Google.