WP:Interface administrators' noticeboard
{{Short description|Interface administrators: coordination and requests}}
|archiveheader = {{talkarchivenav}}
|maxarchivesize = 250K
|counter = 3
|minthreadsleft = 3
|minthreadstoarchive = 1
|algo = old(30d)
|archive = Wikipedia:Interface administrators' noticeboard/Archive %(counter)d
}}__NEWSECTIONLINK__{{/Header}}
__TOC__
Warning required that WebAuthn is currently unsupported by Mobile Apps
While phab:T230043 remains unimplemented, the [https://auth.wikimedia.org/enwiki/wiki/Special:Manage_Two-factor_authentication Manage Two-factor authentication] preference page should warn users that enabling Web Authentication (WebAuthn) for 2FA on their account will prevent them from logging back in on both the official Wikipedia apps for iOS and Android. Only TOTP (one-time token) is supported at this time. -- Netsnipe ► 13:19, 22 May 2025 (UTC)
:[https://auth.wikimedia.org/enwiki/w/index.php?title=Special:Manage_Two-factor_authentication&useformat=desktop] contains a fairly verbose warning already. Sohom (talk) 14:02, 22 May 2025 (UTC)
::There's no warning on the preference page itself. One has to click/scroll all the way down to Help:Two-factor_authentication#WebAuthn before they even get to it. -- Netsnipe ► 05:07, 23 May 2025 (UTC)
:::This doesn't appear to require an interface admin, as system messages are editable by admins. Feel free to open an edit request on whichever message you are concerned with. Note, we can't create new messages on pages that don't have messages - for that you would need to file a feature request. I'm not seeing any specific problem here, as Sohom noted before you can activate the experimental WebAuthn you should already know this from the other messages. — xaosflux Talk 10:45, 23 May 2025 (UTC)
::::{{Not done}}, I did some investigation, (interface-)admins cannot add a warning to the Special:Preferences page changing that will definitely require a feature request on Phabricator. I've however changed MediaWiki:Webauthn-module-description to now have a huge orange tag to make the problems more apparent as a normal admin action. Sohom (talk) 16:51, 23 May 2025 (UTC)
Req: Set my js sandbox as an actual js page
User:SMcCandlish/common.js/sandbox.js is not flagged as a .js page. MW thinks it's a regular wiki page. — SMcCandlish ☏ ¢ 😼 07:12, 29 May 2025 (UTC)
:{{done}} Izno (talk) 07:34, 29 May 2025 (UTC)
:: For future reference you could have done this yourself using Special:ChangeContentModel since you're a template editor. * Pppery * it has begun... 16:48, 29 May 2025 (UTC)
:::Changing any page to a Javascript content model requires int admin. Izno (talk) 17:34, 29 May 2025 (UTC)
:::: No, it doesn't. As long as you have editcontentmodel
access (and hence are a template editor or above) and will still be able to edit the page once you've changed the content model (hence either are the user in question or are an interface admin), then you can do it. The second requirement usually dwarfs the first one, but not here. * Pppery * it has begun... 18:21, 29 May 2025 (UTC)
Personal CSS edit blocked by filter, please review
{{resolved|No action needed. — xaosflux Talk 01:44, 8 June 2025 (UTC)}}
If an IA has a moment, could one of ya'll take a look at Wikipedia:Edit_filter/False_positives/Reports#Atomixe? I've fixed the filter to exempt personal JS/CSS in the future, but I can't implement the edit itself to the user's CSS page. EggRoll97 (talk) 22:09, 7 June 2025 (UTC)
:So if the filter is no longer in the way, why can't the user do this now? That edit is a rather "bad idea" to a common.css page, but if they really want to whatever. — xaosflux Talk 22:15, 7 June 2025 (UTC)
::Fair enough actually, didn't occur to me that they can in fact do this themselves. EggRoll97 (talk) 22:25, 7 June 2025 (UTC)