Meta:Babel
- You can comment here in any language.
- This forum is primarily for discussion of Meta policies and guidelines, and other matters that affect more than one page of the wiki.
- If your comment only relates to a single page, please post it on the corresponding discussion page (if necessary, you can provide a link and short description here).
- For notices and discussions related to multilingualism and translation, see Meta:Babylon and its discussion page.
- For information about how to indicate your language abilities on your user page ("Babel templates"), see User language.
- To discuss Wikimedia in general, please use the Wikimedia Forum.
- Consider whether your question or comment would be better addressed at one of the major Wikimedia "content projects" instead of here.
 |
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 30 days.
|
| Wikimedia Foundation social media strategy |
| Wikimedia Social Suite |
| Meetup |
| Babel |
| Distribution list |
| ComCom |
| Mailing lists |
|---|
| Overview |
| Administration |
| Standardization |
| List info template |
| Unsubscribing |
| Wikimedia IRC |
| Channels listing |
| #wikidata-admin |
| #wikimedia-admin |
| #wikipedia-en-admins |
| Channel operators |
| #wikimedia-admin |
| #wikipedia-en-admins |
| #wikipedia and #wikipedia-en |
| Instructions |
| Guidelines |
| #wikipedia |
| Group Contacts |
| Noticeboard & Log |
| Cloaks |
| Bots |
| FAQ |
| Stalkwords |
| WikiLounge (WMCS-based IRC web client and bouncer) |
| Quotes (en) |
| archives |
| Quotes (fr) |
| Other social networks |
| Discord |
| Matrix.org |
| Signal |
| Steam |
| Telegram |
| [Edit] |
RFC about AI-generated content in Wikimedia Commons
[edit]You are invited to participate in a request for comment on Wikimedia Commons about a policy update for AI content. This may affect files that are uploaded to Wikimedia Commons for use on this project. Thank you. Codename Noreste (talk) 17:11, 23 June 2026 (UTC)
Request for translation: Education Newsletter June 2026
[edit]The June 2026 education newsletter has been released for translation. Please help our readers to read education newsletter in their native language. The latest education newsletter is ready for translation: here Newsletter headlines link for translation: here, to read individual articles check out: Category:Education/Newsletter/June 2026. Your support in making this newsletter multilingual means a lot. Thanks for helping share knowledge across borders! Regards, ZI Jony (Talk) 04:15, 28 June 2026 (UTC)
Unsubsted usernames in MassMessages
[edit]Shouldn't there be a rule against having {{PAGENAME}} instead of {{subst:PAGENAME}} in MassMessages? The problem is that the PAGENAME may change if the message is archived, moved, quoted etc. Jonteemil (talk) 00:29, 14 July 2026 (UTC)
Set filter 246 to show CAPTCHA or to warn the user?
[edit]Looking at the log of Special:AbuseFilter/246, I encounter a mix of nonsense, vandalism, test edits, and similar stuff. Therefore, I would like to propose that we set that filter to either:
- Show the CAPTCHA, or…
- …warn the user, using the standard warning message.
Thank you. Codename Noreste (talk) 19:41, 16 July 2026 (UTC)
- Neither. A tag seems more appropriate here. EggRoll97 (talk) 19:58, 17 July 2026 (UTC)
Revoking J ansari's GRN permissions
[edit]Hi, this message is to inform the community that I've started Requests for comment/Revoking J ansari's global renamer rights, due to a history of poor renames and communication. All users are welcome to comment.
Best, //shb (t • c) 10:43, 19 July 2026 (UTC)
This section is resolved and can be archived. If you disagree, replace this template with your comment. 🪶-TΛNBIRUZZΛMΛN (💬) 09:42, 21 July 2026 (UTC) Enable UserPageEditProtection
[edit]Hi. two weeks ago, the configuration option $wgRestrictUserPageEditing was added, allowing the restriction of the "User" namespace to the user themselves and certain user groups.
Since this is already enforced on Meta anyway, using Special:AbuseFilter/161 and Special:AbuseFilter/87, I propose enabling this on the server-side. The permission would be granted to every group that includes the "autopatrol" right.
The benefit would be that users receive a permission error *before* they make the edit, rather than afterwards. Neriah - 💬 - 08:27, 21 July 2026 (UTC)
- Seems a bit of a 'blunt' tool, when our filters already have multiple carve outs for exemptions that would go away. — xaosflux Talk 10:32, 21 July 2026 (UTC)
- No, thanks. A server-side hardcoded limit means lower client-side dynamicity. Admins can actively check for edge cases themselves in the filter logs, but for non-publicly-logged limitations they'd have to passively wait for the affected to make a report. NguoiDungKhongDinhDanh 17:29, 21 July 2026 (UTC)