The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
||||
|
||||
Public discussions of staff decisions are not permitted on the site.
I don't agree with this rule. And this is feedback about the site.
I don't understand why this rule is in place, if not only to hide bad staff decisions. A transparent community is always the best. Not authoritative ones. If you think that leads to anarchy, you are dead wrong. |
#2
|
|||
|
|||
hum, another thread in the edge of being deleted.. lol
|
#3
|
|||
|
|||
Quote:
https://vborg.vbsupport.ru/info.php ) If the specific user in question has any comments or concerns about a policy, they can query the staff privately where they will get a final response. Having staff every staff action up to user debate is not proactive at all, and it is not how we run this forum. |
#4
|
||||
|
||||
On my forums, I let my members discuss every decision I make. I actually learn some things sometimes.
But be as you will. |
#5
|
||||
|
||||
I follow the same policy... public "discussion" of why so and so was banned, or why a thread was deleted is always destructive. Also, members usually don't see the bigger picture, and tend to take the matter personally. When I do something as an admin, that is the bottom line; no ifs ands or buts.
As for this specific incident, I'll stay out of it. |
#6
|
||||
|
||||
I've been a forum administrator for 7 years, I used to be like that. I don't use brute force now unless it's really needed. As in, someone posting pr0n to be annoying.
But again, be as you will. |
#7
|
||||
|
||||
I agree. Since my members are military personell I don't have the same issues others might. They know there was a reason, and don't feel a need to discuss every decision I make. Why should you need to second guess everything....
|
#8
|
||||
|
||||
I run a gaming site, pretty much overrun by stupidity. The other admin is a bit more laid back, but tihngs tend to get out of control quite quickly unless we put our foot (feet?) down. Of course it depends on the community.
Considering this is a business site, and not really a public discussion board, they have a public image to maintain. Having hacks here with security holes could hurt thousands of customers, so they treat it with the highest priority to 1) remove the hack, and 2) notify the customers at risk. 3) is a lower priority, and that's notifying the creator of the hack for it to be dealt with. Sure it may hurt the creators reputation, but in all honesty that is the least of their worries. It's not like their own stuff hasn't had security holes - it's the fact that they are dealt with and fixed ASAP that is important. edit, Oops I said I would stay out of this one. Too late >.< |
#9
|
||||
|
||||
I agree with the mod being removed. I don't agree with not letting the coder express his frustration. Would it hurt the site's image? No it wouldn't... It hurts more deleting posts than letting people express themselves.
This community has intelligent people, it's not composed of nonsense babbling brats other communities might face. If you treat people as intelligent beings, they will turnout to be just that. Given exceptions, that are not the case on this board. If people second guess every decision you make, let them. They might find out the reason you made the decision in the first place, if not try to explain to them. They are not always going to become a mob. If they do, be a man and deal with the mob. Just my 2 cents. ps: I run a gaming site too |
#10
|
||||
|
||||
Just so there is no misunderstanding, I respect your ideas and the way that you run your sites. I disagree with opening every decision to discussion. Everyone has an opinion, it's almost impossible to get things done if you need to have a poll or discussion for every little decision. Once you decide on the staff on your site they decide how it's going to be run, and what policy will be. Policy, like the rules is something that the members have signed off on if they want to be a member of your site. Every one of us run our sites differently, can you imagine the headache vBorg must have trying to enforce it?
They made the policy and in becoming members here we agreed to follow it. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|