This is an archive of past discussions with User:Enterprisey. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
That got me L235. My jaw dropped in genuine surprise but also mild concern that it would flop being, you know, an hour and 7 minutes after the RfA close --TheSandDoctorTalk00:13, 27 January 2019 (UTC)
Hi Enterprisey, I have closed your request for adminship as successful. Congratulations for both your successful nomination and for your place on WP:RFX200 - an impressive feat after your landslide of a victory! As always, the administrators' reading list is worth reading and the new admin help pages are most certainly available if you feel that you might require some practice with the tools in a safe environment prior to applying them elsewhere on the project. Good luck! Acalamari23:07, 26 January 2019 (UTC)
By my calculations, for this RfA to fail now you need 135 more opposes in about 15 minutes. That's an oppose every six seconds. The software can't cope with that, even allowing for edit conflicts so ... welcome to the admin corps, carefully, and please apply for interface admin so I can resign my privs (as I won't need them if you have them). Ritchie333(talk)(cont)23:01, 26 January 2019 (UTC)
Scripts++ Newsletter – Issue 2
News and updates associated with user scripts from the past month (January 2019).
Hello everyone and welcome to the second issue of the new Wikipedia Scripts++ Newsletter:
There was a recent village pump thread about either Enterprisey's or Equazcion's "Script Installer" tool becoming a gadget. It wasn't officially closed, and so far neither has become a gadget. Stay tuned for updates.
Congratulations Enterprisey! Your RfA was successful. You are now an administrator on the English Wikipedia. I hope you have just as happy a time editing in the future as you did before your RfA. You may want to look at the admin guide to read up on any tools you are unfamiliar with.
As a Floridian I have just completed the recount, and I regret to report that I am unable to certify three of the votes as proper and correct. -Ad Orientem (talk) 00:17, 27 January 2019 (UTC)
Felicitations on your RfA and welcome to the team. There is a learning curve but it's not too steep. Always remember that you can lean on any of us if you have questions or are not sure how to proceed in a given situation. But for now, I'd just take a few minutes to enjoy the triumph. Maybe some nice scotch and a good cigar... -Ad Orientem (talk) 00:00, 27 January 2019 (UTC)
Congratulations on your successful RFA! I'm a little late, but that won't stop me from torturing you passing on what the puppy told me Katie after my Katie's RFA passed – eleven long, sordid, hasn't-Katie-gone-away-yet years ago:
Remember you will always protect the wrong version. (I got nothing here. It's inevitable. I'd be shocked if you haven't done it already.)
Remember you must always follow the rules, except for when you ignore them. Without exception, you will pick the wrong one to do. (See #5.)
Remember to assume good faith and not bite. Remember that when you are applying these principles most diligently, you are probably dealing with a troll. (You'll attract many more of those now, because mop. They must like to drink the dirty water in the bucket.)
Use the block ability sparingly. Enjoy the insults you receive when you do block, because really, what else is there to live for?
Remember that when you make these errors, someone will be more than happy to point them out to you in dazzling clarity and descriptive terminology. It will not be a personal attack because we are admins and, therefore, we are all rouge anyway.
Finally, remember to contact me if you ever need assistance, and I will do what I am able.
DISCLAIMER: This humor does not reflect the official humor of Wikipedia, the Wikimedia Foundation, or Jimbo Wales, because if it did, it would be much, much better. All rights released under GFDL.
AFCH doubling-up on comments when switching modes
See this edit. I first selected Reject, then switched to Decline (or maybe it was the other way around?). I was surprised when I switched that it lost the text I had begun to type, so I re-entered it. It looks like it kept both bits of text around and saved them both as distinct comments. -- RoySmith(talk)22:18, 23 January 2019 (UTC)
I definitely have to go in and fix up that code. I'll have some free time in the next few days to maybe look at these issues. Thanks for reporting this bug! Enterprisey (talk!) 06:47, 24 January 2019 (UTC)
I updated the script so that it'll stop adding duplicate comments. For now, (because it's harder to fix), it will keep deleting your text when you switch between decline vs reject, but I do plan to fix that in the future. Enterprisey (talk!) 01:32, 30 January 2019 (UTC)
The reply-link newsletter, issue 1
Hey. I got your message. Thanks for starting the newsletter! Just wanted to say that your message should link to your user page, etc, not to User:MediaWiki message delivery. To ensure this doesn't fall through the cracks, I write my message, sign it, and then "subst:" it to recipients, to ensure that its my signature that is added, not the bot's. Just an fyi. --DannyS712 (talk) 02:47, 30 January 2019 (UTC)
Don't know if you missed this, you've been editing your talk page a bunch since I posted, so just wanted to make sure you saw it. Thanks, --DannyS712 (talk) 07:52, 1 February 2019 (UTC)
Yup, I was thinking of splitting out the red-link part into another script, which might take a bit more time but will probably be a better solution than showing some irrelevant stuff on more pages. ETA... soonish (tm) as usual. Enterprisey (talk!) 07:58, 1 February 2019 (UTC)
A beer for you!
Barkeep49 just pointed me at your copyvio revdel request tool - simple, easy to use, generally splendid, thank you. Congrats on a well-deserved RfA vote too. Cheers GirthSummit (blether)21:40, 29 January 2019 (UTC)
Hi, Enterprisey, I have a suggestion for an enhancement to the script. Yesterday I declined an unblock request and hoped that a blank decline would insert {{subst:Decline reason here}}, so I then had to go back and add it myself. I'm not sure which would be a better approach, but if the script could either load that as a default decline reason (as with the default decline code attached to {{unblock}}), or to have a checkbox to select it, it would make the script slightly more helpful. Thanks for this and your other excellent tools. —DoRD (talk) 13:26, 31 January 2019 (UTC)
Good idea! Yes, I do intend to make that script a lot more useful, now that I actually have it installed and thus have to look at it on a regular basis . A checkbox is a great idea. Enterprisey (talk!) 07:41, 1 February 2019 (UTC)
Hey. I saw your newest update. I think you made a small mistake with var CCLEAN_TPL = "Cclean";. Since this is used to make the link (line 132), shouldn't it be var CCLEAN_TPL = "Template:Cclean";? I mention this because when I clicked on the link, it took me to Cclean, rather than what I assume you meant (Template:Cclean). Thanks, --DannyS712 (talk) 07:08, 5 February 2019 (UTC)
I think it was actually correct before Special:diff/881960888. At least, now it's telling me that every userscript is insecure. Though if this script is to become a gadget, I question if it's a good idea to allow installation of non-User, non-MediaWiki pages at all; that kind of defeats the purpose of having intadmins in the first place, and the current text that pops up doesn't explain to new users why it's insecure. Suffusion of Yellow (talk) 23:25, 5 February 2019 (UTC)
MediaWiki will not load user scripts that are non-user non-mediawiki unprotected pages, and the script will not allow those to be installed; non-user non-mediawiki fully-protected pages are loaded, but may be deprecated soon, so the script allows those to be installed but shows a warning. At least, that's how it's supposed to work I'll take another look at it to fix the remaining related bugs. Enterprisey (talk!) 01:42, 6 February 2019 (UTC)
Y Looks good! Thanks. My point about the gadget is that people who haven't kept up on recent events won't realize why it's a bad idea to install a "fully" protected script that 827 people accounts can edit, so perhaps the gadget version should eliminate that possibility entirely, even if MediaWiki continues to allow this. Or at least, the warning should be more detailed. But I assume there will be a second discussion somewhere before this is made a gadget, so I'll bring it up there. Suffusion of Yellow (talk) 02:26, 6 February 2019 (UTC)
Script idea
Obviously, from your RfA, I know that you are good at developing user scripts. Do you think you could make (or is there already) a script which allows one to close discussions like ANI threads more easily and write closing statements without having to go through the editing window? SemiHypercube01:25, 22 January 2019 (UTC)
If anyone wants, they can do it. I'm thinking of perhaps a button on each section (level 2 and level 3 headings) like OneClickArchiver which opens up a dialog box (similar to Twinkle) which allows one to enter a closing statement, possibly an option of a setting the "status" parameter of Template:Archive top and how far down the close goes. (as sometimes the whole section could be closed, or just the top of the L2 section to the first L3 header) If it's too hard to understand, please ask, sometimes it's hard for me to describe what I'm thinking into words. SemiHypercube02:05, 22 January 2019 (UTC)
This would be really helpful (to whoever works on it) - I started to dip my foot into the world of closing RfCs and found it surprisingly tough Nosebagbear (talk) 18:39, 23 January 2019 (UTC)
You are invited to join the Wikimedia NYC community for our monthly "WikiWednesday" evening salon (7-9pm) and knowledge-sharing workshop at Metropolitan New York Library Council in Midtown Manhattan. Is there a project you'd like to share? A question you'd like answered? A Wiki* skill you'd like to learn? Let us know by adding it to the agenda.
We will also follow up on plans for recent and upcoming edit-a-thons, museum and library projects, education initiatives, and other outreach activities.
(note this month we will be meeting in Midtown Manhattan, not at Babycastles)
We especially encourage folks to add your 5-minute lightning talks to our roster, and otherwise join in the "open space" experience! Newcomers are very welcome! Bring your friends and colleagues! --Wikimedia New York City Team 08:59, 27 February 2019 (UTC)
Art+Feminism’s sixth-annual MoMA Wikipedia Edit-a-thon will take place at the Dorothy and Lewis B. Cullman Education and Research Building, The Museum of Modern Art, New York, 4 West 54 Street, on Saturday, March 2, 2019 from 10 a.m. to 6 p.m. People of all gender identities and expressions are encouraged to attend.
On a sadder note, just this morning we said goodbye to Abelmoschus Esculentus, a prolific script writer.
We are three months in to this newsletter and everything is going great–keep on creating amazing new scripts! Who knows–maybe the scripts will take over one day... --DannyS712 (talk) 17:59, 28 February 2019 (UTC)
Pending requestsWikiProject Portals is looking for some help making scripts...
Hello Enterprisey, you have probably other things on your mind with your RfA (glad to see it is going so well), but here is an additional suggestion to save a bit more time for copyvio maintenance editors: when using cv-revdel it would be very helpful to also substitute Template:Cclean in the article's talkpage, with the URL value from your script interface given as parameter for "url=" (see template documentation). This additional message should be optional though, as sometimes such an additional info might not make sense and just bloat the talkpage (maybe trigger it with a checkbox somewhere near the URL field in your script UI). Of course this is just a random idea, but it would be great if it would be possible to semi-automate this additional step as well. GermanJoe (talk) 19:56, 26 January 2019 (UTC)
Thanks a lot, @Enterprisey:. A quick test in userspace works fine. One minor nitpick though: the script-generated message lacks a preceding CRLF compared to a manual subst with "New section". Not quite sure why the subst call via API would behave differently, but could you add another line-break please to separate the previous message? GermanJoe (talk) 09:25, 5 February 2019 (UTC)
It's only a miniscule bug of course, @Enterprisey:, but could you fix the linebreak formatting for the talkpage message please when you got some time? Just pinging once, in case you overlooked the message. GermanJoe (talk) 08:34, 1 March 2019 (UTC)
No problem at all, you probably have a lot on your plate. A quick test looked fine - thank you for fixing this. GermanJoe (talk) 09:15, 2 March 2019 (UTC)
Really old :) I just use the provided version on toolforge, because I wrote the original in early 2016, back when I didn't know what a venv was. I'll update it soon, don't worry! Enterprisey (talk!) 04:21, 3 March 2019 (UTC)
Following discussions at the Bureaucrats' noticeboard and Wikipedia talk:Administrators, an earlier change to the restoration of adminship policy was reverted. If requested, bureaucrats will not restore administrator permissions removed due to inactivity if there have been five years without a logged administrator action; this "five year rule" does not apply to permissions removed voluntarily.
Technical news
A new tool is available to help determine if a given IP is an open proxy/VPN/webhost/compromised host.
Arbitration
The Arbitration Committee announced two new OTRS queues. Both are meant solely for cases involving private information; other cases will continue to be handled at the appropriate venues (e.g., WP:COIN or WP:SPI).
paid-en-wpwikipedia.org has been set up to receive private evidence related to abusive paid editing.
checkuser-en-wpwikipedia.org has been set up to receive private requests for CheckUser. For instance, requests for IP block exemption for anonymous proxy editing should now be sent to this address instead of the functionaries-en list.
StraussInTheHouse, it's almost certainly due to the table. The tool looks for more "cohesive" comments, and doesn't like it very much when there's a table or other large object in the middle of a comment. Maybe you could move the table to after your signature, and add a bolded "comment" tag before it? Enterprisey (talk!) 22:33, 20 March 2019 (UTC)
The Wikimedia Foundation has requested help with the testing of and feedback on a new tool for "Automated article section recommendations" for stub articles. See the village pump notice for more.
You are invited to join the Wikimedia NYC community for our monthly "WikiWednesday" evening salon (7-9pm) and knowledge-sharing workshop at Metropolitan New York Library Council in Midtown Manhattan. Is there a project you'd like to share? A question you'd like answered? A Wiki* skill you'd like to learn? Let us know by adding it to the agenda.
We will also follow up on plans for recent and upcoming edit-a-thons, museum and library projects, education initiatives, and other outreach activities.
(note this month we will be meeting in Midtown Manhattan, not at Babycastles)
We especially encourage folks to add your 5-minute lightning talks to our roster, and otherwise join in the "open space" experience! Newcomers are very welcome! Bring your friends and colleagues! --Wikimedia New York City Team 21:05, 3 April 2019 (UTC)
Translat-a-thon NYC 2019 @ LaGuardia Community College is hosting the second annual Wikipedia Translatathon! At this event on Thursday evening and during the day Friday this week, anyone from the public is invited to LaGuardia to join students, professors, and CUNY faculty in translating Wikipedia articles among any languages which attendees understand. Themes for this event include public health and the history of New York City.
New York City has a large immigrant population and great diversity of speakers of various languages. Among all schools in New York City, LaGuardia has the highest percentage of immigrant students, the highest percentage of students who speak a language other than English as their first language, and the greatest representation of language diversity. It is a strength of LaGuardia that it can present "Wikipedia translatathons", which are Wikipedia translation events.
(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)
News and updates associated with user scripts from the past month (April 2019). Hello everyone and welcome to the 5th issue of the Wikipedia Scripts++ Newsletter:
Recently, several Wikipedia admin accounts were compromised. The admin accounts were desysopped on an emergency basis. In the past, the Committee often resysopped admin accounts as a matter of course once the admin was back in control of their account. The committee has updated its guidelines. Admins may now be required to undergo a fresh Request for Adminship (RfA) after losing control of their account.
What do I need to do?
Only to follow the instructions in this message.
Check that your password is unique (not reused across sites).
Check that your password is strong (not simple or guessable).
Enable Two-factor authentication (2FA), if you can, to create a second hurdle for attackers.
How can I find out more about two-factor authentication (2FA)?
Administrator account security (Correction to Arbcom 2019 special circular)
ArbCom would like to apologise and correct our previous mass message in light of the response from the community.
Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.
We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.
XTools Admin Stats, a tool to list admins by administrative actions, has been revamped to support more types of log entries such as AbuseFilter changes. Two additional tools have been integrated into it as well: Steward Stats and Patroller Stats.
Arbitration
In response to the continuing compromise of administrator accounts, the Arbitration Committee passed a motion amending the procedures for return of permissions (diff). In such cases, the committee will review all available information to determine whether the administrator followed "appropriate personal security practices" before restoring permissions; administrators found failing to have adequately done so will not be resysopped automatically. All current administrators have been notified of this change.
Following a formal ratification process, the arbitration policy has been amended (diff). Specifically, the two-thirds majority required to remove or suspend an arbitrator now excludes (1) the arbitrator facing suspension or removal, and (2) any inactive arbitrator who does not respond within 30 days to attempts to solicit their feedback on the resolution through all known methods of communication.
@QEDK: It's the line breaks in the AFD !vote, I had a similar challenge with my !vote at Wikipedia:Articles for deletion/Shania (given name). The workaround for now is to state or repeat the bolded !vote on the same line as your signature. On a related note, there's an editor, I forgot who it is, who will end nominations with something like: "Therefor I believe this is a delete. ~~~~" AfD Stats parses that as a delete !vote, not a nomination. SamSailor18:49, 8 May 2019 (UTC)
You are invited to join the Wikimedia NYC community for our monthly "WikiWednesday" evening salon (7-9pm) and knowledge-sharing workshop at Metropolitan New York Library Council in Midtown Manhattan. Is there a project you'd like to share? A question you'd like answered? A Wiki* skill you'd like to learn? Let us know by adding it to the agenda.
Featuring this month a presentation by Interference Archive guests, and a group discussion on the role of activist archives and building wiki content based on ephemeral publications and oral histories.
To close off the night, we'll also have Wikidojo - a group collaborative writing activity / vaudeville!
We will also follow up on plans for recent and upcoming edit-a-thons, museum and library projects, education initiatives, and other outreach activities.
(note this month we will be meeting in Midtown Manhattan, not at Babycastles)
We especially encourage folks to add your 5-minute lightning talks to our roster, and otherwise join in the "open space" experience! Newcomers are very welcome! Bring your friends and colleagues! --Wikimedia New York City Team 17:10, 16 May 2019 (UTC)
(You can subscribe/unsubscribe from future notifications for NYC-area events by adding or removing your name from this list.)
To some degree, I am a little worried that I might be way out of my depth in discussing all these hypothetical software changes, but for this particular topic, I think there are fairly good reasons that creating a new interface altogether wouldn't be reinventing the wheel with respect to reply-link.
For starters, reply-link is heavily customized specifically to suit the community processes of the English Wikipedia, and contains several hard-coded page names and even some section headers. A lot of text is matched solely using regular expressions, which would be problematic for things that change significantly between wikis like date formats and templates. Even if it were to to be generalized, it would probably take a fair amount of work to adapt it to the 700 other Wikimedia projects. Something developed as a full MediaWiki extension by the WMF would also normally have to go through the bureaucracy involved (e.g. security audits) and would have to be usable on any MediaWiki installation right from the outset, including in right-to-left languages.
You also have the issue of having to adapt this somewhat fragile user script over hundreds or thousands of different wikis' conversational conventions. Even on the English Wikipedia, there are quite a lot of experienced users who seem to be completely unaware that they're not indenting comments correctly and that the little bullet doesn't really affect how anyone reads their comments. This is mainly relevant because reply-link easily fails if users don't format their comments correctly (and might even fail for some values of "correctly"). With a complete interface, you would be able to circumvent this due to users being encouraged to reply inline (in contrast to the current situation of users having to find the user script and choose to opt-in), as well as errors being either glaringly visible or smoothed over by the software in most cases.
These two reasons alone would make a new extension much more attractive to the WMF and possibly more convenient to implement, because an interface that has to be re-customized for deployment on each site and only works 95% of the time is not a very good interface, particularly if the intention is that users shouldn't have to learn to use an alternative. I could go on about accessibility, design, the visual editor and adding new sections (though some of these are flaws of the core software, not reply-link). Reply-link is ultimately a band-aid that serves to lessen some of the glaring flaws of a part of MediaWiki that wasn't designed properly (if at all) from the outset. This doesn't mean that reply-link isn't any good – in fact, I think it's surprisingly good given the limitations that it has to work around – but it's still a band-aid, and it would be better if it weren't necessary at all. Jc86035 (talk) 23:38, 20 May 2019 (UTC)