User talk:Callanecc
 | Callanecc is busy and may not respond swiftly to queries. |  |
| This is Callanecc's talk page, where you can send them messages and comments. |
|
Archives (index): 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28Auto-archiving period: 32 days  |
 | If you wish to discuss or inform me of a sensitive or private matter please read User:Callanecc/Emailnotice before emailing me. |
 |
 | This user talk page might be watched by friendly talk page stalkers which means that someone other than me might reply to your query. Their input is welcome and their help with messages is appreciated. |
Close of Kallas birthplace naming RFC
[edit]Hey, I hope I am not bothering you with this, but I wonder how you claim that rfc should only be taken to be about this article rather than applying more broadly to any other article or the topic more generally
when the decision is based on policy that isn’t directly related to her personal background.
Those policies would also apply to other articles of people from the same place, I would think, and the logical outcome would be that those get the same treatment. I think it does set a precedent, because if others don’t follow the same procedure, there would be an inconsistency in policy.
In my view this also touches on the broader rfc that is currently ongoing, and perhaps you cannot comment on that, but in my view that would be the arena where a standard for all these BLP infoboxes is set. I also want to ask about that rfc, because there they also claim it is unrelated to the one you closed, but I don’t want to seem to be taking sides in that rfc (yet). I’m just a bit confused. Slomo666 (talk) 09:28, 19 March 2026 (UTC)
- The reason I added that in there is that a number of participants (on both sides) indicated that they thought this article was a special case as there was additional context around her and the way she and her background are discussed in sources. I think it's likely that the RFC would be referred to in a wider discussion but I felt it was clear from reviewing arguments that this was an agreement about how to best apply the topic-wide RFC and other policies to this article. Callanecc (talk • contribs • logs) 07:25, 22 March 2026 (UTC)
Administrators' newsletter – April 2026
[edit]News and updates for administrators from the past month (March 2026).
Administrator changes
Checkuser changes
Oversight changes
Guideline and policy news
- The content of Wikipedia:Writing articles with large language models has been updated following a request for comment. It now prohibits using LLMs to generate content, with exceptions for translation and copy-editing.
Arbitration
- Following a motion, the GSCASTE extended-confirmed restriction in the Indian military history case has been narrowed. It now applies to caste-related topics in South Asia, and the preemptive protection remedy has been amended accordingly.
- The arbitration case Pbsouthwood has been closed.
- The arbitration case Maghreb has been opened. Evidence submissions in this case will close on 7 April.
Tech News: 2026-15
[edit]Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
- The CampaignEvents extension now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in the documentation.
The new watchlist labels feature (announced in Tech News 2026-07) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via EditWatchlist. In all three places it is a new field following the expiry field.
View all 23 community-submitted tasks that were resolved last week. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [1]
Updates for technical contributors
- The sub-referencing feature, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to more wikis later this year. Wikis using the Reference Tooltips gadget are encouraged to update their version (typically at MediaWiki:Gadget-ReferenceTooltips.js as shown here) to ensure compatibility. Other reference-related gadgets may also be affected. [2]
- All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. Read more.
- The Action API has had several formats for requested output. One of them,
format=php, is being removed soon. Please ensure your scripts or bots use the JSON format. This removal should affect very few scripts and bots. [3] - The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [4]
- Detailed code updates later this week: MediaWiki
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 16:17, 6 April 2026 (UTC)
Feedback request: Wikipedia policies and guidelines request for comment
[edit]
Your feedback is requested at Wikipedia:Reliable sources/Noticeboard on a "Wikipedia policies and guidelines" request for comment. Thank you for helping out!
You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name.
(replacing Yapperbot) SodiumBot (botop|talk|contribs) 10:31, 8 April 2026 (UTC)
Tech News: 2026-16
[edit]Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
- Experienced editors are invited to test the Article guidance feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are available. Also, after reviewing the outlines, please provide feedback on the project talk page. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out the video explaining the feature.
Updates for editors
- On most wikis, all autoconfirmed users can now use Special:ChangeContentModel page to create new pages with custom content models, such as mass message lists, making custom page formats more accessible. Check Special:ListGroupRights for the status of your wiki. [5]
- The Growth team has launched an account creation experiment to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
- View all 30 community-submitted tasks that were resolved last week. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed. [6]
Updates for technical contributors
- Starting later this week, Edit filter managers who have the Improved Syntax Highlighting beta feature enabled will have CodeMirror instead of CodeEditor as the editor at Special:AbuseFilter. This is part of the broader effort to make the user experience more consistent across all editors. [7][8]
- Tools and bots that access the Notifications API (
action=query&meta=notifications) will need to update their OAuth or BotPassword grants to also include access to private notifications. [9] - Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia). [10]
- Detailed code updates later this week: MediaWiki
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.