Feed The Beast Wiki:Administrators' noticeboard/Archive/2013

From Feed The Beast Wiki
Jump to: navigation, search

Checklist for opening up the wiki

Overall progress:
 
100% (19/19)
100% (19/19)
Setup progress:
 
100% (10/10)
100% (10/10)
Testing progress:
 
100% (4/4)
100% (4/4)
Finalization progress:
 
100% (3/3)
100% (3/3)
Post-finalization progress:
 
100% (2/2)
100% (2/2)

Setup stage

  • Yes check.pngDone. Set up CAPTCHA on the wiki.
  • Yes check.pngDone. Set up an IRC channel for the wiki.
  • Yes check.pngDone. Clean up the Community portal
  • Yes check.pngDone. Protect important pages.
  • Yes check.pngDone. Require email confirmation.
  • Yes check.pngDone. Configure ConfirmEdit CAPTCHA trigger settings.
  • Yes check.pngDone. Setup group permissions.
  • Yes check.pngDone. Add the Nuke and Renameuser extensions.
  • Yes check.pngDone. Remove unused accounts.
  • Yes check.pngDone. Inform team members about their new responsibilities.

Testing stage

  • Yes check.pngDone. Test user rights.
  • Yes check.pngDone. Test account creation.
  • Yes check.pngDone. Test email confirmation.
  • Yes check.pngDone. Test CAPTCHA triggers.

Finalization stage

  • Yes check.pngDone. Grant group 'user': edit.
  • Yes check.pngDone. Grant group '*' (all): createaccount.
  • Yes check.pngDone. Rebuild statistics.

Post-finalization stage

  • Yes check.pngDone. Announce on forums.
  • Yes check.pngDone. Start recruiting new team members.

Response time (must not exceed 1 day)

Vandalism and Spam
  • Yes check.pngPassed. New page spam/vandalism response time (delete): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Spam/Vandalism response time (revert): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Consecutive spam/vandalism response time (rollback): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Excessive spam/vandalism response time (protect): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. User spam/vandalism response time (notify).
  • Yes check.pngPassed. User spam/vandalism response time (warn).
  • Yes check.pngPassed. User spam/vandalism response time (block) (>5 counts): Min: 76min Average: 166.4min Max: 288min
  • Yes check.pngPassed. Excessive user spam/vandalism response time (nuke): Min: N/A Average: N/A Max: N/A
Quality assessment
  • Yes check.pngPassed. Tag bad articles with template (community): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Tag bad articles with template (staff)
  • Yes check.pngPassed. Fix/Resolve (community): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Fix/Resolve (staff): Min: N/A Average: N/A Max: N/A
Maintenance
  • Yes check.pngPassed. RFD (normal): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. RFC (deletion): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Patrol (revision)
  • Yes check.pngPassed. Patrol (new page)
Requests and Help
  • Yellow check.pngSkipped. Help desk (community): Min: N/A Average: N/A Max: N/A
  • Yellow check.pngSkipped. Help desk (staff/sysop): Min: N/A Average: N/A Max: N/A
  • Yellow check.pngSkipped. IRC help (community): Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. IRC help (staff/sysop): Min: N/A Average: N/A Max: N/A
  • Yellow check.pngSkipped. Admin noticeboard: Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Staff noticeboard: Min: N/A Average: N/A Max: N/A
  • Yellow check.pngSkipped. Translator noticeboard: Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Bot operator noticeboard: Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. Issues: Min: N/A Average: N/A Max: N/A
  • Yes check.pngPassed. RFC: Min: N/A Average: N/A Max: N/A
  • Yellow check.pngSkipped. Skin bugs: Min: N/A Average: N/A Max: N/A
  • Pictogram voting delete.pngInactive. AFC submissions (accept): Min: N/A Average: N/A Max: N/A
  • Pictogram voting delete.pngInactive. AFC submissions (review): Min: N/A Average: N/A Max: N/A
  • Pictogram voting delete.pngInactive. AFC submissions (merge): Min: N/A Average: N/A Max: N/A

New extensions proposals

  • Yes check.pngInstalled. mw:Extension:TitleBlacklist
  • Yes check.pngInstalled. mw:Extension:AbuseFilter
  • Yes check.pngInstalled. mw:Extension:FlaggedRevs
    • Discussion
      • I like this extension because staff can review and assess the quality of the article at the same time, administrators can also stabilize the quality of pages with a tool included. -- Jinbobo SysOp · BotOp · talk · contribs 11:29, 4 July 2013 (UTC)
    • Poll
      • This poll will end in 1 day.
      • Support: Please add {{Status|done|Support.}} and a comment if you want this extension to be installed.
      • Against: Please add {{Status|done|Against.}} and a comment if you want this extension to not be installed.
      • Conditional support: Please add {{Status|partlydone|Conditional support.}} and a comment if you want this extension to be installed only under some circumstances.
      • Yes check.pngSupport. I think this is a good idea. -- auris331
      • Yes check.pngSupport. This should be good, provided we can quickly learn the new system. -- AgentTadpole Staff · talk · contribs 12:24, 4 July 2013 (UTC)

