Wikiversity:Notices for custodians/Archive/6

Account Hacking
I just received a notice that there have been multiple failed attempts to log into my account from a new device. Anyone who might be a target for harassment needs to make sure you have two-factor authentication enabled. -- Dave Braunschweig (discuss • contribs) 01:18, 6 December 2019 (UTC)
 * Thanks for the heads up. Do you yourself have 2fa enabled? --DannyS712 (discuss • contribs) 01:23, 6 December 2019 (UTC)
 * Yes, everywhere I can, and with a physical Yubikey where those are accepted. -- Dave Braunschweig (discuss • contribs) 04:32, 6 December 2019 (UTC)
 * I also recently received a "Multiple failed attempts to log in to Wikiversity" notification. --mikeu talk 06:36, 6 December 2019 (UTC)

Temporary interface adminship requested
Hi. Can I be flagged as an interface admin for a few days? I'd like to edit to remove the categories / apply nowiki tags to suppress the templates (and then delete Category:Wikipedians who use RC script and Category:VoA scripted admins, which each only have 1 page right now).
 * User:Atcovi/common.js
 * User:Alex43223/monobook.js
 * User:Alkhowarizmi/common.js
 * User:Digitalme/admin/monobook.js
 * User:Gbaor/monobook.js
 * User:Hillgentleman/monobook.js
 * User:Juandev (usurped)/vector.js

Thanks, --DannyS712 (discuss • contribs) 08:03, 6 December 2019 (UTC)


 * Anyone have any objections or concerns? -- Dave Braunschweig (discuss • contribs) 14:37, 6 December 2019 (UTC)


 * I have no objections or concerns, this seems reasonable to me. I have a slight preference for a short descriptive note about the reasons for the changes on the off-chance that any of the participants have questions about modification to their userspace js. Otherwise, please go ahead. I support, --mikeu talk 02:56, 7 December 2019 (UTC)

I've added you to Interface Administrators for seven days, mostly just to make sure I don't forget about this if no one else responds. Before making any changes, please expand (a little) on the changes necessary. I know it's clear to you, but not as obvious to the rest of us. Thanks! -- Dave Braunschweig (discuss • contribs) 04:20, 7 December 2019 (UTC)
 * The pages are currently in one or more categories that they shouldn't be in (or in the case of the 2 categories I noted above, categories with only 1 item that I think should be deleted) due to templates or categories that are meant to be a part of the script. By applying nowiki tags (within javascript comments), I should be able to stop the categorization without altering the underlying code. I'll leave this for a bit in case there are objections. --DannyS712 (discuss • contribs) 05:33, 7 December 2019 (UTC)
 * Thanks. Perhaps include a link to this discussion in the edit summary. --mikeu talk 16:47, 7 December 2019 (UTC)
 * now --DannyS712 (discuss • contribs) 03:33, 9 December 2019 (UTC)
 * ✅ except for User:Hillgentleman/monobook.js - not sure what I thought the issue was. --DannyS712 (discuss • contribs) 03:41, 9 December 2019 (UTC)

CheckUser
See Requests for CheckUser. -- Dave Braunschweig (discuss • contribs) 04:43, 7 December 2019 (UTC)

Extensive Use of User Space for Non-English Resources
Please take a look at Special:PrefixIndex/User%3ASaltrabook%2F. There are 274 subpages, most of which are in Spanish. I have repeatedly suggested that the user move these resources to es.wikiversity, to no effect. Does anyone else have concerns about this use of en.wikiversity? -- Dave Braunschweig (discuss • contribs) 23:35, 7 December 2019 (UTC)


 * Yes, I see this as something that should be moved to es or beta. We are the English Wikiversity and it is inapppropiate to have extensive non-english resources here, --mikeu talk 05:03, 9 December 2019 (UTC)


 * I agree with mikeu --Guy vandegrift (discuss • contribs) 03:53, 10 December 2019 (UTC)

I've created an abuse filter and custom messages to prevent this user from creating new pages. I've left a message directing that the non-English content be moved to Wikiversidad or another hosting site. If desired, the filter is designed to support adding other users we may want to allow to edit, but restrict from creating new pages. -- Dave Braunschweig (discuss • contribs) 04:42, 10 December 2019 (UTC)

