Jimbo has just been granted nearly unlimited powers project-wide.

It's true, — I am your Founder.

I brought you into this world and I can take you out.

Now, I am become Wikipedia, the destroyer of worlds

Useful - I didn't know that most of those flags existed (or where codifed, at any rate). I have previously argued on Jimbo's talkpage that all his buttons - whether he uses them sparingly or at all or not - should be shown, just so we know what he can/could do. I suspect, since it was probably over a month or two ago I suggested this, it is co-incidence that it has happened.

I thought some of these were gag-entries, put in as satire. Bigdelete? Nuke? Just goes to show you how hard it is actually satirize WP when they're really going at it. It's like congress and politics. At some point you just put in the moments of zen exactly as they happen.

Uh, Dude, this is Jimbo we are talking about. Founder, certainly, but maybe not so smart that he might understand globalreformatservers means "nuke", or ServerPermanentStandby is "Bigdelete". When the only people able to press the buttons are the Devs and Jimbo, you write it in the language of the lowest common denominator...

Until recently Jimbo did not know that stewards have sysop rights on every wiki, hence why he was so annoyed the Meta-wiki community removed the redundant ones. He had to test before he accepted what we were saying was in fact true.

A list of groups, their rights and an explanation of what most rights do is at http://toolserver.org/~pathoschild/globalgroups/ . The rights listed for each group doesn't seem to accurately reflect currently held rights though. For example, compare what's listed to the stewards global rights log.

Most of those bits come with usergroups on en
apihighlimits: bot
autoconfirmed: autoconfirmed (the autoconfirmed permission is what allows editing of pages whose protection level is autoconfirmed, the autoconfirmed usergroup is the actual bit)
autopatrol: not used on en
bigdelete: I forget, maybe Bureaucrat? It's to bypass the 5000-revision limit.
block, blockemail, browsearchive: sysop
createaccount: accountcreator and sysop
createpage: user
createtalk: everyone
delete, deletedhistory: sysop
edit: everyone
editinterface, editusercssjs: sysop
import, importupload: sysop, import, transwiki. funny considering the feature doesn't actually work
ipblock-exempt: sysop and ipblockexempt
move: autoconfirmed
noratelimit: bot
protect: sysop
purge: everyone
rollback: sysop and rollbackers
suppressredirect, undelete, unwatchedpages: sysop
upload: either user or autoconfirmed, i forget
checkuser-log: checkuser
tboverride: no idea what this does
globalblock, globalunblock, globalblock-whitelist: steward on meta
renameuser: bureaucrat
nuke: feature not enabled on en. (sysop on meta, incidentally)
oversight: oversight
centralauth-merge: steward on meta
globalgroupmembership: steward on meta
abusefilter-modify, abusefilter-log-detail, abusefilter-view, abusefilter-log, abusefilter-modify-restricted, abusefilter-revert: Either the feature is not enabled on en, or it's a centralized thing that lives on meta. I can't tell who has the permissions

I used to know an API call that listed all the permissions someone has (it's how I found out that I apparently had the suppressredirect right - though the feature was not enabled on en at the time)

Nuke, if you were wondering, is a feature to delete every article a user has created.

I think Jimbo just wanted to make Razorflame jealous.

Does this bit refer to articles of clothing, I wonder? Everyone's heard of the casting couch method of getting (a)head, but it's strange that Jimbo and his helots should feel the need to point out that he got all that stuff fair and square. Oh well.

abusefilter is close to being enabled on en.

The description is here.


The stewards are currently arguing amongst themselves whether they should be allowed to access all of its features.