This is more of a staff guideline, not necessary to add as a public rule.
TheXnator wrote:
I've dealt with this situation.
Teamspeak staff members are not allowed to use this addon, and I have told both Hinata and Nickolas to uninstall the addon to stop this happening again.
I beg your pardon? You might be a teamspeak head admin, but since when is using a
public addon something within your control to stop. I get something happened and the correct action needs to be taken to correct this situation and/or the problem entirely, but your solution is to tell people they aren't allowed to have something that Teamspeak clearly allows us to have. There is such a thing called Self-Control and Self-Accountability. When people fuck up, it's on them and nobody else, you cannot justify your point to any degree just because someone fucked up. Tell them not to do it again, disable it if they can't maintain self-control over themselves, but don't start trying to impede our freedom by telling us staff we aren't allowed to use something when it's supposed to be used as an administrative function. We've done nothing to deserve it as a whole, just because some people fucked up, doesn't give you the right to strip a resource away from the rest of us.