Temporary interface adminship requested (again)
Hi. As I noted in Request custodian action/Archive/21, the current contribs-range gadget is broken. Indeed, the source, w:User:Splarka/contribsrange.js, says as much. I'd like to be flagged to:


 * 1) Remove the current contribs range gadget
 * 2) Recreate the gadget by syncing from enwiki's version (w:MediaWiki:Gadget-contribsrange.js)
 * 3) Continue developing the gadget (there is a todo tag, and the code is pretty old, so I have some improvement ideas, like using mw.Api instead of mw.loader.load[ing] the query. I'll test everything in a user script before deploying site-wide)

Reviewing Interface administrators, I can confirm:
 * The edits to the gadget should be uncontrovertial
 * I have two-factor authentication enabled.

Thanks, --DannyS712 (discuss • contribs) 01:44, 25 December 2019 (UTC)


 * Can you test the user script first and then we turn on IA when you're ready to replace the current gadget? -- Dave Braunschweig (discuss • contribs) 02:56, 25 December 2019 (UTC)
 * Well, I'm ready to replace it with enwiki's, which works. I subscribe to "perfection is the enemy of good" - use enwiki's for now, improve later rather than improve as a user script now and then replace. I have a lot of different coding work to do (I'm developing tests for my global watchlist script at the moment) so I'd rather fix the gadget now and then improve it when I have time. --DannyS712 (discuss • contribs) 02:59, 25 December 2019 (UTC)


 * Sorry, it wasn't clear to me that they were separate efforts. I don't see any issues with implementing what Wikipedia already has. IA membership granted for 1 week, assuming you'll disable again when you're done. Thanks! -- Dave Braunschweig (discuss • contribs) 21:01, 25 December 2019 (UTC)
 * Okay, its up and running - if you have the script installed you may need to disable and re-enable, but the current enwiki version was copied successfully. --DannyS712 (discuss • contribs) 21:54, 25 December 2019 (UTC)

Okay, so if you take a look at User:DannyS712 test/contribsrange.js you'll see what I'm doing - so far, there should be no change to the functionality, just cleaning it up (use some more jquery, implement some of mw:Manual:Coding conventions/JavaScript). I'm going to test it a bit, and then sync it to the gadget. Next steps: Thoughts? --DannyS712 (discuss • contribs) 11:11, 26 December 2019 (UTC)
 * Script improvements
 * Separate css into a separate file (instead of the current )
 * Continue linting to apply consistent styling
 * Declare a version 0.3 and update the notice


 * Currently, the script loads contributions with the earliest edits at the top, and the newest at the bottom. This is the opposite of Special:Contributions, which puts the newest edits at the top. I suggest reversing the order. Thoughts? --DannyS712 (discuss • contribs) 02:28, 27 December 2019 (UTC)


 * I took a quick look at it. It would take a good bit of time and testing to comment meaningfully. Is there a specific part you'd like an opinion on?
 * The next steps listed make sense. Yes, I agree that newest should be on top for consistency. -- Dave Braunschweig (discuss • contribs) 04:06, 27 December 2019 (UTC)
 * Just if you notice anything working differently than before. I'll wait a bit for the change to the order, but that should only take a few minutes to code. --DannyS712 (discuss • contribs) 04:19, 27 December 2019 (UTC)
 * I've deployed 0.2.9 - the css is now separate, at MediaWiki:Gadget-contribsrange.css - let me know if any issues arise. Next up will be the direction switch, but I'll hold off for a few more days --DannyS712 (discuss • contribs) 05:59, 31 December 2019 (UTC)
 * I was about to push the next version (mostly linting and style issues) and found out the rights had expired... can you extend them please? Happy new year, --DannyS712 (discuss • contribs) 01:23, 2 January 2020 (UTC)
 * ✅ -- Dave Braunschweig (discuss • contribs) 01:29, 2 January 2020 (UTC)

