Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/http.php on line 61

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php:520) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-content/themes/guzel/guzel-pro/functions.php on line 2

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-settings.php:520) in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-content/themes/guzel/guzel-pro/functions.php on line 2

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-content/plugins/register-plus/register-plus.php on line 1704

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-content/plugins/register-plus/register-plus.php on line 1704
SlashAsia » Internet in China becomes a platform for muckracking
Tuesday, September 1, 2015 20:06

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 55

Internet in China becomes a platform for muckracking


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/46/d201698760/htdocs/slashasia/WP-Current/wp-includes/functions.php on line 55
Monday, April 6, 2009, 12:26
This news item was posted in China, News category and has 0 Comments so far.

Recently a group of Chinese Internet users went on a witchhunt to expose a local government official at a media watchdog, posting uploaded receipts adding up to nearly $7000 in dining, entertainment and massage expenses. Dubbed the Liuyang Scandal, Internet users started asking how such a lowly public servant could be living such a lavish lifestyle. Analysts point to the Internet as a content firehose that officials will have trouble controlling in the future. An estimated 3000 websites are created daily and while the government can limit some websites by setting up campaigns in the name of ridding pornography, for example, many say online communities are tuned in to updates on new sites before they catch the attention of officials. And the muckracking is not just limited to corruption. In another recent case, the mother of a young man executed for killing six police officers last year has used the Internet as a platform to tell her harrowing story.

China Web users turn keen eye back on government - Reuters
The Story of Cop-Killer Yang Jia’s Mother - Beijing Briefs

Both comments and pings are currently closed.

No Responses to “Internet in China becomes a platform for muckracking”