UDWiki talk:Administration/Policy Discussion/Signature Text Policy Revision
This policy proposal was prompted by User:Revenant's latest signature, which uses extensive vertical lines of characters which cover significant portions of whatever page the signature is transcluded on. For prior discussion on this signature, see here. Hat tip to User:Spiderzed for the initial wording.
Discussion on this policy should occur below.
Luke's gud
Get it to voting already. -- Spiderzed▋ 18:56, 5 October 2015 (UTC)
- Technically, policies are supposed to be open for discussion for three days before voting can begin. Bob Moncrief EBD•W! 19:03, 5 October 2015 (UTC)
I'd support it, but...
From the original policy:
- If a signature or template is changed in such a way as to seriously impair the operation of the wiki, the damage may immediately be reverted, or deleted if necessary, and the user who performed the alteration will be perma-banned with no questions asked.
Given that the whole point of the wiki is to be a resource that we can read, obstructing the ability to read the wiki seems like something that falls under that provision already. I'm okay with the proposed change, but I'm just not convinced it's necessary.
If anything, I'd suggest adding clarification regarding the one week warning period if we're talking about changes to the sig policy. There's a broad misconception that we can't act on a bad signature until the week-long warning period is up, when it's clear from historical comments and even other parts of the policy that that was not the intent. Rather, the intent was to give someone a one-week grace period before bad faith was assumed (i.e. don't assume that their very first post with a bad sig was intended in bad faith), but the policy itself says
- If a user repeats such actions then the initial warning can be skipped and the vandalism case can be brought forth immediately.
That is, we can take immediate action against the user if they post repeatedly with their sig, and the earlier quote I provided makes it clear that we can take immediate action against sigs that "impair the operation of the wiki" (not to mention perma-banning the user too). So, the week-long period is not an opportunity for someone to hold the wiki hostage for a week until they're forced to revert the changes, nor does the existing policy preclude others from taking action. It merely prevents them from punishing the user immediately in some circumstances. Making that clearer would address more of the issues we've dealt with over the years with the signature policy. —Aichon— 20:33, 5 October 2015 (UTC)
- Isn't pretty much all of that already clear from the text as it stands? It seemed that way to me. Bob Moncrief EBD•W! 21:16, 5 October 2015 (UTC)
- I find it utterly hilarious that there's a clause in the Sig policy that allows you to perma anyone that tries to break the wiki. Beautiful. A ZOMBIE ANT 23:41, 5 October 2015 (UTC)
Couple of thoughts
Good work putting it forward asap to have it fixed as soon as possible Bob, but I think the thing that needs to be changed most pressingly is the one-week obligatory waiting period. I think that sysops need the power to make a 'ruling' of sorts on what signatures are damaging, in extreme cases like this and SLR. Waiting one week for this to blow over is too long for something as wiki-damaging as Revenant's signature. That is, it's already within precedent through SLR and maybe even a couple of others that the sysop team can stop this right now through A/VB but I fear that's where your respect/fear towards Revenant is stopping this from being ended now.
The signature issue here is one of having the power to change damaging signatures quickly, and for it to stay that way. Rev's already essentially breaks the image height rule (doing it with text still in practice doesn't change that) and you could make an argument that it's still wiki-breaking, so while adding extra rules will help, it won't help you with the fact that this issue needs to be fixed now. A ZOMBIE ANT 23:41, 5 October 2015 (UTC)
I oppose this and all the buttfuckery that birthed it. It's not like this is a heavily trafficked site which will suffer for the occasional sig issue. 00:27, 6 October 2015 (UTC)