Why is this temporary? —Justin ( koavf ) ❤T☮C☺M☯ 01:42, 2 January 2020 (UTC)
 * because according to policy (which I wrote : "interface administratorship may only be granted temporarily by bureaucrats (not to exceed 2 weeks without discussion)". If this becomes an issue where I keep needing to request it for short periods, I might open a full community request for (eg) a year, like on wikispecies. --DannyS712 (discuss • contribs) 02:33, 2 January 2020 (UTC)
 * Good point but why is that restriction there? Seems unnecessary. —Justin ( koavf ) ❤T☮C☺M☯ 02:45, 2 January 2020 (UTC)
 * I've gone ahead and flipped the contributions to be newest on top. --DannyS712 (discuss • contribs) 03:38, 5 January 2020 (UTC)
 * I'm getting an odd "JavaScript parse error: Parse error: Missing ; before statement in file 'MediaWiki:Gadget-contribsrange.js' on line 51" alert, and the script isn't working, but the trace provided doesn't help, and it doesn't appear to be related - line 51 is just . Is it working for anyone else? If not, I'll file a phab task --DannyS712 (discuss • contribs) 03:57, 5 January 2020 (UTC)
 * It seems to be working for me. I see newest on top. I have the gadget enabled, and I can search for /24 and /16 on IPv4 contributions and /56 on IPv6 contributions. Using Chrome latest on macOS 10.14.6. -- Dave Braunschweig (discuss • contribs) 04:08, 5 January 2020 (UTC)
 * In that case, I'll stop for now; hopefully it starts working for me again soon. Removing the rights... --DannyS712 (discuss • contribs) 01:58, 6 January 2020 (UTC)

Temporary interface adminship requested (once more)
...to update MediaWiki:Mobile.js now that the code was moved to MediaWiki:DebateTree.js. I'm about to log off for now, but should only take a few minutes once I'm back; 24 hours should be long enough to ensure that I have a chance to update it. Thanks, --DannyS712 (discuss • contribs) 08:05, 5 February 2020 (UTC)
 * I support a trusted user making these changes. --mikeu talk 01:09, 6 February 2020 (UTC)
 * Okay, so I made the update, but I have reverted it:
 * Currently, the common.js contains a few lines that result in, when the url contains  (also works for other js targets), loading MediaWiki:DebateTree.js
 * The button in DebateTree takes the user to the same page with that parameter appending, triggering the code to load
 * The common.js function that allows this does not work in mobile.js, since common.js isn't processed for mobile views
 * Simply updating the mobile.js import to import debate tree means that it is always run for mobile users, rather than just when the request is included in the url
 * So, for now, I have reverted to the status quo. I would suggest adding the  part to mobile.js as well, to allow for the same functionality, but that could have some other consequences (it allows loading any mediawiki scripts). I don't see any dangers, but wanted to discuss before proceeding. Thoughts?
 * Mu301 granted me the rights until February 13, and I haven't removed them yet, but I'll hold off on further action for now. Thanks, --DannyS712 (discuss • contribs) 06:37, 6 February 2020 (UTC)

Maybe I'm missing something here, but it looks like MediaWiki:Mobile.js is loading a previously deleted page MediaWiki:Dialectiki.js. If it's not functional, I would be inclined to just remove it. I don't have a recommendation yet regarding the rest of this. My concern is the ""it allows loading any mediawiki scripts" part. Can you elaborate on the benefits and risks? -- Dave Braunschweig (discuss • contribs) 15:33, 8 February 2020 (UTC)
 * the withjs code, which is also present on enwiki, allows users to manually load javascript that is in the mediawiki namespace. The scripts there were put there by admins (in the past) and interface admins (currently) so the risk of a malicious script is minimal, but I haven't looked at what all the scripts are --DannyS712 (discuss • contribs) 17:58, 8 February 2020 (UTC)
 * ...so this expired without me doing anything --DannyS712 (discuss • contribs) 03:28, 15 February 2020 (UTC)

Please see Candidates for Custodianship/DannyS712 (interface administrator) for requesting longer-term access --DannyS712 (discuss • contribs) 20:00, 13 March 2020 (UTC)

Template import
Hi ! Is that possible to import this template ? Thanks in advance. Lionel Scheepmans ✉ Contact (French native speaker) 15:05, 19 March 2020 (UTC)
 * --DannyS712 (discuss • contribs) 15:08, 19 March 2020 (UTC)
 * ✅, let me know if there are any issues --DannyS712 (discuss • contribs) 15:10, 19 March 2020 (UTC)
 * Thanks DannyS712, the diplay of documentation don't work. Probably because Wikiversity miss Lionel Scheepmans ✉ Contact (French native speaker) 16:16, 21 March 2020 (UTC)

COVID resources
Please keep an eye out for questionable COVID related resources. I just moved a mainspace page to Draft:An application of phenol injection in treating coronavirus-2019. One of the people mentioned is described in news reports as "Additionally, Li Yuehua, a “divine doctor” (神医), was also investigated for asserting that he had cured Covid-19 patients using a low-cost method of acupoint injection therapy." We need to be esp. vigilant about patrolling pages on this topic to prevent bogus information from spreading. --mikeu talk 21:11, 21 March 2020 (UTC)
 * A search for this "doctor" yields no reputable sources. Good eye and I +1 this message (and will, myself, be looking out for this too as I hopefully increase in activity over the coming weeks). We do not want to be the source of misinformation in regards to a tragic pandemic (one of the worst pandemics that has ever occurred) that is claiming the lives of thousands of people across the world.


 * BTW for any curious minds, see what this has to say about this "divine treatment". —Atcovi (Talk - Contribs) 21:16, 21 March 2020 (UTC)


 * Thanks, and welcome back. I usually check global contribs when I see serious issues. A translation at zh wikiversity by this same user has been tagged for speedy. I moved a page on en wikibooks to userspace and tagged it for deletion. Also, I blanked the page here and intend to delete it in a few days. --mikeu talk 21:58, 21 March 2020 (UTC)

Proposal: Grant custodians `nuke` rights
just makes deletion easier, and is available to sysops on other projects. It simplifies mass deletion of pages created by the same user, and saves time. Is there a reason only crats have it here? --DannyS712 (discuss • contribs) 01:51, 14 April 2020 (UTC)


 * right was removed at phab:T113109. &mdash;Hasley talk  02:20, 14 April 2020 (UTC)


 * At the time it was discussed, mass delete had not been used by anyone in several years, and there was greater concern for misuse than there was need for appropriate use. Some of that concern has been addressed since then, but it's still a tool that is much easier to use than to undo, by orders of magnitude. -- Dave Braunschweig (discuss • contribs) 13:31, 14 April 2020 (UTC)
 * I just came across a time when I would have used it on some spam. I don't know if it had the feature at the time, but it includes a confirmation "are you sure" type message after you hit submit before proceeding, and if it would be helpful I can write a user script to help with the undo part --DannyS712 (discuss • contribs) 00:45, 15 April 2020 (UTC)


 * My personal perspective is that it would be more effective for you to write a user script that can help you nuke a user's contributions when you need to than it would be to give nuke abilities to nine other people, most of whom have not taken any administrative actions in the last year or more. -- Dave Braunschweig (discuss • contribs) 02:31, 15 April 2020 (UTC)


 * Such scripts already exist. See s:MediaWiki:Gadget-massdelete.js and m:User:Tks4Fish/nukeAll.js. &mdash;Hasley  talk  11:34, 15 April 2020 (UTC)

I've had the nuke button for a dozen years and I have used it exactly zero times. I've only considered using it once or twice but the circumstances never warranted taking the risk of unintended consequences. If someone were to request use of this tool I would consider it but would likely use other means to accomplish the same outcome. Can you provide a single example of nuke being the best recourse to respond to unwanted activity? I can't recall an instance where it would have been appropriate to use it. --mikeu talk 11:57, 16 April 2020 (UTC)
 * I would have used it for Special:DeletedContributions/2607:FB90:5FD2:9E35:0:1C:A60:9901, and when I saw I couldn't I opened this discussion - yes, its only 3 pages, but nuke would have saved time --DannyS712 (discuss • contribs) 13:57, 16 April 2020 (UTC)
 * Would nuke have been preferable to rollback in this case? --mikeu talk 01:05, 17 April 2020 (UTC)
 * It was page creations, so rollback wouldn't have worked --DannyS712 (discuss • contribs) 01:20, 17 April 2020 (UTC)
 * Ok, but I'm still not seeing a compelling need for this. I wouldn't have used nuke on the example you gave. Our abuse filters prevent unconfirmed users from creating too many pages. The number is rather small. The problem that nuke was designed to fix has been thwarted via other means. --mikeu talk 10:41, 20 April 2020 (UTC)

Small Wiki Toolkits
See Small wiki toolkits for a variety of tutorials on configuring and maintaining the wiki environment. Let us know if you find anything useful that we should implement. -- Dave Braunschweig (discuss • contribs) 19:44, 27 April 2020 (UTC)

Globally Banned User
After about a six month lull, we are now under attack again by a globally banned user. Please be on the lookout for any resources or comments related to boxing, fighting, Rocky, or strange links to other wikis with related comments. If possible, those with anonymous accounts should delete these contributions rather than those of us who share our real-world identities. -- Dave Braunschweig (discuss • contribs) 01:04, 10 May 2020 (UTC)
 * As far as I know my identity hasn't been compromised, so will do --DannyS712 (discuss • contribs) 02:06, 10 May 2020 (UTC)