Some people are lobbying for changing the article's name to Macedonian without any qualifier. As it seems, a number of these people come from the Macedonian/Macedonian Slav wikipedia project. It seemed only fair to attract the attention of people possibly from the other side of the story. I hope that this message is of interest to you, if not please accept my apologies. Dstork 02:35, 18 Jun 2005 (UTC)Newcomer 05:45, 22 Jun 2005 (UTC)
I'm also listed in the category and I think that the list is useful while most people are on the list and not the category. I think you can be bold and put the category tag to all user pages of users listed on that page (but not to anyone who is not listed). --geraki17:08, 23 November 2005 (UTC)[reply]
Hey Geraki, I nominated the Thessaloniki article as a candidate for the Article Improvement Drive. The article is so very close to becoming a featured article so I thought it was appropriate that it be a candidate for the AID. Please feel free to vote at the AID page here. Thanks! Oh, also, I was wondering how knowledgeable you were on Phanar in Istanbul...I wanted to get a group of editors to work on that article since it is the seat of the Ecumenical Patriarch. --Caponer00:59, 6 March 2006 (UTC)[reply]
Thanks for uploading Image:Benizelos.jpg. I notice the 'image' page currently doesn't specify who created the content, so the copyright status is unclear. If you have not created this media yourself then there needs to be an argument why we have the right to use the media on Wikipedia (see copyright tagging below). If you have not created the media yourself then it needs to be specified where it was found, i.e., in most cases link to the website where it was taken from, and the terms of use for content from that page.
If the media also doesn't have a copyright tag then one should be added. If you created/took the picture, audio, or video then the {{GFDL-self}} tag can be used to release it under the GFDL. If you believe the media qualifies as fair use, consider reading fair use, and then use a tag such as {{Non-free fair use in|article name}} or one of the other tags listed at Wikipedia:Image copyright tags#Fair_use. See Wikipedia:Image copyright tags for the full list of copyright tags that you can use.
If you have uploaded other media, consider checking that you have specified their source and copyright tagged them, too. You can find a list of 'image' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "Image" from the dropdown box. Note that any unsourced and untagged images will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you. Jkelly17:42, 15 April 2006 (UTC)[reply]
An image you uploaded, Image:Thessaloniki seal.png, was tagged with the {{coatofarms}} copyright tag. This tag was deleted because it does not actually specify the copyright status of the image. The image may need a more accurate copyright tag, or it may need to be deleted. If the image portrays a seal or emblem, it should be tagged as {{seal}}. If you have any questions, ask them at Wikipedia:Media copyright questions. -- 23:31, 29 December 2006 (UTC)
To arthro gia ton Germano karavangeli dexetai sinexos epithesi apo pseutika ID!! Pos mporoume na to prostateusoume???
Assistance needed!
Seleukosa09:30, 18 September 2007 (UTC)[reply]
Thanks for uploading Image:Benizelos.jpg. I noticed the 'image' page specifies that the image is being used under fair use, but its use in Wikipedia articles fails our first fair use criterion in that it illustrates a subject for which a freely licensed image could reasonably be found or created that provides substantially the same information. If you believe this image is not replaceable, please:
If you have uploaded other fair use media, consider checking that you have specified how these images fully satisfy our fair use criteria. You can find a list of 'image' pages you have edited by clicking on this link. Note that even if you follow steps 1 and 2 above, fair use images which could be replaced by free-licensed alternatives will be deleted 2 days after this notification (7 days if not used in an article), per our Fair Use policy. If you have any questions please ask them at the Media copyright questions page. Thank you. Calliopejen113:47, 3 October 2007 (UTC)[reply]
Thanks for uploading Image:Benizelos.jpg. The media description page currently specifies that it is non-free and may only be used on Wikipedia under a claim of fair use. However, it is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the media was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that media for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
If you have uploaded other unlicensed media, please check whether they're used in any articles or not. You can find a list of 'image' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "Image" from the dropdown box. Note that all non-free media not used in any articles will be deleted after seven days, as described on criteria for speedy deletion. Thank you. BetacommandBot20:42, 10 October 2007 (UTC)[reply]
I don't generate the interwiki geodata myself; this work is done by Stefan Kühn, who parses multiple Wikipedia dumps and cross-correlates them -- you can find his interwiki geodata dataset at Wikipedia:WikiProjekt Georeferenzierung (English language page on de: Wikipedia). There may be some encoding issues regarding this file: please contact me if you have problems decoding it.
As an alternative, I have some dump analysis tools I use on the en: Wikipedia dumps, which could be fairly straightforwardly adapted to extract geotags for pages which have interwiki links to gr: However, since they perform a complete parse of all templates in the dump, they are rather slow: you will need to download several gigabytes of compressed dump, and then spend about 5 to 6 hours of CPU time parsing a complete dump. However, once the dumps have been parsed into a simple intermediate file represenation of the template data, analysis and re-analysis passes over the data extracted are easy and fast. -- The Anome09:44, 12 October 2007 (UTC)[reply]
Just to thank you for finding this picture of Benny Carter. He is a great artist and I truly enjoy his music. I still have difficulties understanding the procedure and rules for posting images that do not create violation of some sort.
Too bad you could not find a picture with Benny and his alto saxophone. For example, I would have preferred this one. Same photographer, I believe.
Hi, unfortunately I didn't find this picture but the picture found me. The fact is that I responded to an e-mail (to [email protected]) by the photographer complaining about the use of one of his Benny Carter photos without his permission. Portraits of individuals usually are not accepted as "fair use" per the fair use guidelines. The photo would have been deleted, but Mr. Edward Berger was kind enough to release under a free license, another picture of his choice. You should always ask the photographer's permission to use a photo in order to not create violations. If you'd like another picture, please ask Mr. Edward Berger to release it under a free license, and then the picture has to be uploaded with the appropriate license tag and Mr. Berger mentioned as the author. GerakiTL08:20, 16 September 2008 (UTC)[reply]
Thank you so much. With those few well chosen words, you have taught me more about how to put photos of people on Wikipedia than the usual lengthy policy documents that I have consulted. You are a great teacher. -- Jazzeur (talk) 13:58, 16 September 2008 (UTC)[reply]
Hey. Your monobook.js page is currently showing up in the candidates for speedy deletion category, probably because of your db tagging script (specifically, having "{{db|" stuff "}}" on the page may still cause it to be listed. I suggest editing the script - consider replacing one '{' with a variable containing the same. Cheers, Ale_Jrbtalk22:28, 22 January 2009 (UTC)[reply]
Hi there. Unless an image is a blatant copyright violation and you can prove as much with a URL, it is not eligible for speedy deletion as you have been tagging them. If the copyright status is in doubt, it's better to tag it with {{subst:nsd}}. If, after 7 days, the uploader doesn't add a source where we can verify the copyright status, it is deleted automatically. --Laser brain(talk)16:46, 28 May 2009 (UTC)[reply]
Hello, Geraki. Please check your email; you've got mail! It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
My name is Victor Grigas and I'm a Storyteller at the Wikimedia Foundation. We're exploring new ways to explain why Wikipedia is so special and we’ve started a Wikipedia Stories Project, where we’re chronicling the inspiring stories of the Wikipedia community, especially editors and active contributors in the movement like you. I'll be traveling to Wikimania next month to collect stories for our 2011 Fundraiser. While there I'd love the chance to meet with you and hear your thoughts about Wikipedia. We’ll have a schedule of available times for you to sign up if you’re interested, but right now, we’d like to make the initial contact to gauge your interest. Please let me know by emailing me at [email protected] or responding on my talk page (http://en.wikipedia.org/wiki/User:VgrigasWMF)
Thanks to all of you who have commented on the New Page Triage talkpage. If you haven't had a chance yet, check it out; we're discussing some pretty interesting ideas, both from the Foundation and the community, and moving towards implementing quite a few of them :).
In addition, on Tuesday 13th March, we're holding an office hours session in #wikimedia-office on IRC at 19:00 UTC (11am Pacific time). If you can make it, please do; we'll have a lot of stuff to show you and talk about, including (hopefully) a timetable of when we're planning to do what. If you can't come, for whatever reason, let me know on my talkpage and I'm happy to send you the logs so you can get an idea of what happened :). Regards, Okeyes (WMF) (talk) 23:56, 8 March 2012 (UTC)[reply]
Thanks to everyone who attended our first office hours session; the logs can be found here, if you missed it, and we should be holding a second one on Thursday, 22 March 2012 at 18:00 UTC in #wikimedia-office. I hope to see you all there :).
In the meantime, I have greatly expanded the details available at Wikipedia:New Page Triage: there's a lot more info about precisely what we're planning. If you have ideas, and they aren't listed there, bring them up and I'll pass them on to the developers for consideration in the second sprint. And if you know anyone who might be interested in contributing, send them there too!
Sorry for the radio silence, guys :). I just wanted to let you know that we're planning on starting a new round of hand coding, which you can sign up for here. This will be the final round (honest!), and is basically because we found some really interesting results from the last round that blew our collective mind. It's important to check that they weren't a fluke, though, and so a bit more work is needed.
If you have any questions, drop a note on my talkpage - and if you know anyone who would be interested in participating, please tell them about it! We'll be holding an IRC training session in #wikimedia-office at 18:00 UTC on the 21st of March to run through the tool and answer any questions you may have. Thanks! :) Okeyes (WMF) (talk) 00:42, 14 March 2012 (UTC)[reply]
I appreciate this isn't quite what you signed up for, but I figured as people who are already pretty good at evaluating whether material is useful or not useful through Special:NewPages, you might be interested :). Over the last few months we've been developing the new Article Feedback Tool, which features a free text box. it is imperative that we work out in advance what proportion of feedback is useful or not so we can adjust the design accordingly and not overwhelm you with nonsense.
This is being done through the Feedback Evaluation System (FES), a tool that lets editors run through a stream of comments, selecting their value and viability, so we know what type of design should be promoted or avoided. We're about to start a new round of evaluations, beginning with an office hours session tomorrow at 18:00 UTC. If you'd like to help preemptively kill poor feedback, come along to #wikimedia-office and we'll show you how to use the tool. If you can't make it, send me an email at okeyeswikimedia.org or drop a note on my talkpage, and I'm happy to give you a quick walkthrough in a one-on-one session :).
Hey! Big update on what the developers have been working on, and what is coming up:
coding
Fixes for the "moved pages do not show up in Special:NewPages" and "pages created from redirects do not show up in Special:NewPages" bugs have been completed and signed off on. Unfortunately we won't be able to integrate them into the existing version, but they will be worked into the Page Triage interface.
Coding has been completed on three elements; the API for displaying metadata about the article in the "list view", the ability to keep the "patrol" button visible if you edit an article before patrolling it, and the automatic removal of deleted pages from the queue. All three are awaiting testing but otherwise complete.
All other elements are either undergoing research, or about to have development started. I appreciate this sounds like we've not got through much work, and truthfully we're a bit disappointed with it as well; we thought we'd be going at a faster pace :(. Unfortunately there seems to be some 24-72 hour bug sweeping the San Francisco office at the moment, and at one time or another we've had several devs out of it. It's kind of messed with workflow.
Stuff to look at
We've got a pair of new mockups to comment on that deal with the filtering mechanism; this is a slightly updated mockup of the list view, and this is what the filtering tab is going to look like. All thoughts, comments and suggestions welcome on the NPT talkpage :). I'd also like to thank the people who came to our last two office hours sessions; the logs will be shortly available here.
I've also just heard that the first functional prototype for enwiki will be deployed mid-April! Really, really stoked to see this happening :). We're finding out if we can stick something up a bit sooner on prototype.wiki or something.
I appreciate there may be questions or suggestions where I've said "I'll find out and get back to you" and then, uh. not ;p. I sincerely apologise for that: things have been a bit hectic at this end over the last few weeks. But if you've got anything I've missed, drop me a line and I'll deal with it! Further questions or issues to the usual address. Thanks, Okeyes (WMF) (talk) 17:11, 3 April 2012 (UTC)[reply]
Hey all. My regular(ish) update on what's been happening with the new Article Feedback Tool.
Hand-coding
As previously mentioned, we're doing a big round of hand-coding to finalise testing :). I've been completedly bowled over by the response: we have 20 editors participating, some old and some new, which is a new record for this activity. Many thanks to everyone who has volunteered so far!
Coding should actively start on Saturday, when I'll be distributing individualised usernames and passwords to everyone. If you haven't spoken to me but would be interested in participating, either drop me a note on my talkpage or email okeyeswikimedia.org. If you have spoken to me, I'm very sorry for the delay :(. There were some toolserver database issues beyond our control (which I think the Signpost discussed) that messed with the tool.
New designs and office hours
Our awesome designers have been making some new logos for the feedback page :) Check out the oversighter view and the monitor view to get complete coverage; all opinions, comments and suggestions are welcome on the talkpage :).
We've also been working on the Abuse Filter plugin for the tool; this will basically be the same as the existing system, only applied to comments. Because of that, we're obviously going to need slightly different filters, because different things will need to be blocked :). We're holding a special office hours session tomorrow at 22:00 UTC to discuss it. If you're a regex nut, existing abuse filter writer, or simply interested in the feedback tool and have suggestions, please do come along :).
The article will be discussed at Wikipedia:Articles for deletion/Greek Wikipedia until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion template from the top of the article. —Justin (koavf)❤T☮C☺M☯22:46, 26 April 2012 (UTC)[reply]
Hey Geraki; just a quick note to let you know that we'll be holding an Office Hours session at 18:00 UTC (don't worry, I got the time right ;p) on 4th May in #wikimedia-office. This is to show off the almost-finished feedback page and prep it for a more public release; I'm incredibly happy to have got to this point :). Hope to see you there! Regards, Okeyes (WMF) (talk) 03:55, 30 April 2012 (UTC)[reply]
Hey Geraki :). A quick update on how things are going with the New Page Triage/New Pages Feed project. As the enwiki page notes, the project is divided into two chunks: the "list view" (essentially an updated version of Special:NewPages) and the "article view", a view you'll be presented with when you open up individual articles that contains a toolbar with lots of options to interact with the page - patrolling it, adding maintenance tags, nominating it for deletion, so on.
On the list view front, we're pretty much done! We tried deploying it to enwiki, in line with our Engagement Strategy on Wednesday, but ran into bugs and had to reschedule - the same happened on Thursday :(. We've queued a new deployment for Monday PST, and hopefully that one will go better. If it does, the software will be ready to play around with and test by the following week! :).
On the article view front, the developers are doing some fantastic work designing the toolbar, which we're calling the "curation bar"; you can see a mockup here. A stripped-down version of this should be ready to deploy fairly soon after the list view is; I'm afraid I don't have precise dates yet. When I have more info, or can unleash everyone to test the list view, I'll let you know :). As always, any questions to the talkpage for the project or mine. Thanks! Okeyes (WMF) (talk) 23:29, 5 May 2012 (UTC)[reply]
Hey Geraki! We've finally finished the NPT prototype and deployed it on enwiki. We'll be holding an office hours session on the 16th at 21:00 in #wikimedia-office to show it off, get feedback and plot future developments - hope to see you there! Okeyes (WMF) (talk) 03:38, 13 May 2012 (UTC)[reply]
Hey all :). A notification that the prototype for the New Pages Feed is now live on enwiki! We had to briefly take it down after an unfortunate bug started showing up, but it's now live and we will continue developing it on-site.
The page can be found at Special:NewPagesFeed. Please, please, please test it and tell us what you think! Note that as a prototype it will inevitably have bugs - if you find one not already mentioned at the talkpage, bring it up and I'm happy to carry it through to the devs. The same is true of any additions you can think of to the software, or any questions you might have - let me know and I'll respond.
Just a quick update on what we've been working on:
The centralised feedback page is now live! Feel free to use it and all other feedback pages; there's no prohibition on playing around, dealing with the comments or letting others know about it, although the full release comes much later. Let me know if you find any bugs; we know it's a bit odd in Monobook, but that should be fixed in our deployment this week.
On Thursday, 7th June we'll be holding an office hours session at 20:00 UTC in #wikimedia-office. We'll be discussing all the latest developments, as well as what's coming up next; hope to see you all there!
Those of you who hand-coded feedback; I believe I contacted you all about t-shirts. If I didn't, drop me a line and I'll get it sorted out :).
Hey all :). First-off, thanks to everyone for all their help so far; we're coming up to a much wider deployment :). Starting at the end of this month, and scaling up until 3 July, AFT5 will begin appearing on 10 percent of articles. For this release we plan on sending out a CentralNotice that every editor will see - and for this, we need your help :). We've got plans, we know how long it's going to run for, where it's going to run...but not what it says. If you've got ideas for banners, give this page a read and submit your suggestion! Many thanks, Okeyes (WMF) (talk) 16:26, 19 June 2012 (UTC)[reply]
So, big news this week - on Tuesday, we ramped up to 5 percent of articles :). There's been a lot more feedback (pardon the pun) as I'm sure you've noticed, and to try and help we've scheduled a large number of office hours sessions, including one this evening at 22:00 UTC in the #wikimedia-officeconnect channel, and another at 01:00 UTC for the aussies amongst us :). I hope to see some of you there - if any of you can't make it but have any questions, I'm always happy to help.
Hey again all :). So, some big news, some small news, some good news, some bad news!
On the "big news" front; we've now deployed AFT5 on to 10 percent of articles, This is pretty awesome :). On the "bad news", however, it looks like we're having to stop at 10 percent until around September - there are scaling issues that make it dangerous to deploy wider. Happily, our awesome features engineering team is looking into them as we speak, and I'm optimistic that the issues will be resolved.
For both "small" and "good" news; we've got another office hours session. This one is tomorrow, at 22:00 UTC in #wikimedia-officeconnect - I appreciate it's a bit late for Europeans, but I wanted to juggle it so US east coasters could attend if they wanted :). Hope to see you all there!
Hey all. Some quick but important updates on what we've been up to and what's coming up next :).
The curation toolbar, our Wikimedia-supported twinkle replacement. We're going to be deploying it, along with a pile of bugfixes, to wikipedia on 9 August. After a few days to check it doesn't make anything explode or die, we'll be sticking up a big notice and sending out an additional newsletter inviting people to test it out and give us feedback :). This will be followed by two office hours sessions - one on Tuesday the 14th of August at 19:00 UTC for all us Europeans, and one on Wednesday the 15th at 23:00 UTC for the East Coasters out there :). As always, these will be held in #wikimedia-office; drop me a note if you want to know how to easily get on IRC, or if you aren't able to attend but would like the logs.
I hope to see a lot of you there; it's going to be a big day for everyone involved, I think :). I'll have more notes after the deployment! Okeyes (WMF) (talk) 20:02, 3 August 2012 (UTC)[reply]
First, you'll note that all the project titles have now changed to the Page Curation prefix, rather than having the New Pages Feed prefix. This is because the overarching project name has changed to Page Curation; the feed is still known as New Pages Feed, and the Curation Toolbar is still the Curation Toolbar. Hopefully this will be the last namechange ;p.
On the subject of the Curation Toolbar (nice segue, Oliver!) - it's now deployed on Wikipedia. Just open up any article in the New Pages Feed and it should appear on the right. It's still a beta version - bugs are expected - and we've got a lot more work to do. But if you see something going wrong, or a feature missing, drop me a note or post on the project talkpage and I'll be happy to help :). We'll be holding two office hours sessions to discuss the tool and improvements to it; the first is at 19:00 UTC on 14 August, and the second at 23:00 on the 15th. Both will be in #wikimedia-office as always. Thanks! Okeyes (WMF) (talk) 15:40, 10 August 2012 (UTC)[reply]
Hey all :). We've just deployed another set of features for Page Curation. They include flyouts from the icons in Special:NewPagesFeed, showing who reviewed an article and when, a listing of this in the "info" flyout, and a general re-jigging of the info flyout - we've also fixed the weird bug with page_titles_having_underscores_instead_of_spaces in messages sent to talkpages, and introduced CSD logging! As always, these features will need some work - but any feedback would be most welcome.
Good news! You are approved for access to 77,000 full-text books and 4 million journal, magazine, newspaper articles, and encyclopedia entries. Check your Wikipedia email!
Input your unique Offer ID and Promotional code. Click Continue. (Note that the activation codes are one-time use only and are case-sensitive).
Create your account by entering the requested information. (This is private and no one from Wikipedia will see it).
You'll then see the welcome page with your Login ID. (The account is now active for 1 year).
If you need help, please first ask Ocaasi at [email protected] and, second, email [email protected] along with your Offer ID and Promotional Code (subject: Wikipedia).
A quick reminder about using the account: 1) try it out; 2) provide original citation information, in addition to linking to a Questia article; 3) avoid bare links to non-free Questia pages; 4) note "(subscription required)" in the citation, where appropriate. Examples are at WP:Questia/Citations.
Hey Geraki. This will be, if not our final newsletter, one of the final ones :). After months of churning away at this project, our final version (apart from a few tweaks and bugfixes) is now live. Changes between this and the last release include deletion tag logging, a centralised log, and fixes to things like edit summaries.
We're (very shortly) closing down this development cycle for Page Curation. It's genuinely been a pleasure to talk with you all and build software that is so close to my own heart, and also so effective. The current backlog is 9 days, and I've never seen it that low before.
However! Closing up shop does not mean not making any improvements. First-off, this is your last chance to give us a poke about unresolved bugs or report new ones on the talkpage. If something's going wrong, we want to know about it :). Second, we'll hopefully be taking another pass over the software next year. If you've got ideas for features Page Curation doesn't currently have, stick them here.
Anyway. You're getting this note because you've participated in discussion and/or asked for updates to either the Article Feedback Tool or Page Curation. This isn't about either of those things, I'm afraid ;p. We've recently started working on yet another project: Echo, a notifications system to augment the watchlist. There's not much information at the moment, because we're still working out the scope and the concepts, but if you're interested in further updates you can sign up here.
In addition, we'll be holding an office hours session at 21:00 UTC on Wednesday, 14 November in #wikimedia-office - hope to see you all there :). I appreciate it's an annoying time for non-Europeans: if you're interested in chatting about the project but can't make it, give me a shout and I can set up another session if there's enough interest in one particular timezone or a skype call if there isn't. Thanks! Okeyes (WMF) (talk) 10:59, 10 November 2012 (UTC)[reply]
Hey all :). A couple of quick updates (one small, one large)
First, we're continuing to work on some ways to increase the quality of feedback and make it easier to eliminate and deal with non-useful feedback: hopefully I'll have more news for you on this soon :).
Second, we're looking at ways to increase the actual number of users patrolling and take off some of the workload from you lot. Part of this is increasing the prominence of the feedback page, which we're going to try to do with a link at the top of each article to the relevant page. This should be deployed on Tuesday (touch wood!) and we'll be closely monitoring what happens. Let me know if you have any questions or issues :). Thanks, Okeyes (WMF) (talk) 14:27, 16 November 2012 (UTC)[reply]
Yes, I see a zero-width space (U 200B) after bo:ཨེ་ཕི་སེ་ལོན།. The fact is that the addition of this, seem right! It seems that the character is part of the corresponding article at bo.wikipedia. The same link without the invisible character, as it was corrected from Yobot [4], sends to a not existing page: bo:ཨེ་ཕི་སེ་ལོན། (as opposed to the correct link as it was corrected by Gerakibot). We should move the article in order to remove the U 200B -gerakiTL12:16, 7 December 2012 (UTC)[reply]
If you're not already aware, a Request for Comment on the future of the Article Feedback Tool on the English-language Wikipedia is open; any and all comments, regardless of opinion and perspective, are welcome.
Our final round of hand-coding is complete, and the results can be found here; thanks to everyone who took part!
We've made test deployments to the German and French-language projects; if you are aware of any other projects that might like to test out or use the tool, please let me know :).
Developers continue to work on the upgraded version of the feedback page that was discussed during our last office hours session, with a prototype ready for you to play around with in a few weeks.
As promised, we've built a set of improvements to the Article Feedback Tool, which can be tested through the links here. Please do take the opportunity to play around with it, let me know of any bugs, and see what you think :).
A final reminder that the Request for Comment on whether AFT5 should be turned on on Wikipedia (and how) is soon to close; for those of you who have not submitted an opinion or !voted, it can be found here.
Greetings Wikipedia Library members! Welcome to the inaugural edition of Books and Bytes, TWL’s monthly newsletter. We're sending you the first edition of this opt-in newsletter, because you signed up, or applied for a free research account: HighBeam, Credo, Questia, JSTOR, or Cochrane. To receive future updates of Books and Bytes, please add your name to the subscriber's list. There's lots of news this month for the Wikipedia Library, including new accounts, upcoming events, and new ways to get involved...
New positions: Sign up to be a Wikipedia Visiting Scholar, or a Volunteer Wikipedia Librarian
Wikipedia Loves Libraries: Off to a roaring start this fall in the United States: 29 events are planned or have been hosted.
New subscription donations: Cochrane round 2; HighBeam round 8; Questia round 4... Can we partner with NY Times and Lexis-Nexis??
New ideas: OCLC innovations in the works; VisualEditor Reference Dialog Workshop; a photo contest idea emerges
News from the library world: Wikipedian joins the National Archives full time; the Getty Museum releases 4,500 images; CERN goes CC-BY
Announcing WikiProject Open: WikiProject Open kicked off in October, with several brainstorming and co-working sessions
New ways to get involved: Visiting scholar requirements; subject guides; room for library expansion and exploration
Welcome to the second issue of The Wikipedia Library's Books & Bytes newsletter! Read on for updates about what is going on at the intersection of Wikipedia and the library world.
Happy New Year, and welcome to a special double issue of Books & Bytes. We've included a retrospective on the changes and progress TWL has seen over the last year, the results of the survey TWL participants completed in December, some of our plans for the future, a second interview with a Wiki Love Libraries coordinator, and more. Here's to 2014 being a year of expansion and innovation for TWL!
The Wikipedia Library completed the first 6 months of its Individual Engagement grant last week. Here's where we are and what we've done:
Increased access to sources: 1500 editors signed up for 3700 free accounts, individually worth over $500,000, with usage increases of 400-600%
Deep networking: Built relationships with Credo, HighBeam, Questia, JSTOR, Cochrane, LexisNexis, EBSCO, New York Times, and OCLC
New pilot projects: Started the Wikipedia Visiting Scholar project to empower university-affiliated Wikipedia researchers
Developed community: Created portal connecting 250 newsletter recipients, 30 library members, 3 volunteer coordinators, and 2 part-time contractors
Tech scoped: Spec'd out a reference tool for linking to full-text sources and established a basis for OAuth integration
Broad outreach: Wrote a feature article for Library Journal's The Digital Shift; presenting at the American Library Association annual meeting
Hi ! We're so happy you wanted to play to learn, as a friendly and fun way to get into our community and mission. I think these links might be helpful to you as you get started.
Donations drive: news on TWL's partnership efforts with publishers
Open Access: Feature from Ocaasi on the intersection of the library and the open access movement
American Library Association Midwinter Conference: TWL attended this year in Philadelphia
Royal Society Opens Access To Journals: The UK's venerable Royal Society will give the public (and Wikipedians) full access to two of their journal titles for two days on March 4th and 5th
Going Global: TWL starts work on pilot projects in other language Wikipedias
Hi Books & Bytes recipients: The Wikipedia Library has been expanding rapidly and we need some help! We currently have 10 signups for free account access open and several more in the works... In order to help with those signups, distribute access codes, and manage accounts we'll need 2-3 more Account Coordinators.
It takes about an hour to get up and running and then only takes a couple hours per week, flexible depending upon your schedule and routine. If you're interested in helping out, please drop a note in the next week at my talk page or shoot me an email at: jorlowitzgmail.com. Thanks and cheers, Jake Ocaasi via MediaWiki message delivery (talk) 23:41, 20 June 2014 (UTC)[reply]
My name is Victor and I'm a storyteller and video producer for the Wikimedia Foundation. I'll be looking to capture stories about Wikimedians at Wikimania in London in a week. Here is an example of the kind of thing that I'm aiming to do. I saw that you're attending Wikimania and I was wondering if you might have some time to talk about your work on Wikimedia projects. Anyway let me know if you are interested, I'll be at Wikimania from the 6th-10th of August and would need maybe 30 minutes of your time. I can answer any questions you may have. I’m best reached at vgrigas(at)wikimedia.org
Highbeam: 100 remaining accounts for newspaper and magazine archives
Questia: 100 remaining accounts for journal and social science articles
JSTOR: 100 remaining accounts for journal archives
Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 23:25, 5 November 2014 (UTC)
You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
Other partnerships with accounts available are listed on our partners page. Do better research and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team.00:25, 18 December 2014 (UTC)
You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).
New donations, including real-paper-and-everything books, e-books, science journal databases, and more
New TWL coordinators, conference news, a new open-access journal database, summary of library-related WMF grants, and more
Spotlight: "Global Impact: The Wikipedia Library and Persian Wikipedia" - a Persian Wikipedia editor talks about their experiences with database access in Iran, writing on the Persian project and the JSTOR partnership
Hello Books & Bytes subscribers. There is a new Visual Editor reference feature in development called Citoid. It is designed to "auto-fill" references using a URL or DOI. We would really appreciate you testing whether TWL partners' references work in Citoid. Sharing your results will help the developers fix bugs and improve the system. If you have a few minutes, please visit the testing page for simple instructions on how to try this new tool. Regards, MediaWiki message delivery (talk) 18:47, 10 April 2015 (UTC)[reply]
The Wikipedia Library is expanding, and we need your help! With only a couple of hours per week, you can make a big difference in helping editors get access to reliable sources and other resources. Sign up for one of the following roles:
Account coordinators help distribute research accounts to editors.
Partner coordinators seek donations from new partners.
Outreach coordinators reach out to the community through blog posts, social media, and newsletters or notifications.
Technical coordinators advise on building tools to support the library's work.
Thank you for using the collections feature in Wikipedia beta! Due to technical and moderation issues, we will be turning off this experimental feature. Your collections will be available for viewing and export until March 1st. If you would like to save your collection as links on a special Wikipedia page, please fill out the following form. If you are interested in giving your feedback about Wikipedia Collections please do so here.
Hello, Geraki. 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.
Hello, Geraki. 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.
You may want to consider using the Article Wizard to help you create articles.
Hello, and welcome to Wikipedia. This is a notice that the page you created, Geraki:RefToolbarMessages-el.js, was tagged as a test page under section G2 of the criteria for speedy deletion and has been or soon may be deleted. Please use the sandbox for any other tests you want to do. Take a look at the welcome page if you would like to learn more about contributing to our encyclopedia.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. PKT(alk)13:09, 27 January 2017 (UTC)[reply]
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.
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, Geraki. 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, Geraki. 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.
I'd like to extend a cordial invitation to you to join the Fifteen Year Society, an informal group for editors who've been participating in the Wikipedia project for fifteen years or more.
You have been a member of Wiki Project Med Foundation (WPMEDF) in the past. Your membership, however, appears to have expired. As such this is a friendly reminder encouraging you to officially rejoin WPMEDF. There are no associated costs. Membership gives you the right to vote in elections for the board. The current membership round ends in 2020.
Hi Geraki, I have started a discussion over our Village pump with the aim of maintaining a public list of all editors who are granted access to any TWL resource. Your thoughts and opinions on the proposal are welcome:-) Regards, ∯WBGconverse
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.
Hi Geraki. Letting you know that the 1917 speech is probably not public domain in the United States, because US laws on sound recording copyrights are completely insane. If the speech is linked in an article, and accompanied by commentary, you can use {{Non-free speech}} and a fair use rationale to protect it from deletion. Although, if it gets deleted again before you get around to it, we at least know where it is now. Someguy1221 (talk) 08:08, 1 September 2019 (UTC)[reply]
As you were not the original uploader of the ogg version, it appears you have not been notified that the file is up for discussion. This is a courtesy notification to rectify that omission; I am not the nominator. --kingboyk (talk) 17:27, 1 September 2019 (UTC)[reply]
Management has migrated to phabricator; to report a bug or request a feature, please create a new task with the script's tag
Message translation has been reduced; for common messages that are already translated in mediawiki core, the system translations are used, in order to reduce duplication of efforts
Recent additions
New pages are shown at the start of a site's feed
Log entries are shown at the end of a site's feed
Basic validation has been added to user settings, applied before saving
Site validation has also been added; a site (excluding unique projects like wikidata, meta, commons, etc.) is considered to be valid if it is the form of "language.project", where both the language code and project name are valid. It does not, however, check that the actual site is valid; only that it could be. In other words, even though sco.wiktionary refers to a site that doesn't exist, it is considered valid, because sco is a valid language code (sco.wikipedia is a working site) and wiktionary is a valid project.
Announcements
BREAKING CHANGE: Backwards compatibility supporting the use of sites as *.*.org (like 'en.wikipedia.org' or 'meta.wikimedia.org'), deprecated in version 1.7.5, will be removed soon; all sites should now be saved as *.* (like 'de.wikinews' or 'fr.wikisource')
BREAKING CHANGE: Storing user sites as window.GlobalWatchlistSites, deprecated in version version 1.11.11, will be removed soon; all settings should be stored in the window.GlobalWatchlistConfig object
Both of these breaking changes will be implemented alongside version 4.0; until then, any use of the config page (m:Special:BlankPage/GlobalWatchlistConfig) will result in saving settings in the newest format
Next release
Version 4.0 should be released in around a week. It will include the new features mentioned above, as well as removal of backwards compatibility for settings and sites.
To report a bug or request a feature, please create a new task on Phabricator with the script's tag
Recent additions
Site validation has been tightened. Previously, only the language code and project name had to be valid - now, they must be a valid combination (i.e. en.wikiversity exists, and so is valid, but sco.wikiversity is not valid, because no such wiki exists).
When the global watchlist feed is loading, an OOUI widget will be shown, rather than an animated gif.
An option has been added to no longer group edits to the same page. For now, this isn't very useful, since metadata for the edits (editor, summary, tags, etc.) are not yet shown, but they will be soon. Until then, ungrouped edits are treated the same as pages with only 1 edit - the minor and bot flags are displayed if applicable. If edits are grouped, the minor and bot flags are only shown if they apply to all of the edits.
Upcoming changes
Starting with version 5.0, there will be an option at the settings page to switch to and from a "stable" version of the script. When activated, the script import in your global.js should be replaced, and then the page refreshed with the new script loaded. The stable script will live at m:User:DannyS712/Global watchlist/stable.js, and will be updated with each full release. Otherwise, it shouldn't be edited, providing a version that is less prone to bugs as the script is developed.
Announcements
WARNING: Starting with version 5.1, the option to mark the pages of a site as seen be implemented using the entirewatchlist API option, rather than manually listing the titles. This is being done to simplify the implementation code. This will result in the same functionality as marking all pages as seen via Special:Watchlist (i.e. even if the page isn't visible due to your filter choices, it will still be marked as seen). If you would like to keep using the current method for a while, please switch to the stable branch.
Next release
Version 5.0 has just gone live. It includes the new features mentioned above.
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.
I am investigating adding more context to each entry that is shown (such as the edit summaries, tags, patrol marks, the user who made the edit, etc.). Is there any desire for such additions? If so, what should be added first, and what is a low priority? Please leave feedback on the relevant phabricator task, phab:T238300.
Recent additions
Site validation has been overhauled. Rather than hard-coding a list of valid sites, users will be able to watch any site where they have an attached local user account. If a site is rejected as invalid, please ensure that there is indeed a local account attached to your global account.
Users will now be alerted regarding the results of attempting to update their settings.
Live updates have been added - when activated, the script will refresh in the background, and then load the new feed, every 7.5 seconds. In the future, this frequency may be configurable.
OOUI icons have been added to most buttons.
There is now an option to eliminate the confirmation dialog when marking all sites as seen.
Announcements
WARNING: Starting with version 6.1, site aliases currently used when saving settings will be removed, and only sites in the form of `lang.project` will be accepted.
As noted in the last update, marking a site as seen now uses entirewatchlist, which means that any changes to watched pages between when the watchlist was loaded and when the site was "marked as seen" may be ignored.
Next release
Version 6.0 was just finalized for the development and stable branches of the script.
A new "fast" mode has been introduced. When used, the watchlist serves as just a list of pages that have been modified, and no longer includes context about the edits themselves.
More information has been added to entries. When edits are not grouped by page, or when there is only 1 edit to a page, minor and bot flags are shown, as well as the user who made the edit, the summary used, and any tags that were applied. When multiple entries are grouped, bot and minor flags are only shown if all of the grouped edits were made by bots or where marked as minor. If only 1 user edited the page, that user's name is still shown, but no summaries or tags are included.
All watchlists are now fetched in parallel, rather than in series, greatly reducing load time.
Technical notes
Most of the source code is now annotated with jsdoc notes, allowing others to more clearly understand and review the code.
I will be looking into creating guidelines to let others contribute to the script; see phab:T238298.
Newly translated messages are added to the script when I notice them; if you have translated messages that aren't showing up, please let me know at m:User talk:DannyS712.
Next release
Version 7.0 was just finalized for the development and stable branches of the script.
Twinkle has a new update (more). It now supports partial blocks and includes the select2 library as a dependency. Select2 is available at MediaWiki:Gadget-select2.min.js for other gadgets and scripts to use.
Miscellaneous
Until now, this newsletter has been written primarily by me (DannyS712).
If others would like to contribute, help is always appreciated;
Automatically detecting Good Article, Featured Article, and Featured List status, and limiting ORES predictions to B-class
An updated version of Twinkle was released. Features relating to the recently-enabled partial blocks include automatic lookup of pages and expanded options for block templates. See a full list of changes here
For users of Enterprisey's easy-brfa script, the bug with transcluding new BRFAs has been resolved
For any scripts that previously made use of the edit API to change a page's content model, a new API module is available: use action=changecontentmodel to specify the new content model of an existing page. Documentation is available: mw:API:ChangeContentModel.
The dispute resolution noticeboard wizard is no longer a gadget, but rather is loaded using withJS and withCSS. See the discussion at MediaWiki talk:Gadget-DRN-wizard.js
Pending requests
A script to help file movers process requests, including
renaming the file
updating file links
removing the {{Rename media}} template (when relevant)
Enterprisey's reply-link has been updated to fail less, especially around template transclusions.
Twinkle released new features, including a new option to disable individual modules, support for stub template nomination at CfD, and integration with the PageTriage extension used to patrol new pages. (See full list of changes)
Open tasks
The mediawiki.notify resource loader module was deprecated and is no longer needed; its functionality is now available by default. See mw:ResourceLoader/Migration guide (users) for more. Any dependency on it should be removed.
Twinkle's Morebits library added a new Morebits.date class to replace the moment library. It can handle custom formatting and natural language for dates, as well as section header regexes. If you were using getUTCMonthName or getUTCMonthNameAbbrev with Date objects, those have been deprecated and should be updated.
Thank you for your interest and contributions to WikiLoop Battlefield.
We are holding a voting for proposed new name. We would like to invite you to this voting. The voting
is held at m:WikiProject_WikiLoop/New_name_vote and ends on July 13th 00:00 UTC.
HI Geraki,
I'm writing to let you know we have simplified the RfC on trust levels for the tool WikiLoop DoubleCheck. Please join and share your thoughts about this feature! We made this change after hearing users' comments on the first RfC being too complicated. I hope that you can participate this time around, giving your feedback on this new feature for WikiLoop DoubleCheck users.
Thanks and see you around online, María Cruz MediaWiki message delivery (talk) 20:05, 19 November 2020 (UTC)[reply]
If you would like to update your settings to change the wiki where you receive these messages, please do so here.
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.
Enterprisey's parsoid-round-trip uses Parsoid to convert wikitext to HTML and back, and then shows the result and the difference between the original wikitext and the post-conversion wikitext.
Frietjes's infoboxgap assists in renumbering infobox labels/data/classes, so that a new line can be inserted in the middle of the infobox.
Twinkle has made a number of improvements, including using a change tag to identify actions made with it and automatically filing edit requests for protected XfD nominations.
GeneralNotability's spihelper updated to 2.2.10, fixing a number of small bugs, automatically tagging globally locked socks as such in the sockpuppet template, and restoring open cases following an SPI history merge.
Enterprisey's script-installer gadget has been updated with more internationalization of messages, as well as addition of a user preference, window.scriptInstallerInstallTarget to allow controlling where new scripts are to be installed.
Enterprisey's copy-section-link adds popups to section headers which has an appropriate wikilink and external link to the section.
DannyS712's FindBlacklistEntry can be used to figure out which line(s) in either the local or global spamblacklist prevent a particular url from being added.
The Watchlist Expiry feature worked on by the Community Tech team has been enabled on Wikipedia. For scripts that include watching or unwatching pages, developers may want to update their code to take advantage of the new functionality. See the documentation on mediawiki.org.
As noted in the prior issue, Enterprisey's links-in-logs script has now been implemented as part of MediaWiki core. By my count, this is his third script that was replaced by implementing the code in MediaWiki core or an extension, along with link-section-edits and abusefilter-hide-search. Additionally, his reply-link script is being converted in part to mw:Extension:DiscussionTools. Are there any other scripts that might be worth integrating directly in MediaWiki? Thoughts would be welcome at Wikipedia talk:Scripts .
You have been a member of Wiki Project Med Foundation (WPMEDF) in the past. Your membership, however, appears to have expired. As such this is a friendly reminder encouraging you to officially rejoin WPMEDF. There are no associated costs. Membership gives you the right to vote in elections for the board. The current membership round ends in 2022.
User:Ahecht/Scripts/pageswap - version 1.4 fixes reading destination from form field if destination is not in article namespace, and fixes self redirects.
Wikipedia:XFDcloser - version 4 brings a new user interface for dialogs, some preferences for customising XFDcloser, major behind-the-scenes coding changes, and resolves various issues raised on the talkpage. Also, since version 3.16.6 non-admin soft delete closure have been allowed at TfD.
Open tasks
As a reminder, the legacy javascript globals (like accessing wgPageName without first assigning it a value or using mw.config.get('wgPageName') instead) are deprecated. If your user scripts make use of the globals, please update them to use mw.config instead. Some global interface editors or local interface administrators may edit your user script to make these changes if you don't. See phab:T72470 for more.
Miscellaneous
For people interested in creating user scripts or gadgets using TypeScript, a types-mediawiki package (GitHub, NPM) is now available that provides type definitions for the MediaWiki JS interface and the API.
A GitHub organization has been created for hosting codebases of gadgets. Users who maintain gadgets using GitHub may choose to move their repos to this organization, to ensure continued maintenance by others even if the original maintainer becomes inactive.
As always, if anyone else would like to contribute, including nominating a featured script, help is appreciated. Stay safe, and happy new year! --DannyS712 (talk) 01:17, 3 February 2021 (UTC)[reply]
Thank you for supporting Project WikiLoop! The year 2020 was an unprecedented one. It was unusual for almost everyone. In spite of this, Project WikiLoop continued the hard work and made some progress that we are proud to share with you. We also wanted to extend a big thank you for your support, advice, contributions and love that make all this possible.
Thank you for taking the time to review Wikipedia using WikiLoop DoubleCheck. Your work is important and it matters to everyone. We look forward to continuing our collaboration through 2021!
FoldArchives collapses archived talk page threads in order to reduce screen space
GoToTitle converts the page title into an input field for navigating to other pages
UserHighlighter adds highlighting to links to the userpages, talk pages, and contributions of administrators and other user groups as well as tooltips to indicate which groups a user is in
filterDiff: Adds a "Show changes" button to the filter editor.
filterNotes: Parses filter notes as wikitext (so links are clickable), and signs and dates new comments for you.
filterTest: Adds a "Test changes" button. Opens Special:AbuseFilter/test with what's currently in the edit form, not with what's saved in the database, so you don't have to copy-paste your changes.
Twinkle has a number of improvements, including that most watchlist defaults now make use of the new temporary watchlist feature. Other changes include rollbacks treating consecutive IPv6 editors in the same /64 range as the same user, adding a preview for shared IP tagging, a preference for watching users after CSD notification, and for sysops, the ability to block the /64 and link to a WP:RfPP request, and new copyright blocks default to indefinite.
Wikipedia:Shortdesc helper now v3.4.17, changes include minor fixes and preventing edits that don't change the description.
Joeytje50's JWB now version 4.1.0, includes the ability to generate page lists from the search tool, major updates to the handling of regular expressions, the storing of user settings, the addition of upload protection, and an option to skip pages that belong to a specific category, among other changes. See User:Joeytje50/JWB/Changelog for a full list of recent changes.
Wikipedia:User scripts/List has been revamped to make it easier to find scripts suited for your needs. If you know of a cool script that is missing on the list, or a script on the list that is no longer working, please edit the list or let us know on the talk page.
My apologies for this long-overdue issue, and if I missed any scripts. Hopefully going forward we can go back to monthly releases - any help would be appreciated. Thanks, --DannyS712 (talk) 13:04, 2 June 2021 (UTC)[reply]
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!"
Hello everyone, and welcome to the 22nd issue of the Wikipedia Scripts Newsletter. This issue will be covering new and updated user scripts from the past seven months (June through December 2021).
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Featured script
LuckyRename, by Alexis Jazz, is this month's featured script. LuckyRename makes requesting file moves easier, and automates the many steps in file moving (including automatic replacement of existing usage). Give it a shot!
Updated scripts
SD0001: hide-reverted-edits has been updated to take into account changes in reversion tools like Twinkle and RedWarn.
ClaudineChionh: SkinSwitcher (a fork and update of Eizen's script) provides an options menu/toolbox/toolbar allowing users to view a given page in MediaWiki's default skins.
Wikipedia:User scripts/Ranking is a sortable table of Wikipedia's thousand-or-so most commonly used scripts; it includes their author, last modification date, installation count, and sometimes a short description.
Toolhub is a community managed catalog of software tools used in the Wikimedia movement. Technical volunteers can use Toolhub to document the tools that they create or maintain. All Wikimedians can use Toolhub to search for tools to help with their workflows and to create lists of useful tools to share with others.
draft-sorter sorts AfC drafts by adding WikiProject banners to their talk pages. It supersedes User:Enterprisey/draft-sorter, adding a few features and fixing some bugs.
BooksToSfn adds a portlet link in Visual Editor's source mode editing, in main namespace articles or in the user's Sandbox. When clicked, it converts one {{cite book}} inside a <ref>...</ref> tag block into an {{Sfn}}.
diffedit enables editing directly from viewing a diff "when, for instance, you notice a tiny mistake deep into an article, and don't want to edit the entire article and re-find that one line to fix that tiny mistake".
warnOnLargeFile warns you if you're about to open a very large file (width/height >10,000px or file size >100 MB) from a file page.
QuickDiff (by OneTwoThreeFall at Fandom) lets you quickly view any diff link on a wiki, whether on Recent Changes, contribs pages, history pages, the diff view itself, or elsewhere. For more information, view its page on Fandom.
talkback creates links after user talk page links like this: |C|TB (with the first linking to the user's contributions, and the latter giving the option of sending a {{talkback}} notice). It also adds a [copy] link next to section headers.
diff-link shows "copy" links on history and contributions pages that copy an internal link to the diff (e.g., Special:Diff/1026402230) to your clipboard when clicked.
auto-watchlist-expiry automatically watchlists every page you edit for a user-definable duration (you can still pick a different time using the dropdown, though).
generate pings generates the wikitext needed to ping all members of a category, up to 50 editors (the limit defined by MediaWiki).
share ExpandTemplates url allows for easy sharing of your inputs to Special:ExpandTemplates. It adds a button that, when clicked, copies a shareable URL to your exact invocation of the page, like this. Other editors do not need to have this script installed in order to access the URL generated.
show tag names shows the real names of tags next to their display names in places such as page revision histories or the watchlist.
ColourContrib color-codes the user contributions page so that pages you've edited last are sharply distinguished from pages where another editor was the last to edit the page.
All in all, some very neat scripts were written in these last few months. Hoping to see many more in the next issue -- drop us a line on the talk page if you've been writing (or seeing) anything cool and good. Filling in for DannyS712, this has been jp×g. Take care, and merry Christmas! jp×g07:30, 24 December 2021 (UTC)[reply]
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".
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. 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.
He may notability criteria, but please add another permanent collection to insure he meets WP:NARTIST. Also, the article is an orphan, please introduce links from related articles.
To reply, leave a comment here and begin it with {{Re|Netherzone}}. Please remember to sign your reply with ~~~~. (Message delivered via the Page Curation tool, on behalf of the reviewer.)
New year, new scripts. Welcome to the 23rd issue of the Wikipedia Scripts Newsletter, covering around 39% of our favorite new and updated user scripts since 24 December 2021. That’s right, we haven’t published in two years! Can you believe it? Did you miss us?
Got anything good? Tell us about your new, improved, old, or messed-up script here!
User:Alexander Davronov/HistoryHelper has now become stable with some bugfixes and features such as automatically highlighting potentially uncivil edit summaries and automatically pinging all the users selected.
To a lesser extent, the same goes for User:PrimeHunter/Search sort.js. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Aaron Liu: Watchlyst Greybar Unsin is a rewrite of Ais's Watchlist Notifier with modern APIs and several new features such as not displaying watchlist items marked as seen (hence the name), not bolding diffs of unseen watchlist elements which doesn’t work properly anyways, displaying the rendered edit summary, proper display of log and creation actions and more links.
Alexis Jazz: Factotum is a spiritual successor to reply-link with a host of extra features like section adding, link rewriting, regular expressions and more.
User:Aveaoz/AutoMobileRedirect: This script will automatically redirect MobileFrontend (en.m.wikipedia) to normal Wikipedia. Unlike existing scripts, this one will actually check if your browser is mobile or not through its secret agent string, so you can stay logged in on mobile! Hooray screen estate!
Deputy is a first-of-its-kind copyright cleanup toolkit. It overrides the interface for Wikipedia:Contributor copyright investigations for easy case processing. It also includes the functionality of the following (also new) scripts:
User:Elominius/gadget/diff arrow keys allows navigation between diffs with the arrow keys. It also has a version that requires holding Ctrl with the arrow key.
Frequently link to Wikipedia on your websites yet find generating CC-BY credits to be such a hassle? Say no more! User:Luke10.27/attribute will automatically do it for ya and copy the credit to yer clipboard.
User:MPGuy2824/MoveToDraft, a spiritual successor (i.e. fork) to Evad37's script, with a few bugs solved, and a host of extra features like check-boxes for choosing draftification reasons, multi-contributor notification, and appropriate warnings based on last edit time.
/CopyCodeBlock: one of the most important operations for any scripter and script-user is to copy and paste. This script adds a copy button in the top right of every code block (not to be confused with <code>) that will, well, copy it to your clipboard!
m:User:NguoiDungKhongDinhDanh/AceForLuaDebugConsole.js adds the Ace editor (a.k.a. the editor you see when editing JS, CSS and Lua on Wikimedia wikis) to the Lua debug console. "In my opinion, whoever designed it to be a plain <textarea> needs to seriously reconsider their decision."
GANReviewTool quickly and easily closes good article nominations.
ReviewStatus displays whether or not a mainspace page is marked as reviewed.
SpeciesHelper tries to add the correct speciesbox, category, taxonbar, and stub template to species articles.
User:Opencooper/svgReplace and Tol's fork replaces all rasterized SVGs with their original SVG codes for your loading pleasures. Tell us which one is better!
ArticleInfo displays page information at the top of the page, directly below the title.
/HeaderIcons takes away the Vector 2022 user dropdown and replaces it with all of the icons within, top level, right next to the Watchlist. One less click away! There's also an alternate version that uses text links instead of icons.
Hello everyone, and welcome to the 24th issue of the Wikipedia Scripts Newsletter, covering all our favorite new and updated user scripts since 24 December 2021. Uh-huh, we're finally covering the good ones among the rest! Aren't you excited? Remember to include a link in double brackets to the script's .js page when you install the script, so that we can see who uses the script in WhatLinksHere! The ScriptInstaller gadget automatically does this. Aaron Liu (talk) 01:00, 1 March 2024 (UTC)[reply]
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Making user scripts load faster by SD0001 is this month's featured script, which caches userscripts every day to eliminate the overhead caused by force-downloading the newest version of scripts every time you open a Wikipedia page. Despite being released in April 2021, our best script scouters have failed to locate it due to its omission from the US of L. For security reasons, the script only supports loading JavaScript pages.
Ahecht has created a fork of SiBr4/TemplateSearch, which adds the "TP:" shortcut for "Template:" in the search box, and updated it to be compatible with Vector 2022.
AquilaFasciata/goToTopFast is a much faster fork of the classic goToTop script that also adds compatibility for Minerva and Vector 2022.
Without caching. Each script takes 400–500ms. A particularly large script takes 1.11 s! Internet download speed is 50 Mbps.With caching enabled. Each script takes just 1-2 ms to load.
To a lesser extent, the same goes for PrimeHunter/Search sort. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Dragoniez/SuppressEnterInForm stops you from accidentally submitting anything due to pressing enter while in the smaller box, and works on almost anything... except the InputBox element itself, used in subscription lists and the Signpost Crossword! Oh, the humanity!
Doǵu/Adiutor(pictured) provides a nice, integrated interface to do some twinkley tasks such as copyvio detection, CSD tagging, and viewing the most recent diff.
Eejit43 has quite the aesthetically pleasing scripts, all made in TypeScript.
/afcrc-helper is a replacement for the unmaintained Enterprisey/AFCRHS and processes Redirects for Creation and Categories for Creation requests.
/ajax-undo stops the "undo" button from taking you to another page while providing a text box to provide a reason for the revert.
/redirect-helper(pictured) adds a much better interface for editing and redirects, including categorization, for which valid categories are dictated by /redirect-helper.json.
/rmtr-helper helps process technical requested moves without being able to actually move them.
Guycn2/UserInfoPopup(pictured) adds a flyout after the watchlist star on userspace pages that displays the common information you might use about a user.
Jeeputer/editCounter, under userspace, adds a portlet link to count your edits by namespace, put them in a table, and put that table in a hardcoded subpage, all in the background.
Hilst/Scripts/sectionLinks converts all section links to use the § sign, which are known to be preferred over the ugly # by 99% of the devils I've met.
PrimeHunter/Category source.js adds portlet links to tell you where a category for an article comes from and supports those from template transclusions.
Dragoniez/ToollinkTweaks adds more and customizable links next to users in page history, logs, watchlist, recent changes, etc.
Firefly/more-block-info optimizes the display of rangeblocks in contribution pages. Doesn't work outside the English locale of any wiki, unfortunately.
NguoiDungKhongDinhDanh/AjaxLoader makes paging links (e.g. older 50, 500, newest) load without refreshing and makes you realize how slow your internet actually is.
Ahecht/RedirectID adds the redirect target to all redirects. For all the WP:NAVPOPS haters. (Do these exist?)
Dragoniez/MarkBLockedGlobal: Remember the "strike blocked usernames" gadget? Now you can use a red, dotted line to highlight rangeblocks and global locks!
Jonesey/common(pictured) has some styles to overhaul your Vector 2022 experience. It reduces padding everywhere, and makes the top bar animation faster.
Aaron Liu/V22 is a fork that narrows the sidebars instead of upheaving them, reverts the January 2024 dropdown changes, and restores the old page-link color for links that don't go outside the current wiki.
Nardog: SmartDiff is a spiritual successor to Enterprisey/fancy-diffs. It makes the page title part of links in diffs clickable, along with template and parser function calls. Unnamed parameters can be configured per template to also be linked. All links are styled based on the normal CSS classes of rendered links.
For the paranoid: Rublov/anonymize replaces your username at the top of the screen with the generic "User page" text. Remember, it is your duty to persuade everyone that editing is an honor.
/AjaxBlock provides a dialog box for easy input of reasons while blocking users.
/Selective Rollback(pictured) provides a dialog box to customize rollback edit summaries and does them without reloading the page. Seriously, why doesn't MediaWiki already do this?
/flickrsearch adds a portlet link to search for uploadable flickr images about the subject.
/randomincategory adds a portlet link when on Category pages to go to a random page in the current category.
Vghfr/EasyTemplates adds a portlet link to automatically insert some of the most common inline {{fix}} templates.
Yes, we're just doing 'em as we go now. Thanks for reading through this looong issue, if you did! I'm sure this'll send a record for the longest issue ev-ah. You may need to wait even longer for the last issue, as our reserve of old-y and goodie scripts have ran out... We encourage you to try and do some of the requests or improvement tasks. See you in Summer, hopefully!
To reply, leave a comment here and begin it with {{Re|North8000}}. Please remember to sign your reply with ~~~~. (Message delivered via the Page Curation tool, on behalf of the reviewer.)
To reply, leave a comment here and begin it with {{Re|North8000}}. Please remember to sign your reply with ~~~~. (Message delivered via the Page Curation tool, on behalf of the reviewer.)
Hey there, welcome to the 25th issue of the Wikipedia Scripts Newsletter, covering all our favorite new and updated user scripts since 1 March 2024. We've got a ton of wonderful editors taking back their pitchforks today. Don't worry, for they come in peace, to forcibly fix and extend existing scripts you use with sheer passion. There's so many, them forks have got what's basically their own column now! gift us with some rows before it's too late Aaron Liu (talk) 04:01, 1 August 2024 (UTC)[reply]
Got anything good? Tell us about your new, improved, old, or messed-up script here!
To a lesser extent, the same goes for PrimeHunter/Search sort. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
An easily configurable script to add a link to the #p-vector-user-menu-overflow portlet with a name, target, and icon. This one should be a relatively easier one. I would do it myself, but I'm too busy rotting away on Celeste (video game).
After the ＲＩＩＪ update, Aaron Liu: Watchlyst Greybar Unsin has a dismiss button that allows you to mark an item as read in one click and cycle to the next Watchlist item.
Lordseriouspig/StatusChangerImproved is just like Enterprisey's script, except you select your status from a dropdown instead of cycling through them with a button. The WMF operates out of car-centric infrastructure anyway. Shame!
Aaron Liu has created Duplinks from Evad37/duplinks-alt; his fork adds a config variable to automatically highlight duplicate links on the loading of any page where the portlet link would've appeared.
Tired of staring at a bunch of filtering text and waiting for darn filter logs to load? Msz2001/AbuseFilter analyzer can parse abuse filters into a visual syntax tree and evaluate locally on-demand!
Polygnotus/DuplicateReferences finds references with the same link and displays the number of them along with a button to add the {{duplicated citations}} tag under the references section. Being lazy has never been easier!
fastest gun on the net Ponor/really-quick-block really quick add to contribution lists three buttons awesome
Hello! Voting in the 2024 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 2 December 2024. 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.
Thanks for uploading Image:Benizelos.jpg. The media description page currently specifies that it is non-free and may only be used on Wikipedia under a claim of fair use. However, it is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the media was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that media for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
wikimedia.org or drop a note on my talkpage, and I'm happy to give you a quick walkthrough in a one-on-one session :).
The Wikipedia Library
The Wikipedia Library
There is currently a discussion at Wikipedia:Administrators' noticeboard regarding an issue with which you may have been involved. The thread is Geraki created his JavaScript page with an incorrect title. Eyesnore 13:22, 27 January 2017 (UTC)
Miscellaneous
Twinkle has made a number of improvements, including using a change tag to identify actions made with it and automatically filing edit requests for protected XfD nominations.
Open tasks
Pending requests
.jpg)
Got anything good? Tell us about your new, improved, old, or messed-up script here!
New scripts
_shown_in_her_laboratory_in_1947.jpg)
.jpg)
_(cropped_to_40%25).jpg){kind=small}
Featured script
Improve a script
Requested scripts
New scripts
Newly maintained scripts.png)
.png)
Requested scripts
){kind=link}
