By
motion,
standard discretionary sanctions have been temporarily
authorizedfor all pages relating to the
Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes). The effectiveness of the discretionary sanctions can be evaluated on the request by any editor after March 1, 2021 (or sooner if for a good reason).
Completion rates for comments made with the Reply tool and full-page wikitext editing. Details and limitations are in this
report.
The
Reply tool is available at most other Wikipedias.
The Reply tool has been deployed as an opt-out
preference to all editors at the Arabic, Czech, and Hungarian Wikipedias.
It is also available as a
Beta Feature at almost all Wikipedias except for the English, Russian, and German-language Wikipedias. If it is not available at your wiki, you can request it by following
these simple instructions.
Research notes:
As of January 2021, more than 3,500 editors have used the Reply tool to post about 70,000 comments.
There is preliminary data from the Arabic, Czech, and Hungarian Wikipedia on the Reply tool.
Junior Contributors who use the Reply tool are more likely to publish the comments that they start writing than those who use full-page wikitext editing.
[1]
The Editing and Parsing teams have significantly reduced the number of edits that affect other parts of the page. About 0.3% of edits did this during the last month.
[2] Some of the remaining changes are automatic corrections for
Special:LintErrors.
A large
A/B test will start soon.[3] This is part of
the process to offer the Reply tool to everyone. During this test, half of all editors at
24 Wikipedias (not including the English Wikipedia) will have the Reply tool automatically enabled, and half will not. Editors at those Wikipeedias can still turn it on or off for their own accounts in
Special:Preferences.
During
Talk pages consultation 2019, editors
said that it should be easier to know about new activity in conversations they are interested in. The
Notifications project is just beginning. What would help you become aware of new comments? What's working with the current system? Which pages at your wiki should the team look at? Please post your advice at
mw:Talk:Talk pages project/Notifications.
A
request for comment is open that proposes a process for the community to revoke administrative permissions. This follows a
2019 RfC in favor of creating one such a policy.
A
request for comment is in progress to remove
F7 (invalid fair-use claim)
subcriterion a, which covers immediate deletion of non-free media with invalid fair-use tags.
A
request for comment asks if sysops may place the General sanctions/Coronavirus disease 2019 editnotice template on pages in scope that do not have page-specific sanctions?
When blocking an IPv6 address with
Twinkle, there is now a checkbox with the option to
just block the /64 range. When doing so, you can still leave a block template on the initial, single IP address' talkpage.
When protecting a page with Twinkle, you can now add a note if doing so was in response to a request at
WP:RfPP, and even link to the specific revision.
By
motion, the
discretionary sanctions originally authorized under the
GamerGate case are
now authorized under a new
Gender and sexuality case, with sanctions authorized for all edits about, and all pages related to, any gender-related dispute or controversy and associated people. Sanctions issued under GamerGate are now considered Gender and sexuality sanctions.
Welcome to the seventeenth newsletter from the
Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in
mid-size Wikimedia projects.
Structured tasks
Add a link: the team is continuing to engineer on our first "structured task", which will break down the workflow of adding wikilinks to articles, and assist newcomers with an algorithm to identify words and phrases that could be made into links.
Add an image: even as we build our first structured task, we have been thinking about the next one. "Add an image" is a structured task in which newcomers would be recommended images from Wikimedia Commons to add to unillustrated articles. This is an ambitious idea with many details to consider. We have already learned a lot from community members, and we encourage everyone to
look at the project page and
join the discussion.
Moving forward: more wikis to get the features
Last November, our team
published the analysis of the impact of newcomer tasks. We announced that we found that the Growth features, and particularly newcomer tasks, lead to increased editing from newcomers.
Because of these results, we believe all Wikipedias should implement these features.
We have started to contact more wikis to deploy the features, including Wikipedias of all sizes. Bengali Wikipedia recently began using Growth features, and Danish, Thai, Indonesian, and Romanian Wikipedias will be coming soon. Please
contact us if you have questions regarding deployment.
We are looking for translators who can help by translating the interface. Translating is done on
Translatewiki.net (it requires a different account that your Wikimedia one). Communities that already have the Growth features being deployed are invited to check on the translations. Access translations here.
Variant testing
As mentioned in
our previous newsletter, we ran a test of two variants of the newcomer homepage, meant to find a version that increases users completing suggested edits. We have completed the experiment,
and learned that one of the variants leads to more edits on desktop while the other leads to more edits on mobile. Therefore,
we will deploy the strongest variants for each platform to all newcomers.
News for mentors
Mentor dashboard: we have interviewed mentors from several communities as we plan a
mentor dashboard feature, which would help mentors track the progress of their mentees. We encourage all mentors to
share their thoughts on tools that would help them.
Magic word for mentors: it is now possible to
use a magic word, {{#mentor}}, to display the name of a given newcomer's mentor. This can be used on welcome messages, userboxes, etc.
Help panel questions going to mentors: in most wikis, newcomers using the help panel ask questions to the help desk. On Czech Wikipedia, we have experimented with sending these questions to mentors instead. This simplifies the newcomer experience, and only led to a increase in mentorship questions
of about 30%. We tried this
in Arabic, Bengali, French and Vietnamese Wikipedias, and we are making it
the default experience.
Hi wub, where would be the correct place to make the reverted complaint about too much bad weather featured articles? --
Schweikhardt (
talk) 14:00, 15 March 2021 (UTC)reply
Following a
request for comment,
F7 (invalid fair-use claim)
subcriterion a has been deprecated; it covered immediate deletion of non-free media with invalid fair-use tags.
Following a
request for comment,
page movers were granted the delete-redirect userright, which allows moving a page over a single-revision redirect, regardless of that redirect's target.
Technical news
When you move a page that many editors have on their watchlist the history can be split and it might also not be possible to move it again for a while. This is because of a
job queue problem. (
T278350)
Code to support some very old
web browsers is being removed. This could cause issues in those browsers. (
T277803)
So I've been going on a spree of adding that specific subtemplate on articles which used to be tagged with expand language with an =fr code.
Just wondering if I should help you fix all those instances by capitalizing the Expand part of the code.
Sorry for the inconvenience
Sadenar40000 (
talk) 16:18, 21 April 2021 (UTC)reply
@
Sadenar40000 Oh no, it's totally fine to use lower case for "expand". I was just trying to clear out
Category:Pages with no translate target (which is done for now) and taking the opportunity to tweak other things as I went, but it's not like it really needs "fixing".
the wub"?!" 16:26, 21 April 2021 (UTC)reply
Yeah I just hadn't seen that the target had a different spelling, thanks for picking up on the issue
Sadenar40000 (
talk) 16:57, 21 April 2021 (UTC)reply
The user group oversight will be renamed to suppress. This is for
technical reasons. You can comment at
T112147 if you have objections.
Arbitration
The
community consultation on the Arbitration Committee
discretionary sanctions procedure was closed, and an initial draft based on feedback from the now closed consultation is expected to be released in early June to early July for community review.
Welcome to the eighteenth newsletter from the
Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in
mid-size Wikimedia projects.
Structured tasks
A screenshot of "add a link" feature in development in beta.
"
Add a link" is now being tested in production and is nearing release on our four pilot wikis (Arabic, Czech, Vietnamese, and Bengali Wikipedias). We'll be doing final tests this week and next week, and then plan to deploy to the four wikis either during May 24 week, or May 31 week. After two weeks, we will analyze the initial data to identify any problems or trends. We expect that this feature will engage new kinds of newcomers in easy and successful edits. If things are going well after four weeks, we'll progressively deploy it to the wikis with Growth features.
We are currently working on a
Mentor dashboard. This special page aims to help mentors be more proactive and be more successful at their role. The first iteration will include a table that shows an overview of the mentors current mentees, a module with their own settings, and a module that will allow them to store their best replies to their mentees questions.
Community configuration editing form under development
We are working on project to allow communities to
manage the configuration of the Growth features on their own. In the past, communities have needed to work directly with the Growth team to set up and alter the features. We plan to put this capability in the hands of administrators, through an easy-to-use form, so that the features can be easily tailored to fit the needs of each community. While we developed it initially for Growth features, we think this approach could have uses in other features as well. We'll be trying this on our pilot wikis in the coming weeks, and then we'll bring it to all Growth wikis soon after. We hope you check out
the project page and add any of your thoughts to
the talk page.
Scaling
Growth features are now available
on 35 wikis. Here is the list of the most recent ones: Romanian Wikipedia, Danish Wikipedia, Thai Wikipedia, Indonesian Wikipedia, Croatian Wikipedia, Albanian Wikipedia, Esperanto Wikipedia, Hindi Wikipedia, Norwegian Bokmål Wikipedia, Japanese Wikipedia, Telugu Wikipedia, Spanish Wikipedia, Simple English Wikipedia, Malay Wikipedia, Tamil Wikipedia, Greek Wikipedia, Catalan Wikipedia.
A new group of Wikipedias
has been defined for the deployment of Growth features. Please
contact us if you have questions about the deployment process, or if your community likes to get the features in advance.
Wikimedia previously used the
IRC network
Freenode. However, due to changes over who controlled the network with reports of a forceful takeover by several ex-staff members, the
Wikimedia IRC Group Contacts decided to move to the new
Libera Chat network. It has been reported that Wikimedia related channels on Freenode have been forcibly taken over if they pointed members to Libera. There is a
migration guide and Wikimedia
discussions about this.
When newcomers had the Reply tool and tried to post on a talk page, they were more successful at posting a comment. (
Source)
Earlier this year, the Editing team ran a large study of
the Reply Tool. The main goal was to find out whether the Reply Tool helped
newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.
The key results were:
Newer editors who had automatic ("default on") access to the Reply tool were
more likely to post a comment on a talk page.
The comments that newer editors made with the Reply Tool were also
less likely to be reverted than the comments that newer editors made with page editing.
These results give the Editing team confidence that the tool is helpful.
Looking ahead
The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.
Consensus has been reached to delete all books in the book namespace. There was rough consensus that the deleted books should still be available on request at
WP:REFUND even after the namespace is removed.
An
RfC is open to discuss the next steps following a trial which automatically applied pending changes to
TFAs.
Technical news
IP addresses of unregistered users are to
be hidden from everyone. There is a rough draft of how
IP addresses may be shown to users who need to see them. This currently details allowing administrators, checkusers, stewards and those with a new usergroup to view the full IP address of unregistered users. Editors with at least 500 edits and an account over a year old will be able to see all but the end of the IP address in the proposal. The ability to see the IP addresses hidden behind the mask would be dependent on agreeing to not share the parts of the IP address they can see with those who do not have access to the same information. Accessing part of or the full IP address of a masked editor would also be logged. Comments on the draft are being welcomed
at the talk page.
Arbitration
The community authorised
COVID-19 general sanctions have been superseded by the
COVID-19 discretionary sanctions following a
motion at a case request. Alerts given and sanctions placed under the community authorised general sanctions are now considered alerts for and sanctions under the new discretionary sanctions.
Welcome, subscribers, to the sixth Discontent Content newsletter! Discontent Content is a newsletter aiming to collate and improve Wikipedia articles in need of more eyes and hands to get them in shape. Its unique trimodal structure allows editors to work where they feel comfortable -- with stubs and starts needing to be brought to standard, mid-quality articles with Good or Featured potential, or quality-assessed articles needing help to maintain their status.
Category 1
Articles in this category are those that need to be brought up to a minimum quality standard. Some will be stubs; others will be longer articles that nonetheless have significant concerns putting them far below B- or C-class adequacy.
This issue's Category 1 articles are:
Floating match on card: This famous magic trick is a microstub with an empty section and no meaningful discussion of its methods or effects. Some useful information is available on the talk page.
Erotic horror: A significant literary (or, well...look, you know) genre with significant academic and critical coverage, which you wouldn't know from reading its three-sentence article.
Black ribbon: Currently in poor shape, with unnecessary lists attracting spurious examples, this article nonetheless has potential to cover a coherent topic on a sensitive subject.
Category 2
Articles in this category, while in better current shape than Category 1, are still missing something. They have the potential to be truly high-quality content, and may have been at one point. With work, they can be brought up to dizzying heights.
This issue's Category 2 articles are:
Violin: This twice-candidate at GAN has good bones, but suffers from expanses of uncited content (and indeed expanses of "people slapping CN tags on literally every sentence"). Much of this information should be citable, and potential exists for this article to stand tall amongst other core music articles.
Art museum: Though this looks a little underrated as a soi-disant "Start", it's nonetheless an important cultural article with significant improvement potential. This was a former candidate for the
Team-B-Vital campaign ran by members of the Wikimedia Discord to bring Vital Articles to B-class status, and while not selected, it has strong potential for anyone interested in working on it.
Grocery store: Daily life has always been one of Wikipedia's coverage gaps. Though this topic is something virtually anyone deals with on a regular basis, the article struggles with cleanup tags, sandwiching, and the weird fear of prose that drives people to put everything they can in a list. With hundreds of views a day, readers deserve an article with a stronger core.
Category 3
Articles in this category have been assessed through a content review process in the past, but may require work to be brought up to current GA/FA standard. Editors can help bring them to a level where the star or plus near their names can once again shine.
This issue's Category 3 articles are:
Slackers CDs and Games: This GA hasn't had significant content edits since 2008. As much of its content references then-recent controversies, it needs a good look for updating.
Potential superpowers: GA with a multiple issues template, with concerns of outdated information, lack of citations, and potential OR.
Alzheimer's disease: This major medical FA is at FAR due to outdated information, an unfortunately common scourge of medical articles over time. Such an important article needs people willing to get it in good shape.
Letter from the Editor
After my prior thoughts on GA sweeps and their viability, work is beginning to break down what parts of the backlog can be tackled. Planning is beginning at
User:Vaticidalprophet/GA reform and its talk; feel free to give your opinion, participate in current GARs, and assess articles. The
current plan is to look at GAs with outstanding cleanup tags as our first priority.
Sorry for the delay this time around -- I've been having A Month healthwise. I expect to maintain this at an approximately monthly schedule and will try not to let it slip further. I'm enthused by the work going on at GAR lately and hope to work something excellent out of it. Vaticidalprophet 01:54, 26 July 2021 (UTC)reply
An
RfC is open to add a delay of one week from nomination to deletion for
G13 speedy deletions.
Technical news
Last week all wikis were very slow or not accessible for 30 minutes. This was due to server lag caused by regenerating
dynamic lists on the Russian Wikinews after a large bulk import. (
T287380)
Hi, I'm hosting an online meetup this Saturday;
meta:Meetup/UK Teams/1. Let me know if you can attend and feel free to spread the word.
Rubbish computerPing me or leave a message on my
talk page 11:50, 3 August 2021 (UTC)reply
@
Rubbish computer Sorry, I'm not able to make it on Saturday. I did put a
geonotice on the watchlist for you though, that's usually one of the main ways I notify people about the meetups I host. Hope it goes well!
the wub"?!" 21:27, 5 August 2021 (UTC)reply
No worries, and cheers for adding the notice.
Rubbish computerPing me or leave a message on my
talk page 21:29, 5 August 2021 (UTC)reply
Campaigns Product Update #1
Hello Campaigns Newsletter recipients. We are ready to share our first updates:
We have published our first document about the first feature: event registration. You can find the document on Meta:
https://meta.wikimedia.org/wiki/Campaigns/Foundation_Product_Team/Registration . We provided first responses to initial feedback last week. If you responded before, consider reviewing the talk page and adding to the conversation.
We had several presentations at Wikimania:
Ilana Fried presented the Campaign Product team as part of a larger conversation about Wikimedia Foundation Product Strategy. Campaigns product start at 18:12 time:
https://www.youtube.com/watch?v=57GzJ4GEvCQ&t=1103
What is next? At the office hours, we will share our first version of the designs for the Registration feature, and be asking for feedback. Additionally we will be onboarding our engineering team who will be building the registration feature.
A
discussion is open to decide when, if ever, should discord logs be eligible for removal when posted onwiki (including whether to oversight them)
A
RfC on the next steps after the trial of
pending changes on
TFAs has resulted in a 30 day trial of automatic semi protection for TFAs.
Technical news
The Score extension has been re-enabled on public wikis. It has been updated, but has been placed in safe mode to address unresolved security issues. Further information on the security issues can be found on the
mediawiki page.
Arbitration
A request for comment is in progress to provide an opportunity to amend the structure, rules, and procedures of
the Arbitration Committee election and resolve any issues not covered by existing rules. Comments and new proposals are welcome.
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 deleted 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. Moxy- 13:18, 8 September 2021 (UTC)reply
Following
an RfC, extended confirmed protection may be used preemptively on certain
high-risk templates.
Following
a discussion at the Village Pump, there is consensus to treat discord logs the same as IRC logs. This means that discord logs will be oversighted if posted onwiki.
A
motion has standardised the 500/30 (extended confirmed) restrictions placed by the Arbitration Committee. The standardised restriction is now listed in
the Arbitration Committee's procedures.
Following the closure of the
Iranian politics case, standard discretionary sanctions
are authorized for all edits about, and all pages related to, post-1978 Iranian politics, broadly construed.
The Arbitration Committee
encourages uninvolved administrators to use the discretionary sanctions procedure in topic areas where it is authorised to facilitate consensus in RfCs. This includes, but is not limited to, enforcing sectioned comments, word/diff limits and moratoriums on a particular topic from being brought in an RfC for up to a year.
Miscellaneous
Editors
have approved expanding the trial of Growth Features from 2% of new accounts to 25%, and the share of newcomers getting mentorship from 2% to 5%. Experienced editors are invited to
add themselves to the mentor list.
The
community consultation phase of the 2021 CheckUser and Oversight appointments process is open for editors to provide comments and ask questions to candidates.
Welcome to the nineteenth newsletter from the
Growth team!
The Growth team's objective is to work on software changes that help retain new contributors in Wikimedia projects.
Structured tasks
"
Add an image" prototype, showing suggested image for the article
"
Add a link" is the team's first structured task. It uses machine-learning to suggest wikilinks as easy edits for newcomers. It was deployed in May 2021 on four Wikipedias and then in July on eight more Wikipedias after we evaluated the
initial results. So far, we've seen a high level of engagement from newcomers. Communities that have the feature suggested valuable ideas for improvement. We'll work on improvements and then contact more communities to deploy it.
"
Add an image" is the team's second structured task, currently in development. It is an editing task that suggests Commons images for unillustrated Wikipedia articles. We have conducted many community discussions and tests. Then, we've decided to build a first prototype. We'll first deploy it only to our pilot Wikipedias, to learn whether newcomers can be successful with the task. The project page contains
links to interactive prototypes. We are very interested to hear your thoughts on this idea as we build and test the early versions. These prototypes have already been tested by newcomers, in English and Spanish.
News for mentors
The
Mentor dashboard is available at our pilot wikis: Arabic, Czech, and Bengali Wikipedias. It will soon be available at a few more volunteering wikis, as a test.
[5]
At wikis where the mentor dashboard is deployed, a new filter is available for mentors. Mentors can monitor their mentees' activity in Watchlist and RecentChanges, so they can help support their mentees' work. For privacy reasons, this filter can't be accessed by someone else than the mentor itself. This filter only filters mentees assigned to the mentor. This filter is not visible for people who are
not listed as mentors[6]
Community configuration
Communities now have the ability to configure how Growth features behave on their own wikis. At
Special:EditGrowthConfig, community members can
add a list of volunteer mentors, alter the templates used for suggested edits, update help links, and more. This special page is editable by administrators and interface admins.
Scaling
We are proud to announce that all Wikipedias now have the Growth features! Thank you to all the community members who helped the team build the features and bring them to their wikis. The only exception is Chinese Wikipedia (zh), for technical reasons.
[7]
The wikis that have
Growth features deployed have been part of A/B testing since deployment, in which some newcomers did not receive the new features. Now, all of the newcomers on 280 of the smallest of those Wikipedias have the features.
[8][9]
A test is undergoing at English Wikipedia: 25% of newcomers receive the Growth features. The results from this test will be part of a discussion of how to proceed on that wiki.
Now that Growth features are available at Wikipedia, the Growth team considers to extend them to other projects. Some Wikisource users have expressed some interest in getting Growth features. There is currently a
discussion about implementing them on Wikisource.
News for communities
Do you have questions about the Growth features?
This translatable FAQ contains answers to the most common questions about the Growth team work.
The Growth features were recently used in a test amongst Latin American donors to give donors the opportunity to learn to edit.
You can see the results here.
Interface translations are important for newcomers. Please help for your language, by
translating or copyediting interface translations for the Growth features.
Help:GettingStarted was a feature developed in 2013, which directed newcomers to articles that needed editing. We recently removed this feature from all wikis, because it has been replaced by the Growth features.
Hello Campaigns Product Newsletter subscribers! We are excited to share our updates:
Request for Feedback: We have shared our project principles, wireframes for the desktop version, and open questions for you about the team’s event registration project. See the latest status updates
here.
Wireframes are design tools that imagine the future interface of the software. We haven’t built anything yet. We need your feedback on these designs so that we can make better product decisions. You can give feedback on the talk page regarding the design and features of the wireframes. We would love to hear your comments to help us establish the next necessary steps for the project.
Presentations: The Campaign Product team participated in
WikiArabia 2021 and
WikiConference North America 2021 to give a brief introduction on how the team works. Senior Program Strategist
Alex Stinson gave an overview about campaigns and how we can scale the organizing experience within the Movement. Senior Product Manager
Ilana Fried gave an introduction about the Product Team and the project wireframes of the first campaign software solution: the on-wiki registration tool. View the recorded presentation
here.
Team update: We have hired our first team engineer,
JCarvalho and our campaign organizing fellow,
IBrazal. Newsletter updates will be done by
IBrazal and she will be coordinating with you! We hope to have the rest of the engineering team onboard soon! For those of who missed the last Campaign Office Hour, you may
watch the recording to know more about the Campaign Product Team.
What is next?
Testers Needed! We will be partnering with
YUX, a design research agency, to learn how our team can improve the experience of Wikimedia campaign organizers and participants in Africa. For this reason, we are looking for community members who are willing to be part of the rapid testing sessions. Preferably, we want organizers and editors who have worked in an African context. If you would like to participate in testing, please email ibrazal-ctrwikimedia.org.
Upcoming Conferences.
Wiki Indaba 2021. This year, the conference will be held virtually on November 5-7, 2021 with the theme "Rethink + Reset : Visions of the future". Read more about the conference
here or
register to join the event. We will be presenting the registration features on Sunday November 7.
We will also be attending
Wikimedia CEE Online Meeting 2021, which will be held virtually again this year on November 5-7, 2021. We will be presenting the registration tool on November 6 as part of our communication and sharing process.
Translation Support. We are also beginning to translate the updates on Registration. If you think your language community would benefit from updates, please translate
here.
Invite other organizers to
subscribe to this newsletter for updates!
Phase 2 of the 2021
RfA review has commenced which will discuss potential solutions to address the 8 issues
found in Phase 1. Proposed solutions that achieve consensus will be implemented and you may propose solutions till 07 November 2021.
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.
If you wish to participate in the 2021 election, please review
the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{
NoACEMM}} to your user talk page.
MediaWiki message delivery (
talk) 00:08, 23 November 2021 (UTC)reply
On-wiki Registration Wireframes (Request for Feedback)
Hello!
We are very excited to share with you the wireframes for the desktop version of the On-Wiki Registration Tool. Feel free to share your feedback on this update. Results of these feedback will help determine the next steps we take. Thank you in advance!
Unregistered editors using the mobile website are now able to receive notices to indicate they have talk page messages. The notice looks similar to what is already present on desktop, and will be displayed on when viewing any page except mainspace and when editing any page. (
T284642)
The limit on the number of emails a user can send per day has been made global instead of per-wiki to help prevent abuse. (
T293866)
The already authorized standard
discretionary sanctions for all pages relating to the
Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes), broadly construed,
have been made permanent.
A
recently closed Request for Comment (RFC) reached consensus to remove
Autopatrolled from the administrator user group. You may, similarly as with
Edit Filter Manager, choose to
self-assign this permission to yourself. This will be implemented the week of December 13th, but if you wish to self-assign you may do so now. To find out when the change has gone live or if you have any questions please visit the
Administrator's Noticeboard. 20:07, 7 December 2021 (UTC)
Happy Christmas!
Season's Greetings
Wishing everybody a Happy Holiday Season, and all best wishes for the New Year!
Adoration of the Kings (Bramantino) is my Wiki-Christmas card to all for this year.
Johnbod (
talk) 14:50, 22 December 2021 (UTC)reply
Thanks
Johnbod, Merry Christmas and a very Happy New Year to you as well!
the wub"?!" 23:53, 22 December 2021 (UTC)reply
Hello The Wub, warm wishes to you and your family throughout the holiday season.
Whispyhistory (
talk) 07:03, 24 December 2021 (UTC)reply
Thanks
Whispyhistory, I hope you have a great Christmas and a happy New Year too!
the wub"?!" 15:03, 24 December 2021 (UTC)reply
Merchandise giveaway nomination
A token of thanks
Hi The wub! I've nominated you (along with all other active admins) to receive a solstice season gift from the WMF. Talk page stalkers are invited to comment at the nomination. Enjoy! Cheers, {{u|Sdkb}}talk ~~~~~