UDWiki talk:Administration/Policy Discussion/Semi-protection

keep

• Keep Yarp! =) I lieks this sguggestopnm! -- Cheese 00:20, 11 February 2009 (UTC)

Yarp. --  AHLGTG THE END IS NIGH! 00:26, 11 February 2009 (UTC)

Why?

Should users ever have access to any protection privileges what so ever? I can see move but no, not protection. --Karek^maps?! 03:37, 11 February 2009 (UTC)

Oh, no this is for sysops, but I'll make that clear. --  AHLGTG THE END IS NIGH! 03:39, 11 February 2009 (UTC)

Can you not just copy paste the oridinal article over vandalised ones? --Athur birling 20:55, 11 February 2009 (UTC)

The idea is to prevent the vandalism in the first place. But yes, the edit can be copy-pasted over, or undone using the inbuilt undo function from the history tab. --  RoosterDragon  21:16, 11 February 2009 (UTC)

Then this is not needed at all--Athur birling 12:51, 12 February 2009 (UTC)

Hm...

The fact that it is sysops using it makes me feel a lot better about it, but I still don't see where this would be useful. --Cyberbob 03:46, 11 February 2009 (UTC)

It would help protect some pages from vandal only accounts that don't need to be edited by new users, such as Template:Wiki News (a high risk template).--  AHLGTG THE END IS NIGH! 03:47, 11 February 2009 (UTC)

That reminds me of the time a vandal tried to put goatse into the wiki news template. The semi-protection would be great for heavily used images and important pages that can't be fully protected. --ZsL 07:44, 11 February 2009 (UTC)

Yeah. User signatures would also be good candidates. Linkthewindow  Talk  09:03, 11 February 2009 (UTC)

Good points. --  AHLGTG THE END IS NIGH! 18:45, 11 February 2009 (UTC)

Abuse of auto-confirmed status

I think there should be a section specifically stating that confirmed (by A/VB) vandalism of a semi-protected page will lead to automatic removal of the auto-confirmed status, by the crats. I hope that is possible. If it's not, I don't think I'd support this policy -- boxy ^{talk • teh rulz} 13:36 11 February 2009 (BST)

If Wikipedia can't remove the autconfirmed, then we surely can't. I don't really think you can abuse a semi-protected page, it's treated the same as any other page unless your new (not autconfirmed yet) as you can't edit the page. If you vandalize the page it will be treated the same as if the page wasn't semi-protected. --  AHLGTG THE END IS NIGH! 18:45, 11 February 2009 (UTC)

What should be semi-protected?

Should we give, at least, an outline of what sort of pages should be semi-protected, and which ones should be immune from semi-protection? I'm thinking that any group/user page that is requested for semi-protection should be allowed, but community pages (location/suburb/glossary/etc.) pages should only be semi-protected if there is an imminent threat of vandalism -- boxy ^{talk • teh rulz} 13:36 11 February 2009 (BST)

I have a few good ideas. Semi-protection will work the same in terms of how normal protections are done, except it's purely to stop vandal-only accounts. I'll spell some things out better since a lot of this is copy paste :o --  AHLGTG THE END IS NIGH! 18:45, 11 February 2009 (UTC)

I made some changes. You can fiddle with the text if the wording seems awkward. --  AHLGTG THE END IS NIGH! 19:37, 11 February 2009 (UTC)

Semi-protection will be useful in pages a recently created user would accidently edit because he doesnt know how to use the wiki properly, yet allowing users with more wiki-foo skills to edit it. Various templates fall in this category, specially the ones used in the suggestion system. --People's Commissar Hagnat ^{[talk] [mod]} 21:38, 11 February 2009 (UTC)

I assume you are excluding the various danger reports in that statement. They are the very sort of thing new guys should be encouraged to edit right away. Though you could semi-protect the main bits of the underlying infrastructure. Come to think of it, how come Template:MapSafe & co are protected but Template:DangerMap is wide open? Nothing to stop me turning that thing into a massive rickroll. Hmm...*off to scout YouTube* --  RoosterDragon  22:18, 11 February 2009 (UTC)

It was already. I dont remember why it wasn't protected before, but i'll do it now. And yes, i dont expect danger report pages to protected --People's Commissar Hagnat ^{[talk] [mod]} 23:28, 11 February 2009 (UTC)

The Ridleybank danger report has been semi-protected for years now. Most high profile ones that tend to cause conflicts are. --Karek^maps?! 02:49, 12 February 2009 (UTC)

How is it "semi-protected" if different user groups don't exist on the wiki??? --WanYao 07:38, 12 February 2009 (UTC)

Semi-protection has nothing to do with user groups, although apparently it's possible to add in such a functionality but I can't say for sure. --Karek^maps?! 08:51, 12 February 2009 (UTC)

Well please explain how "semi-protection" currently functions. It's rather relevant to this policy discussion. --WanYao 14:10, 12 February 2009 (UTC)

My understanding of it has been that it blocks users with less than a week of existing from edting semi-protected pages. We once used it as a way of blocking Izumi alts on the Locketside page and it does seem to have worked. --Karek^maps?! 04:23, 13 February 2009 (UTC)

[1]--Karek^maps?! 04:30, 13 February 2009 (UTC)

