Wikipedia:Interface administrators' noticeboard

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Welcome to the interface administrators' noticeboard

This is the interface administrator noticeboard, for discussion of interface administrators and coordination of edits to the interface.

Currently only interface administrators can undelete JS/CSS pages, if you have an uncontroversial undelete or deleted version retrieval request, please list it below.

Individual requests for edits to interface or user JavaScript/CSS pages should continue be made on their respective talk pages.

Interface administrators'
noticeboard archives:
1 2 3 4 5 6 7 8 9 10
0 interface-protected edit requests
Page Tagged since Protection level Last protection log entry
Updated as needed. Last updated: 08:54, 10 June 2019 (UTC)

Not being able to access my common.js due to other account being redirected[edit]

Resolved: There were likely easier ways to do this, but this was the quickest way to close this out. — xaosflux Talk 23:49, 19 May 2019 (UTC)

So I had requested that my username on both of my accounts so that it would be HawkAussie (main) and AussieHawk (secondary) instead of Matt294069 (main) and HawkAussie (secondary) that it was. This went well until I tried to access my common.js for this account and it's stating that it's not available due to the redirect from HawkAussie to AussieHawk. So can you please give me to access to this for me. HawkAussie (talk) 23:24, 19 May 2019 (UTC)

@HawkAussie: for redirected pages you will need to log in with the actual account that is associated with the page to make .js edits. If you just want it deleted you can make a speedy deletion request on its talk page as any admin can delete the page. — xaosflux Talk 23:31, 19 May 2019 (UTC)
@Xaosflux: I have tried using the other account but that is not working as it's only accessible for this account and the interface team. And I attempted to use a speedy deletion request but because it's a redirect for my other account, that won't be able to apply either. HawkAussie (talk) 23:37, 19 May 2019 (UTC)
@HawkAussie: ok - we don't really have a way to "give you access" - do you want User:HawkAussie/common.js deleted? — xaosflux Talk 23:39, 19 May 2019 (UTC)
Or just blanked out? — xaosflux Talk 23:40, 19 May 2019 (UTC)
@Xaosflux: Properly blanked out so that it will be able to work on it. HawkAussie (talk) 23:41, 19 May 2019 (UTC)
 Done @HawkAussie: it has been blanked, let me know if you need anything else on this. — xaosflux Talk 23:43, 19 May 2019 (UTC)
Thanks for that, I am able to edit it now. HawkAussie (talk) 23:44, 19 May 2019 (UTC)

Inactive interface administrators 2019-05-28[edit]

The following interface administrator(s) are inactive:

— JJMC89 bot 23:19, 28 May 2019 (UTC)

 Donexaosflux Talk 23:28, 28 May 2019 (UTC)
eraser Undone as there was 1 deleted edit on 2019-05-09. — xaosflux Talk 23:33, 28 May 2019 (UTC)
The re-load should make the bot be quiet for a month at least! — xaosflux Talk 23:37, 28 May 2019 (UTC)
I think it checks when the bit was granted, and won't report based on using the tools until they've been an int-admin for six months. Good thing RS edited their talk, so there's no issue of having it removed in one month after only technically having the perm for two months! ~ Amory (utc) 16:15, 2 June 2019 (UTC)
I mean, realistically, this person HAS been inactive - but the policy is very forgiving, and only admins can audit this. I've got no concerns for this access for this person, but do think these things should all require "publicly accessible" logs/edits for transparency. — xaosflux Talk 01:20, 3 June 2019 (UTC)
For CSS/JS edits, yes it waits until they've been an iadmin for 6 months. For the 2 months with no edits or logged actions, it doesn't. So we could be back here on 28 August at the earliest. — JJMC89(T·C) 02:02, 4 June 2019 (UTC)