Home / Blog / Culling the Fake Name Herd… Chinese Companies Comply with “Real Name” Requirements.

Culling the Fake Name Herd… Chinese Companies Comply with “Real Name” Requirements.

Posted on

***Blog Post Update:***

Internet In ChinaBack on February 5th, 2015 a blog spot was posted about coming changes in China that require any registered Internet account used in China to use a real name when posting and or communicating. This scenario goes into a requirement status on March 1, 2015.

It seems that the government is rather serious regarding the matter and companies are clamoring to comply. Some Chinese companies, like Alibaba, claim that more than 60,000 accounts have been deleted (as reported in this article). I am surprised it is that low and would wonder if there was not a specific list presented to these groups to run through immediately with other compliance and search measures to follow.

The Cyberspace Administration of China (CAC), the Internet specific equivalent of the Federal Communications Commission (FCC) in the United States, stated that “The reasons for their removal included accusations of being misleading, rumor mongering, links to terrorism, or involving violence, pornography and other violations…” This statement came out on Thursday February 26.

I find it interesting that the CAC and the FCC are both making major changes at the same time and ironically the CAC is more open about their moves and reasoning. Both of these changes have likely been in the making for sometime, however there are efforts between the U.S. and China for cooperation on the Internet. The most recent meeting was in December of 2014 and another is to be held in July.

Though a lot has been printed in recent days, it is yet to be determined what actual changes are part of the “Net Neutrality” work that is being done by the FCC. On that subject, we will remain silent until we can read the documents or something that is official rather than politically motivated talking points.  Keep watching. I am sure more will come out on both of these scenarios.
Original blog post: http://commonsensesecurity.net/?p=137