Macfan assigned the new example account example rights.

Shouldn't his account be disabled, as a community banned user?

Per above comment.

It's OK now. This error isn't happening anymore.

Without it being reproducible, MacFan cannot fix it. Please detail what you did.

Hi, Username, I cannot reproduce this. Can you describe exact steps for the error to occur?

Done by pull request

As I have personally participated in the discussion linked, consensus needs to be determined by MacFan4000. Priority set to low as a controversial request with no clear consensus.

Reopen if issue still happens.

Is this still happening?

fixed

same with creating subpages

same thing has happened even after trying to use different names and ways to create.

There is community consensus for this action at the community portal, so boldly updating to high.

Please refrain from opening pointless tasks, this phabricator instance is not for testing.

done.

I am fully willing to do this myself. I just am creating this item for the record.

Incompatible with our setup

Default skin set to timeless, to keep mobile friendliness

@MacFan4000 any objections?

If there was a consistent issue where there was abuse being stopped by the abuse filters that needed CU information to look into, I'd do it, but there just hasn't been precedent.

I would like to suggest reconsideration of the abusefilter-private right. Abusefilter now logs private data access. This must be enabled with the $wgAbuseFilterPrivateLog setting and the abusefilter-private-log right is required to view it. I suggest this config option be enabled and both rights be added to the checkuser group.

I support a change of default skin to "Vector", I believe that "Refreshed" is difficult to use due to the absence of some sidebar links such as "Special pages".

Done

I made a mistake in my last PR. Please merge this one quick: https://github.com/Test-Wiki/mediawiki/pull/6

Void resolved it

abusefilter-private gives rights to view the IP of whatever user triggered that filter when viewing an abuse log entry. The intended right may have been abusefilter-view-private (provides ability to view private abuse filters) or abusefilter-log-private (provides ability to view AbuseLog entries of filters marked as private). Either way, anyone with abusefilter-modify (given to sysops) has the ability to view (and modify) all filters (including private).
As such, I've merged the PR; the right does not belong with the oversight toolset.

OS is used by Stewards and we never use it as CheckUser. It find to be able to change private filters. Also that link is not releated.

I added a github PR here.

I have one as well.

I err recently acquired a wikimedia cloak in case you guys need a wikimedia cloaked user for something

All sysadmins get dB access now that we’re on a VPs.

Done