Blacklisting new account names

We have figured out a few username patterns that spambots like to use, we will be blocking these usernames that match these regex patterns in the near-future, use Jinbobo's Blocked username list to test the following regex, by default, patterns are case insensitive:

  • Usernames with 4 or more consecutive consonants (Easy fix for real users is to add a space between words?)
    • Pattern: .*((?=[a-z])[^aeiou0-9]){3}(?=[a-z])[^aeiou0-9]+.*
  • Usernames with 3 or more consecutive capital letters (Case sensitive)
    • Pattern: .*[A-Z]{2}[A-Z]+.*
  • Usernames with 2 or more consecutive capital letters at the end (Case sensitive)
    • Pattern: .*[A-Z]{2}
  • Usernames with 2 or more consecutive numbers
    • Pattern: .*[0-9]{2}[0-9]+.*
  • Usernames containing the following words: car, limo, home, house, service, move, moving, guide, clean.
    • Pattern: .*(car|limo|home|service|move|moving|guide|clean).*
  • Usernames with 20+ letters.
    • Pattern: .*.{20}.*

Upgrading mediawiki software to 1.22.2

This checklist can be viewed at [1] after the database has been locked.

Pre-upgrade checklist

  • Yes check.pngDone. Backup database.
  • Yes check.pngDone. Backup files.
  • Yes check.pngDone. Download & extract mw 1.22.2 tarball.
  • Yes check.pngDone. Configure staging site.
  • Yes check.pngDone. Lock database.
  • Yes check.pngDone. Backup database again.
  • Yes check.pngDone. Backup files again.

Upgrade checklist

Post-upgrade checklist

Deployment checklist

  • Yes check.pngDone. Unlock database.
  • Yes check.pngDone. Deploy.

Allowing image uploads for "normal" people

Is there any reason why image uploads are disabled for "normal" people? It is quite annoying to have to post an image URL and wait for a sysop to upload it for you (like for Writing Desk and Talk:Writing Desk). It's not a big vandalism problem - I've been on a rather frequented wiki with image uploads active for anonymous, and have only seen a single case of upload vandalism in a few months. --dgelessus (talk · contribs) 20:59, 11 October 2013 (BST)

In order to upload images, you simply have to be auto-confirmed, which means a few edits patrolled by the wiki team, and then you'll be able to upload images without any issues Retep998 (talk) 00:46, 12 October 2013 (BST)
actually you have to get 50 edits and your account must be 1 week old to get autoconfirmed. The reason you see no vandal on other wikis is because there are more active admins there. -- Jinbobo 04:34, 12 October 2013 (BST)
Let's say I've been actively watching the recent changes/logs, so I would've noticed anyway. Also, is "patrolled" the same as "checked" on this wiki, or is that separate? And will the annoying captchas be gone once I am autoconfirmed? --dgelessus (talk · contribs) 10:37, 12 October 2013 (BST)
yes being autoconfirmed will allow you to skip CAPTCHA tests. Checking is limited to pages in the main and template namespace. -- Jinbobo 16:17, 12 October 2013 (BST)

Server not responding after template edits

okay, you probably already noticed this - every time a template is edited the server stops responding for some time afterwards. Probably because it's updating all the pages, but normally the job queue should do that over time. --dgelessus (talk · contribs) 15:09, 12 October 2013 (BST)

can you tell me what you were editing that caused this? -- Jinbobo 16:17, 12 October 2013 (BST)
Template:P and Template:Infobox. Not sure if Template:Navbox RedPower 2 did it as well... It only lasted a few minutes though. The server problems I posted about on the forums a few weeks ago were probably the same thing. --dgelessus (talk · contribs) 18:03, 12 October 2013 (BST)
I'll try work with the web team to figure out this problem, but no promises, we've tried some stuff already but none seems to work. -- Jinbobo 19:27, 12 October 2013 (BST)
Okay, I'm no expert on this, but have you already tried setting the job queue's rate lower? AFAIK that's what updates the templates transcluded onto pages. --dgelessus (talk · contribs) 19:36, 12 October 2013 (BST)
ok, will take a look when I have the time. -- Jinbobo 21:21, 12 October 2013 (BST)