I've just installed it into my Monobook, it's excellent. Wikipedia:WikiProject User scripts will tell you how to get it included in the list of scripts.
You may want to consider using the Article Wizard to help you create articles.
A tag has been placed on Xymon, requesting that it be speedily deleted from Wikipedia. This has been done under section G11 of the criteria for speedy deletion, because the page seems to be unambiguous advertising which only promotes a company, product, group, service or person and would need to be fundamentally rewritten in order to become an encyclopedia article. Please read the guidelines on spam and Wikipedia:FAQ/Business for more information.
If you think that this notice was placed here in error, you may contest the deletion by adding {{hang on}} to the top of the page that has been nominated for deletion (just below the existing speedy deletion, or "db", tag; if no such tag exists, then the page is no longer a speedy delete candidate and adding a hang-on tag is unnecessary), coupled with adding a note on the talk page explaining your position, but be aware that once tagged for speedy deletion, if the page meets the criterion, it may be deleted without delay. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the page that would render it more in conformance with Wikipedia's policies and guidelines. If the page is deleted, you can contact one of these administrators to request that the administrator userfy the page or email a copy to you. Eeekster (talk) 02:29, 10 March 2011 (UTC)[reply]
You may prevent the proposed deletion by removing the {{proposed deletion/dated}} notice, but please explain why in your edit summary or on the article's talk page.
Hmm. Now none of them seem to be working (they were earlier). Getting the error message: "No webservice. The URI you have requested, /jackbot/snottywong/afdstats.html, is not currently serviced." Thanks. Mojoworker (talk) 01:02, 17 May 2014 (UTC)[reply]
I don't know why the webservice process has stopped, maybe I should restart it by cron every two hours....
Concerning the few tools out of order like the graph, I couldn't repair it in less than one hour, but I can let the volunteers have on look if they have a Labs account. JackPotte (talk) 07:53, 17 May 2014 (UTC)[reply]
Salut Jack. I was wondering if you could take another look at the tool you migrated. Snottywong's adminscore tool still doesn't seem to be working. It seems like some of the other issues you mentioned above might have been fixed. You might want to check out Wikipedia:Wikimedia Labs/Toolserver replacements. Merci beaucoup ! - tucoxn\talk23:30, 4 July 2014 (UTC)[reply]
I've installed the good version of numpy and it's working on my PC. But with the huge Wikipedia database, the URL returns 504 Gateway Time-out. So I should remove or migrate some functions (eg: Python threads, PHP...). JackPotte (talk) 15:33, 15 August 2014 (UTC)[reply]
Because even in shell this simple query takes several minutes: SELECT MIN(rev_timestamp) FROM revision WHERE rev_user_text='JackPotte';JackPotte (talk) 20:55, 21 August 2014 (UTC)[reply]
SELECT COUNT(*) FROM revision WHERE rev_page like 'Articles for deletion/%' and rev_page not like 'Articles_for_deletion/Log/%' and rev_user_text='JackPotte';
Patrols
1 min 42.08 s
select count(*) from logging where log_type="patrol" and log_action="patrol" and log_user_text="JackPotte" and log_namespace=0 and log_deleted=0;
Why don't you use some data that is already farmed (perhaps faster) using other tools that were re-created recently? Block count, namespaces, recent activity, and patrols (4 of the longer calls) are all available from this page (I think missing edit summaries can be calculated from there, too). Non-redirect articles created can be calculated from info on this page. That still leaves the 3 admin-area calls, which are all long. I haven't though much about this but I'll let you know if I come up with any easier solutions. - tucoxn\talk01:07, 26 August 2014 (UTC)[reply]
La plupart des images que j'avais placées dans mes wikilivres (en particulier "Mathématiques avec Python et Ruby" ont été supprimées par Krd qui les trouve mal licenciées pour commons. Y a-t-il un moyen de les récupérer? Si oui, comment? Si non, que faire (réécrire les wikibooks sans images)?
I'm afraid that we've reached the server limit with this time out. So we must rewrite the script, maybe on Xtools (if you know any volunteer he can access to the code). JackPotte (talk) 11:51, 23 November 2014 (UTC)[reply]
Thank you for your contributions. Please mark your edits, such as your recent edits to MongoDB, as "minor" only if they are minor edits. In accordance with Help:Minor edit, a minor edit is one that the editor believes requires no review and could never be the subject of a dispute. Minor edits consist of things such as typographical corrections, formatting changes or rearrangement of text without modification of content. Additionally, the reversion of clear-cut vandalism and test edits may be labeled "minor". Edit in question.Dodi 8238 (talk) 17:57, 11 June 2015 (UTC)[reply]
Hi Jack. After months of asking around, Cyberpower678 tells me that you are the go-to peson for all the tools in this suite: [2]. Scottywong originally made then for us when he was part of the team that was researching solutions to improve RfA and NPP. We now have major policy proposals lined up for quite a while now and we can't launch them until we have data that can only be produced by these relatively simple tools. Is there anything you can do to get them up and running properly? Regards, --Kudpung กุดผึ้ง (talk) 03:17, 8 October 2015 (UTC)[reply]
Hello, actually I still don't have the time to modify them in the next six months, that's why I had asked for Cyberpower678 help.
Thanks Jack. Looks like we'll have to find someone - we can't wait another six months on top of the 9 months already just spent trying to find out who does what. I looked at Phabricatr but as a non IT person I don't understand a word of it. --Kudpung กุดผึ้ง (talk) 14:20, 8 October 2015 (UTC)[reply]
Sorry, Jack, I unfortunately don't have the time to commit to maintaining scripts in a language I don't even have experience with.—cyberpowerChat:Limited Access03:44, 9 October 2015 (UTC)[reply]
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited List of catchphrases, you added a link pointing to the disambiguation page Clash of the Titans. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Hello! I added information about unwanted calls (spam) to a telephone article in russian wiki. Russian rules allow user to know who had been calling him during period of a time in past and other characterictics of activity from his telephone which he have. "Listing of calls of stationary phone can be received at office of the telephone company where it is necessary to provide the passport (passport of the citizen of Russia) confirming that you are the owner of this phone. Specification of stationary phone contains information on long distance and trunk calls (including - my note): about quantity, duration of telephone conversations, about their cost"How to get a listing of calls, Tamara Kovalenko, 18 February, 2013 (ru). It s a way of finding a spam caller phone (except «Calling Line Identification») and publication an information about that in wikipedia gives users a knowledge and a kind of the safety. I don't know full information about rules of this procedure in France. And my french is lower than poor and I don't see source document (reference) intuitively. If you want, you may add this information to a telephone article. You can use duckduckgo.com for finding information about that quickly. Maybe I will do this procedure later when my french will be better. RippleSax (talk) 14:17, 27 February 2016 (UTC)[reply]
I'm not sure if this is the correct place to bring this up, but I was just reminded over at WP:VPT that you're "in charge" of Scotty Wong's former tools like the RfA Vote Counter. In the case of the RfA Vote Counter, it seems to be slightly malfunctioning lately – e.g. in my own entry, it's counting two recently closed RfA's as "Not closed yet". Just thought you should know in case you wanted to look into it and see if there's a quick "fix" for that... TIA! --IJBall (contribs • talk) 02:01, 20 March 2016 (UTC)[reply]
Hello, JackPotte. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
The BAG Newsletter is now the Bots Newsletter, per discussion. As such, we've subscribed all bot operators to the newsletter. You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list.
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Code folding, you added a link pointing to the disambiguation page Vim. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
I found your name at Category:User js (probably because you posted the corresponding userbox on your user page), in the level-unspecified list of JavaScript programmers.
I was wondering how experienced you are at JavaScript, and whether you might be interested in getting involved with developing user scripts, hobnobbing with other JavaScript programmers, and organizing and improving JavaScript articles and support pages.
The WikiProject also organizes every resource it can find about JavaScript out there, such as articles, books, tutorials, etc. See our growing Reference library. If you know of any good ones, please add them.
If you would like to join the JavaScript WikiProject, feel free to add your name to the participants list.
Here is the 4th issue of the Bots Newsletter (formerly the BAG Newletter). You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list.
21 inactive bots have been deflagged (see discussion).
WP:BOTISSUE has been updated to mention that BAG members can act as neutral mediators in bot-related disputes.
WP:INTERWIKIBOT has been updated to reflect the post-February 2013 practice of putting interwiki links on Wikidata, rather than on Wikipedia (see discussion).
Hello, JackPotte. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Here is the 5th issue of the Bots Newsletter (formerly the BAG Newletter). You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list.
While there were no large-scale bot-related discussion in the past few months, you can check WP:BOTN and WT:BOTPOL (and their corresponding archives) for smaller issues that came up.
The edit summary limit has been increased to 1000 characters (see T6715). If a bot you operate relied on the old truncation limit (255 characters), please review/update your code, as overly long summaries can be disruptive/annoying. If you want to use extra characters to have more information in your edit summary, please do so intelligently.
You will soon be able to ping users from the edit summary (see T188469). If you wish to use this feature in your bot, please do so intelligently.
Here is the 6th issue of the Bots Newsletter. You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list.
Highlights for this newsletter include:
ARBCOM
Nothing particular important happened. Those who care already know, those who don't know wouldn't care. The curious can dig ARBCOM archives themselves.
BAG
There were no changes in BAG membership since the last Bots Newsletter. Headbomb went from semi-active to active.
In the last 3 months, only 3 BAG members have closed requests - help is needed with the backlog.
{{Automated tools}}, a new template linking to user-activated tools and scripts has been created. It can be used in articles previews, and can be placed on any non-mainspace page/template (e.g. {{Draft article}}) to provide convenient links to editors.
AWB 5.10.0.0 is out, after nearly 20 months without updates. If you run an old version, you will be prompted to install the new version automatically. See the changelog for what's new. Note that the next version will require .NET Framework 4.5. Many thanks to Reedy and the AWB team.
BotWatch, "a listing of editors that have made >2 edits per minute [without] a bot flag", is being developed by SQL (see discussion).
Hello, JackPotte. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Here is the 7th issue of the Bots Newsletter, a lot happened since last year's newsletter! You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list.
BAG members are expected to be active on Wikipedia to have their finger on the pulse of the community. After two years without any bot-related activity (such as posting on bot-related pages, posting on a bot's talk page, or operating a bot), BAG members will be retired from BAG following a one-week notice. Retired members can re-apply for BAG membership as normal if they wish to rejoin the BAG.
We thank former members for their service and wish Madman a happy retirement. We note that Madman and BU Rob13 were not inactive and could resume their BAG positions if they so wished, should their retirements happens to be temporary.
Activity requirements: BAG members now have an activity requirement. The requirements are very light, one only needs to be involved in a bot-related area at some point within the last two years. For purpose of meeting these requirements, discussing a bot-related matter anywhere on Wikipedia counts, as does operating a bot (RFC).
Copyvio flag: Bot accounts may be additionally marked by a bureaucrat upon BAG request as being in the "copyviobot" user group on Wikipedia. This flag allows using the API to add metadata to edits for use in the New pages feed (discussion). There is currently 1 bot using this functionality.
Mass creation: The restriction on mass-creation (semi-automated or automated) was extended from articles, to all content-pages. There are subtleties, but content here broadly means whatever a reader could land on when browsing the mainspace in normal circumstances (e.g. Mainspace, Books, most Categories, Portals, ...). There is also a warning that WP:MEATBOT still applies in other areas (e.g. Redirects, Wikipedia namespace, Help, maintenance categories, ...) not explicitely covered by WP:MASSCREATION.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hello! Voting in the 2021 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 6 December 2021. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Graphs are unavailable due to technical issues. There is more info on Phabricator and on MediaWiki.org.
BRFA activity by month
Welcome to the eighth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Maintainers disappeared to parts unknown... bots awakening from the slumber of æons... hundreds of thousands of short descriptions... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.
Our last issue was in August 2019, so there's quite a bit of catching up to do. Due to the vast quantity of things that have happened, the next few issues will only cover a few months at a time. This month, we'll go from September 2019 through the end of the year. I won't bore you with further introductions — instead, I'll bore you with a newsletter about bots.
Overall
Between September and December 2019, there were 33 BRFAs. Of these, Y 25 were approved, and 8 were unsuccessful (N2 3 denied, ? 3 withdrawn, and 2 expired).
TParis goes away, UTRSBot goes kaput: Beeblebroxnoted that the bot for maintaining on-wiki records of UTRS appeals stopped working a while ago. TParis, the semi-retired user who had previously run it, said they were "unlikely to return to actively editing Wikipedia", and the bot had been vanquished by trolls submitting bogus UTRS requests on behalf of real blocked users. While OAuth was a potential fix, neither maintainer had time to implement it. TParis offered to access to the UTRS WMFLabs account to any admin identified with the WMF: "I miss you guys a whole lot [...] but I've also moved on with my life. Good luck, let me know how I can help". Ultimately, SQL ended up in charge. Some progress was made, and the bot continued to work another couple months — but as of press time, UTRSBot has not edited since November 2019.
Curb Safe Charmer adopts reFill: TAnthonypointed out that reFill 2's bug reports were going unanswered; creator Zhaofeng Li had retired from Wikipedia, and a maintainer was needed. As of June 2021, Curb Safe Charmer had taken up the mantle, saying: "Not that I have all the skills needed but better me than nobody! 'Maintainer' might be too strong a term though. Volunteers welcome!"
Graphs are unavailable due to technical issues. There is more info on Phabricator and on MediaWiki.org.
BRFA activity by month
Welcome to the ninth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Vicious bot-on-bot edit warring... superseded tasks... policy proposals... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.
After a long hiatus between August 2019 and December 2021, there's quite a bit of ground to cover. Due to the vastness, I decided in December to split the coverage up into a few installments that covered six months each. Some people thought this was a good idea, since covering an entire year in a single issue would make it unmanageably large. Others thought this was stupid, since they were getting talk page messages about crap from almost three years ago. Ultimately, the question of whether each issue covers six months or a year is only relevant for a couple more of them, and then the problem will be behind us forever.
Of course, you can also look on the bright side – we are making progress, and this issue will only be about crap from almost two years ago. Today we will pick up where we left off in December, and go through the first half of 2020.
Overall In the first half of 2020, there were 71 BRFAs. Of these, Y 59 were approved, and 12 were unsuccessful (with N2 8 denied, ? 2 withdrawn, and 2 expired).
January 2020
Yeah, you're not gonna be able to get away with this anymore.
A new Pywikibot release dropped support for Python 3.4, and it was expected that support for Python 2.7 would be removed in coming updates. Toolforge itself planned to drop Python 2 support in 2022.
On February 1, some concerns were raised about ListeriaBot performing "nonsense" edits. Semi-active operator Magnus Manske (who originally coded the Phase II software|precursor of MediaWiki) was pinged. Meanwhile, the bot was temporarily blocked for several hours until the issue was diagnosed and resolved.
In March, a long discussion was started at Wikipedia talk:Bot policy by Skdb about the troubling trend of bots "expiring" without explanation after their owners became inactive. This can happen for a variety of reasons -- API changes break code, hosting providers' software updates break code, hosting accounts lapse, software changes make bots' edits unnecessary, and policy changes make bots' edits unwanted. The most promising solution seemed to be Toolforge hosting (although it has some problems of its own, like the occasional necessity of refactoring code).
A discussion on the bot noticeboard, "Re-examination of ListeriaBot", was started by Barkeep49, who pointed out repeated operation outside the scope of its BRFA (i.e. editing pages in mainspace, and adding non-free images to others). Some said it was doing good work, and others said it was operating beyond its remit. It was blocked on April 10; the next day it was unblocked, reblocked from article space, reblocked "for specified non-editing actions", unblocked, and indeffed. The next week, several safeguards were implemented in its code by Magnus; the bot was allowed to roam free once more on April 18.
Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable [...] External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it.
May 2020
We heard you like bots, so we made a bot that reports the status of your bots, so now you can use bots while you use bots
MajavahBot 3, an impressively meta bot task, was approved this month for maintaining a list of bots running on the English Wikipedia. The page, located at User:MajavahBot/Bot status report, is updated every 24 hours; it contains a list of all accounts with the bot flag, as well as their operator, edit count, last activity date, last edit date, last logged action date, user groups and block status.
In July 2017, Headbomb made a proposal that a section of the Wikipedia:Dashboard be devoted to bots and technical issues. In November 2019, Lua code was written superseding Legobot's tasks on that page, and operator Legoktm was asked to stop them so that the new code could be deployed. After no response to pings, a partial-block of Legobot for the dashboard was proposed. Some months later, on June 16, Headbomb said: "A full block serves nothing. A partial block solves all current issues [...] Just fucking do it. It's been 3 years now." The next day, however, Legoktm disabled the task, and the dashboard was successfully refactored.
On June 7, RexxS blocked Citation bot for disruptive editing, saying it was "still removing links after request to stop". A couple weeks later, a discussion on the bots noticeboard was opened, saying "it is a widely-used and useful bot, but it has one of the longest block logs for any recently-operating bot on Wikipedia". While its last BRFA approval was in 2011, its code and functionality had changed dramatically since then, and AntiCompositeNumber requested that BAG require a new BRFA. Maintainer AManWithNoPlan responded that most blocks were from years ago (when it lacked a proper test suite), and problems since then had mostly been one-off errors (like a June 2019 incident in which a LTA had "weaponized" the bot to harass editors).
David Tornheim opened a discussion about whether bots based on closed-source code should be permitted, and proposed that they not. He cited a recent case in which a maintainer had said "I can only suppose that the code that is available on GitHub is not the actual code that was running on [the bot]". Some disagreed: Naypta said that "I like free software as much as the next person, and I strongly believe that bot operators should make their bot code public, but I don't think it should be that they must do so".
Yes I can confirm that it's abnormal, and persists even after the webservice reboot. Apparently the new Wikimedia Kubernetes back-end does not support CGI anymore (or its config is tricky), neither does Grid Engine. So the entire Snottywong's Tools should probably be rewritten or shutdown. I can share the source code if anyone volunteers: https://github.com/JackPotte/snottywong. JackPotte (talk) 19:27, 8 June 2022 (UTC)[reply]