As most of you know (hopefully), anonymous editing on mobile has been
enabled for all projects (except Korean Wikipedia). One of the side effects
of this is that there has been an increase in vandalism that uses emoji (
https://en.wikipedia.org/wiki/Emoji). Much of this vandalism is not caught
by existing AbuseFilter filters. I encourage all projects to add new
AbuseFilter filters for detecting emoji, and either showing a warning or
preventing such edits.
The Unicode range for all emoji characters is [🌀-🙏🚀-🛳☀-➿], although you
may need to customize this for your particular project. For example, the
emoji characters ★ and ☆ are commonly used in Japanese song titles.
Feel free to steal the filter currently in use on English Wikipedia:
It is very important to us at the Editing Department that VisualEditor
in every language, for every user.
VisualEditor's editing environment is a browser ContentEditable element.
This means that your input method editor
<https://en.wikipedia.org/wiki/Input_method> (IME) should already know how
to work with it. However, to make VisualEditor correctly edit wiki pages,
we have to stop browsers in lots of ways from breaking the page.
Sometimes this can interfere with IMEs. To make sure we work in your IME,
we need your help: please see
This is the core system inside VisualEditor which lets you write and edit.
It is different from the full editor, and some of the tools you are used to
will be missing.
We're interested in particular in whether you can write text at all, what
happens when you select different candidate texts, and how VisualEditor
behaves in general.
More details, and some early test results, are provided here:
We would love to hear from every language, and especially languages which
use IMEs, like Japanese, Korean, Indic languages, Arabic and others. Thank
you for your help.
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
Hello Mobile fans :)
Florian and and myself earlier created a draft for a Mobile Newsletter:
https://www.mediawiki.org/wiki/Mobile/Newsletter -- it is currently a bit
outdated since it has been around for a while. Given the comments on phab
ticket. https://phabricator.wikimedia.org/T93529, it is likely that this
needs to be streamlined with other newsletters, however, meanwhile the
coordination, please check and let me know:
1. What would be the best approach to create it --agree on sections (new
features, testing, etc) where volunteers, PMs and CL add details to?
2. This format is too detailed? Too brief? What else do we need to see on
a newsletter for mobile?
Obviously, it has to be made mobile friendly, as well. :)
Comments, suggestions, thoughts?
The latest tech newsletter is ready for early translation:
Direct translation link:
I'm planning to send the newsletter on Monday afternoon (UTC), i.e.
Monday morning PST. The existing translations will be posted on the
wikis in that language.
There may be a few more edits by tomorrow (Friday), but the existing
content should generally remain fairly stable. I'll let you know
tomorrow in any case.
Let me know if you have any questions, comments or concerns. As
always, I appreciate your help and feedback.
---------- Forwarded message ----------
From: Brad Jorsch (Anomie) <bjorsch(a)wikimedia.org>
Date: Wed, Apr 15, 2015 at 12:51 PM
Subject: [Wikimedia-l] User manipulation of change tags, coming soon
to a wiki near you
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikimedia
Mailing List <wikimedia-l(a)lists.wikimedia.org>
Thanks to some hard and awesome work by This, that and the other (a.k.a
TTO), the long-requested feature of allowing users to add and remove change
tags (see T20670 <https://phabricator.wikimedia.org/T20670>) has been
merged and should be rolled out with 1.26wmf3.
Tags defined by MediaWiki or extensions, such as "HHVM", "visualeditor", or
"mobile edit", cannot be added or removed by this feature. Only tags
specifically activated for the purpose may be added, and only those tags or
tags that are unknown to MediaWiki beyond being on some existing revisions
may be removed.
Management of such tags is already available to users with the
'managechangetags' right (admins by default) via Special:Tags.
Tagging and untagging of individual revisions and log entries will come
with 1.26wmf3. Tags may be applied by users with the 'applychangetags'
right when making an edit, and existing revisions and log entries may be
tagged and untagged by users with the 'changetags' right via an interface
much like that for revision deletion. Both of these rights are granted to
all logged-in users by default.
If the default assignment of these rights is a concern for the community of
any WMF-hosted wiki, please follow the procedure at
request the necessary configuration change.
For API users, the relevant modules include action=managetags, action=tag,
: See https://www.mediawiki.org/wiki/MediaWiki_1.26/Roadmap for the
: By default there is no UI provided on the edit screen, but gadgets
may add a 'wpChangeTags' field with a comma-separated list of tags. API
users may use the new 'tags' parameter to action=edit.
for help, and post questions to mediawiki-api
Brad Jorsch (Anomie)
Wikimedia-l mailing list, guidelines at:
The much anticipated migration of all accounts to global, also known as
single-user login finalization, is happening next week. The renaming is
scheduled to begin on Wednesday, 15 April, and is expected to last about a
week, although realistically it could take anywhere from three days to two
weeks. We shall see.
2.8 million accounts were contacted on their talk pages about impeding
renaming over three weeks ago, and if email was confirmed they received an
email notification as well. Since then ~1.34 million accounts have either
merged and attached or been renamed.
~1.46 million accounts will be renamed next week. They will still be able
to log in with old credentials, which will then provide information about
the account renaming. All accounts will also receive a talk page notice
about the renaming, and invite them to request a new name if they choose.
Please help translate this into your language if it's not done so yet:
All the technical things are on Phabricator:
Let me know if you have any questions.
Community Liaison, Product