Comments on: First report of blog censorship using Blogger “flag” option http://www.blogherald.com/2005/08/22/first-report-of-blog-censorship-using-blogger-flag-option/ The leading source of news covering social media and the blogosphere. Mon, 13 Feb 2012 09:18:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Matthew Robinson http://www.blogherald.com/2005/08/22/first-report-of-blog-censorship-using-blogger-flag-option/comment-page-1/#comment-45374 Matthew Robinson Fri, 26 Aug 2005 00:59:39 +0000 http://www.blogherald.com/2005/08/22/first-report-of-blog-censorship-using-blogger-flag-option/#comment-45374 As a person who disagrees with the current concept of the flag button I've found a work around for it. The solution is posted to my newly created style hacking blog at <a href="http://stylingblogger.blogspot.com/2005/08/how-to-remove-flag-button-from-navbar.html" rel="nofollow">Editing the Navbar</a>. Hope this helps prevent future problems for folks that only want freedom of speech. If something illegal is being posted that is an entirely different subject matter and hopefully the flag button will eventually evolve into a way for us the members of Blogger and Blogspot to police one another against illegal/spam activity. Matthew Robinson As a person who disagrees with the current concept of the flag button I’ve found a work around for it. The solution is posted to my newly created style hacking blog at Editing the Navbar. Hope this helps prevent future problems for folks that only want freedom of speech. If something illegal is being posted that is an entirely different subject matter and hopefully the flag button will eventually evolve into a way for us the members of Blogger and Blogspot to police one another against illegal/spam activity.
Matthew Robinson

]]> By: gypsyman http://www.blogherald.com/2005/08/22/first-report-of-blog-censorship-using-blogger-flag-option/comment-page-1/#comment-45143 gypsyman Mon, 22 Aug 2005 23:38:47 +0000 http://www.blogherald.com/2005/08/22/first-report-of-blog-censorship-using-blogger-flag-option/#comment-45143 Two points concerning your sumnation of my article. One not once did I say his blog had disapeared, I said that he was unable to post to his site. As of now he is still having difficulties, it took twelve attempts to put up one post, and others he was still unable to publish. Two, Blogger says that in their description of the flagging process that they use a process that depends entirely on "community standards" the more votes against a site, the heavier the penalty. They do not appear to check the so called offending sites, but allow the voters to do the work. I also did not allege or accuse anyone of anything, rather said that there was the possibility of this system being abused, and was wondering whether and that Mr. Banker and I were wondering if this had happened in this instance. I also said that he still hoped it was a technical foul up that could easily be explained. The point of the article was not that it happened to Mr. Banker, but that it could have happened and could happen easily enough to someone else in the future. Thank you for publicizing this situation though, maybe it at least will get the people at blogger motivated to move quicker on tech problems. They seem to move quite slowly. I'll send a link to this post to Mr. Banker in case he has missed it. Two points concerning your sumnation of my article. One not once did I say his blog had disapeared, I said that he was unable to post to his site. As of now he is still having difficulties, it took twelve attempts to put up one post, and others he was still unable to publish.

Two, Blogger says that in their description of the flagging process that they use a process that depends entirely on “community standards” the more votes against a site, the heavier the penalty. They do not appear to check the so called offending sites, but allow the voters to do the work.

I also did not allege or accuse anyone of anything, rather said that there was the possibility of this system being abused, and was wondering whether and that Mr. Banker and I were wondering if this had happened in this instance.

I also said that he still hoped it was a technical foul up that could easily be explained. The point of the article was not that it happened to Mr. Banker, but that it could have happened and could happen easily enough to someone else in the future.

Thank you for publicizing this situation though, maybe it at least will get the people at blogger motivated to move quicker on tech problems. They seem to move quite slowly.

I’ll send a link to this post to Mr. Banker in case he has missed it.

]]>