Locking every Backspacer thread has gotten way out of hand

EvolverEvolver Posts: 525
edited September 2009 in The Porch
First off, let me say that I understand and 100% agree with the rule that Kat and the other administrators have posted when locking threads regarding artist copyright respect, etc. And what I have to say is with full respect for ALL of those who use and operate this board, so if my words are taken as disrespect then they have been taken incorrectly. Now, obviously if someone posts something (as many have in the last 24 hours) that infringes artist copyright laws, promotes (i.e. links to) pirated material, or other such obvious infractions those posts should be locked and/or deleted.

However, I have on several occasions come across posts, such as http://forums.pearljam.com/viewtopic.php?f=4&t=110044 which in my estimation in no way breaches the following rule:

"Please respect an artist's copyright. Linking to or otherwise promoting stolen art is prohibited. If an artist's work is leaked online, don't post it here and please be careful when posting other people's images in posts."


From what I can tell:

1. The artist's copyright was never disrespected in that thread.
2. There were absolutely no links to stolen art.
3. There was no promotion of stolen art.
4. There were no other images of any kind posted that belong.

So I'm curious as to exactly why this thread was locked? Because unless there were other posts at the tail end of that thread that were deleted by the mods before/since the post was locked, there was exactly zero reason why a lock should have been warranted. Now I know I have chosen my words carefully and there should be absolutely no reason why this post or thread should be censored. Simply put, if we cannot have an intelligent and viable conversation about topic of unwarranted censorship without fear of censorship, then I think everyone here would agree that something is very wrong with this picture.

Thank you, and I look forward to the discussion.
Post edited by Unknown User on

Comments

This discussion has been closed.