Hmm, you sure? Anyways, are there any problems with the policy? Or can I put this to vote? --  AHLGTG THE END IS NIGH! 05:06, 13 February 2009 (UTC)

I am sure about it. The problem is that no one is updating the proxy ban lists. Semi-protection forced her to make throw away accounts to use at a much latter date. --Karek^maps?! 07:06, 13 February 2009 (UTC)

I've made it as clear as possible. It will work a bit like semi-protection on Wikipedia, except that anonymous users can't edit as usual and all users can upload images. Any issues before I put this to vote?--  AHLGTG THE END IS NIGH! 00:11, 13 February 2009 (UTC)

Remove the "high-risk" bit from "high-risk group pages". No reason to discriminate arbitrarily if the groups have to request it themselves. Can't even imagine it even being a big thing for groups anyway. --  RoosterDragon  00:21, 13 February 2009 (UTC)

Done. It could really be any page, excluding anything that would be edited by a newbie (unless in case of excessive vandalism). Some group pages are prone to vandalism though, see Umbrella. --  AHLGTG THE END IS NIGH! 00:26, 13 February 2009 (UTC)

Yeah, I'm just pre-empting somebody saying "Why couldn't my medium or low risk group page be protected if I want?" and voting to reject it regardless. Just trying to keep those bases covered, not matter how unlikely. :) --  RoosterDragon  00:43, 13 February 2009 (UTC)

Unless this policy makes it so that newbies can't make suggestions I don't like it. You figure out a way to block that and I'm all for it. If there is anything that should have a "you can't edit this shit because you are a new fuck" it is that. -- #99 ^DCC 19:22, 13 February 2009 (UTC)

Actually with semi-protection of Category:Current Suggestions. . . --Karek^maps?! 03:16, 15 February 2009 (UTC)

• Sighs*

Yet another way that a wiki encourages elitism --Imthatguy 21:05, 28 February 2009 (UTC)

Yeah, 25 edits and 7 days, pretty 'elite' that. --  RoosterDragon  21:08, 28 February 2009 (UTC)

Ideas for implimentation

Please discuss... Boxy 11:40, 21 April 2011 (BST)

Replying here instead of 7 times. Nothing is changed by us now being able to add minimum edit amounts here. Semi-protection should be used in the same manner it always has been; Highly controversial pages that tend to attract drama and occasional turn and burn accounts. Most of which are already semi-protected. It, as the policy even says, should never not be case by case. --Karek^{maps 2.0?!} 14:09, 21 April 2011 (BST)

You don't think it would be prudent to leave some of the below types of pages semi-protected for extended periods, if they arn't likely to need editing by new accounts? For example, group pages could remain semi-protected indefinately, whereas simple protection would mean that established (non-sysop) users wouldn't be able to edit their pages. Semi-protection opens up this option -- boxy 14:43, 21 April 2011 (BST)

It's a tool to deal with certain types of vandalism, shouldn't be taken beyond that. Assume Good Faith, even before it gets to A/VB. --Karek^{maps 2.0?!} 14:55, 21 April 2011 (BST)

What I said, apparently. Also, it might be prudent to adjust this policy so that it restricts main page creation too, as one option that could be used against the bots. Though there are certainly a few drawbacks, such as newbies creating group pages. --  AHLGTG THE END IS NIGH! 22:27, 21 April 2011 (BST)

Well the bots have been know to edit pages rather than create new ones and they're a bit harder to catch when they do it so we might want to be careful with that. ~ _{00:00, 22 April 2011}

That too, I'm not sure if disallowing them from making pages will do that though. There's also the option for non-autoconfirms to have to do a captcha when making an external link, though I'm not sure how probable that would be to do (the Shartak wiki has captcha, and there's only been 1 bot in many months). --  AHLGTG THE END IS NIGH! 00:28, 22 April 2011 (BST)

Do consider that lots of newbs use external links for internal purposes, because the captchas can be extremely offputting and annoying.--Yonnua Koponen ^{T G P} ^^^ 00:33, 22 April 2011 (BST)

This would be particularly bad for user pages (profile links), yeah. Creating a main namespace page requiring a captcha may be better, and shouldn't be too annoying. --  AHLGTG THE END IS NIGH! 00:36, 22 April 2011 (BST)

User Pages

Automatic on the request of the user, including all sub pages. The user talk page is only included in extreme circumstances (but archived talk pages are also automatic) Boxy 11:40, 21 April 2011 (BST)

User signature pages might be useful, at the least. --  AHLGTG THE END IS NIGH! 22:31, 21 April 2011 (BST)

Group Pages

I suggest they can be semi-protected on request from a group member (overule allowable by a group leader) Boxy 11:40, 21 April 2011 (BST)

Community Pages

I suggest, only in the case where they are high profile, and have a history of being vandalised by throw away accounts Boxy 11:40, 21 April 2011 (BST)

Event Pages

Only in extreme circumstances? Boxy 11:40, 21 April 2011 (BST)

Templates

On request from the author Boxy 11:40, 21 April 2011 (BST)

Categories

If the category is "owned" by a group or individual, they should be treated as a group or user page, otherwise, as a community page Boxy 11:40, 21 April 2011 (BST)

Other pages

Not listed? Images? I'm unsure if they are applicable Boxy 11:40, 21 April 2011 (BST)