Short version : We need to find solutions to avoid so many africans
being globally IP blocked due to our No Open Proxies policy.
Long version :
I'd like to raise attention on an issue, which has been getting worse in
the past couple of weeks/months.
Increasing number of editors getting blocked due to the No Open Proxies
In particular africans.
In February 2004, the decision was made to block open proxies on Meta
and all other Wikimedia projects.
According to theno open proxiespolicy : Publicly available proxies
(including paid proxies) may be blocked for any period at any time.
While this may affect legitimate users, they are not the intended
targets and may freely use proxies until those are blocked [...]
Non-static IP addresses or hosts that are otherwise not permanent
proxies should typically be blocked for a shorter period of time, as it
is likely the IP address will eventually be transferred or dynamically
reassigned, or the open proxy closed. Once closed, the IP address should
According to the policy page, « the Editors can be permitted to edit by
way of an open proxy with the IP block exempt flag. This is granted on
local projects by administrators and globally by stewards. »
I repeat -----> ... legitimate users... may freely use proxies until
those are blocked. the Editors can be permitted to edit by way of an
open proxy with the IP block exempt flag <------ it is not illegal to
edit using an open proxy
Most editors though... have no idea whatsoever what an open proxy is.
They do not understand well what to do when they are blocked.
In the past few weeks, the number of African editors reporting being
blocked due to open proxy has been VERY significantly increasing.
New editors just as old timers.
Unexperienced editors but also staff members, president of usergroups,
organizers of edit-a-thons and various wikimedia initiatives.
At home, but also during events organized with usergroup members or
trainees, during edit-a-thons, photo uploads sessions etc.
It is NOT the occasional highly unlikely situation. This has become a
There are cases and complains every week. Not one complaint per week.
Several complaints per week.
*This is irritating. This is offending. This is stressful. This is
disrupting activities organized in _good faith_ by _good people_,
activities set-up with _our donors funds. _**And the disruption**is
primarlly taking place in a geographical region supposingly to be
nurtured (per our strategy for diversity, equity, inclusion blahblahblah). *
The open proxy policy page suggests that, should a person be unfairly
blocked, it is recommended
* * to privately email stewards(_AT_)wikimedia.org.
* * or alternatively, to post arequest (if able to edit, if the editor
doesn't mind sharing their IP for global blocks or their reasons to
desire privacy (for Tor usage)).
* * the current message displayed to the blocked editor also suggest
contacting User:Tks4Fish. This editor is involved in vandalism
fighting and is probably the user blocking open proxies IPs the
most. See log
Option 1: contacting stewards : it seems that they are not answering. Or
not quickly. Or requesting lengthy justifications before adding people
to IP block exemption list.
Option 2: posting a request for unblock on meta. For those who want to
look at the process, I suggest looking at it  and think hard about
how a new editor would feel. This is simply incredibly complicated
Option 3 : user:TksFish answers... sometimes...
As a consequence, most editors concerned with those global blocks...
stay blocked several days.
We do not know know why the situation has rapidly got worse recently.
But it got worse. And the reports are spilling all over.
We started collecting negative experiences on this page .
Please note that people who added their names here are not random
newbies. They are known and respected members of our community, often
leaders of activities and/or representant of their usergroups, who are
confronted to this situation on a REGULAR basis.
I do not know how this can be fixed. Should we slow down open proxy
blocking ? Should we add a mecanism and process for an easier and
quicker IP block exemption process post-blocking ? Should we improve a
process for our editors to pre-emptively be added to this IP block
exemption list ? Or what ? I do not know what's the strategy to fix
that. But there is a problem. Who should that problem be addressed to ?
Who has solutions ?
You can find this message translated into additional languages on Meta-wiki.
• Please help translate to your language
Hi everyone! The Ombuds commission (OC) and the Case Review Committee (CRC)
are looking for members. People are encouraged to nominate themselves or
encourage others they feel would contribute to these groups to do so. There
is more information below about the opportunity and the skills that are
About the Ombuds commission
The Ombuds commission (OC) works on all Wikimedia projects to investigate
CheckUser <https://meta.wikimedia.org/wiki/CheckUser_policy> and Oversight
<https://meta.wikimedia.org/wiki/Oversight_policy> (also known as
Suppression) tools. The Commission mediates between the parties of the
investigation and, when violations of the policies are identified, advises
the Wikimedia Foundation on best handling. They may also assist the General
Counsel, the Chief Executive Officer, or the Board of Trustees of the
Foundation in these investigations when legally necessary. For more on the
OC's duties and roles, see Ombuds commission on Meta-Wiki
Volunteers serving in this role should be experienced Wikimedians, active
on any project, who have previously used the CheckUser/Oversight tools OR
who have the technical ability to understand these tools and the
willingness to learn them. They must be able to communicate in English, the
common language of the commission. They are expected to be able to engage
neutrally in investigating these concerns and to know when to recuse when
other roles and relationships may cause conflict. Commissioners will
terms (note that this is different from past years, when the terms have
been for one year).
About the Case Review Committee
The Case Review Committee (CRC) reviews appeals of eligible Trust & Safety
office actions. The CRC is a critical layer of oversight to ensure that
Wikimedia Foundation office actions are fair and unbiased. They also make
sure the Wikimedia Foundation doesn’t overstep established practices or
boundaries. For more about the role, see Case Review Committee on Meta-Wiki
We are looking for current or former functionaries and experienced
volunteers with an interest in joining this group. Applicants must be
fluent in English (additional languages are a strong plus) and willing to
abide by the terms of the Committee charte
If the work resonates and you qualify, please apply. Committee members will
serve two-year terms (note that this is different from past years, when the
terms have been for one year).
Applying to join either of these groups
Members are required to sign the Confidentiality agreement for nonpublic
and must be willing to comply with the appropriate Wikimedia Foundation
board policies (such as the access to non-public information policy
<https://foundation.wikimedia.org/wiki/Privacy_policy>). These positions
require a high degree of discretion and trust. Members must also be over 18
years of age.
If you are interested in serving in either capacity listed above, please
write in English to the Trust and Safety team at ca[image: @]wikimedia[image:
.]org (to apply to the OC) or to the Legal Team at legal[image:
.]org (to apply to the CRC) with information about:
Your primary projects
Languages you speak/write
Any experience you have serving on committees, whether movement or
Your thoughts on what you could bring to the OC or CRC if appointed
Any experience you have with the Checkuser or Oversight tools (OC only)
Any other information you think is relevant
There will be two conversation hours to answer any questions that potential
applicants may have:
17 October 2022, 03:00 UTC (other timezones
<https://iw.toolforge.org/zonestamp/1665975648>) (Zoom meeting link)
(add to calendar)
16 November 2022, 18:00 UTC (other timezones
<https://iw.toolforge.org/zonestamp/1668621642>) (Zoom meeting link)
(add to calendar)
The deadline for applications is 31 December 2022 in any timezone.
Please feel free to pass this invitation along to any users who you think
may be qualified and interested. Thank you!
On behalf of the Committee Support team,
Trust & Safety Specialist
Over the last few months, a small team at the Wikimedia Foundation has been
working on a project that has been discussed by many people in our movement
for many years: building ‘enterprise grade’ services for the high-volume
commercial reusers of Wikimedia content. I am pleased to say that in a
remarkably short amount of time (considering the complexity of the issues:
technical, strategic, legal, and financial) we now have something worthy of
showing to the community, and we are asking for your feedback. Allow me to
introduce you to the Wikimedia Enterprise API project – formerly codenamed
While the general idea for Wikimedia Enterprise predates the current
movement strategy process, its recommendations identify an enterprise API
as one possible solution to both “Increase the sustainability of our
movement” and “Improve User Experience.” That is, to simultaneously
create a new revenue stream to protect Wikimedia’s sustainability, and
improve the quality and quantity of Wikimedia content available to our many
readers who do not visit our websites directly (including more consistent
attribution). Moreover, it does so in a way that is true to our movement’s
culture: with open source software, financial transparency, non-exclusive
contracts or content, no restrictions on existing services, and free access
for Wikimedia volunteers who need it.
The team believes we are on target to achieve those goals and so we have
written a lot of documentation to get your feedback about our progress and
where it could be further improved before the actual product is ‘launched’
in the next few months. We have been helped in this process over the last
several months by approximately 100 individual volunteers (from many
corners of the wikiverse) and representatives of affiliate organisations
who have reviewed our plans and provided invaluable direction, pointing out
weaknesses and opportunities, or areas lacking clarity and documentation in
our drafts. Thank you to everyone who has shared your time and expertise to
help prepare this new initiative.
A essay describing the “why?” and the “how?” of this project is now on
Also now published on Meta are an extensive FAQ, operating principles, and
technical documentation on MediaWiki.org. You can read these at   and
 respectively. Much of this documentation is already available in
French, German, Italian, and Spanish.
The Wikimedia Enterprise team is particularly interested in your feedback
on how we have designed the checks and balances to this project - to ensure
it is as successful as possible at achieving those two goals described
above while staying true to the movement’s values and culture. For example:
Is everything covered appropriately in the “Principles” list? Is the
technical documentation on MediaWiki.org clear? Are the explanations in the
“FAQ” about free-access for community, or project’s legal structure, or the
financial transparency (etc.) sufficiently detailed?
Meet the team and Ask Us Anything:
The central place to provide written feedback about the project in general
is on the talkpage of the documentation on Meta at:
On this Friday (March 19) we will be hosting two “Office hours”
conversations where anyone can come and give feedback or ask questions:
13:00 UTC via Zoom at https://wikimedia.zoom.us/j/95580273732
22:00 UTC via Zoom at https://wikimedia.zoom.us/j/92565175760 (note:
this is Saturday in Asia/Oceania)
Other “office hours” meetings can be arranged on-request on a technical
platform of your choosing; and we will organise more calls in the future.
We will also be attending the next SWAN meetings (on March 21)
also the next of the Wikimedia Clinics
Moreover, we would be very happy to accept any invitation to attend an
existing group call that would like to discuss this topic (e.g. an
affiliate’s members’ meeting).
On behalf of the Wikimedia Enterprise team,
Peace, Love & Metadata
-- Liam Wyatt [Wittylama], Wikimedia Enterprise project community liaison.
*Liam Wyatt [Wittylama]*
WikiCite <https://meta.wikimedia.org/wiki/WikiCite> Program Manager & Wikimedia
Enterprise <https://meta.wikimedia.org/wiki/Okapi> Community Liaison
Please join me in welcoming Luis Bitencourt-Emilio to the Wikimedia
Foundation Board of Trustees. Luis was unanimously appointed to a 3-year
term and replaces a board-selected Trustee, Lisa Lewin, whose term ended in
November 2021 .
Currently based in São Paulo, Luis is the Chief Technology Officer at Loft,
a technology startup in the real-estate industry. He brings product and
technology experience from a globally diverse career that has spanned large
technology companies including Microsoft, online networking sites like
Reddit, and a series of entrepreneurial technology ventures focused in the
USA and Latin America. Luis has led product and technology teams across
Latin America, the United States, Europe and Asia. He is passionately
involved in building and promoting the entrepreneurial ecosystem for Latin
Luis has more than two decades of experience across product development,
software engineering, and data science. At Microsoft, he led engineering
teams shipping multiple Microsoft Office products. At Reddit, he led the
Knowledge Group, an engineering team that owned critical functions such as
data, machine learning, abuse detection and search. He was deeply involved
in Reddit’s growth stage and worked closely with Reddit’s communities in
that evolution. Luis also co-founded a fintech startup to help millennials
manage and automate their finances.
His career has also been shaped by a visible commitment to recruiting
diverse leaders. At Reddit, Luis was a key member of the recruitment
efforts that achieved equal representation of women engineering directors.
Luis says his proudest achievement at Microsoft was building their
Brazilian talent pipeline by working closely with local universities to
place thousands of engineering candidates at Microsoft, as well as his
involvement in expanding global recruitment to markets including Ukraine,
Poland, Great Britain, the EU and Mexico.
Luis was educated in Brazil and the United States, receiving a Bachelor of
Science in Computer Engineering with Honors from the University of
Maryland. He is fluent in Portuguese, Spanish and English. He is also a
proud father and dog lover.
I would like to thank the Governance Committee, chaired by Dariusz
Jemielniak, for this nomination process as well as volunteers in our
Spanish and Portuguese speaking communities who also met with Luis or
shared their experiences.
You can find an official announcement here .
PS. You can help translate or find translations of this message on
 Lisa Lewin served from January 2019 till November 2021:
antanana / Nataliia Tymkiv
Chair, Wikimedia Foundation Board of Trustees
*NOTICE: You may have received this message outside of your normal working
hours/days, as I usually can work more as a volunteer during weekend. You
should not feel obligated to answer it during your days off. Thank you in
Here is a quick update on Outreachy Round 25: we recently concluded the
final call for projects and mentors and are now promoting 6 projects led by
14 mentors. If you know someone who cleared the Outreachy's initial
eligibility check, encourage them to explore the Wikimedia projects below:
- Create a web application for editing Toolhub records, mentored by:
Slavina Stefanova, Damilare Adedoyin, Roy Smith
- Develop features for Wiki Loves Monuments app, mentored by: Ederporto,
- Rewrite Imagebulk tool to scale up, mentored by: Jay Prakash,
- Write a Ruby gem for analyzing Wikidata edits, mentored by: Sage Ross,
- Develop a web app for patrolling based on the new ML-based service to
predict reverts, mentored by: Diego Saez-Trumper, Muniza A.
- Hybrid event production for QueeringWikipedia 2023, mentored by: Z.
Blace, Owen Blacker, Freddy eduardo
If you are interested in any of these projects, you can either subscribe to
the related Phabricator tickets or share your ideas and suggestions in a
Learn more here: <https://www.mediawiki.org/wiki/Outreachy/Round_25> 
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
As others mentioned in the thread, WMF can't enforce this directly as it is
not the copyright holder. However, in past instances, we have raised the
issue with Google (similar to the KPN example) and will do so for this one
I am meeting with Google later today and will flag this to remind them of
the copyright obligations that come with using this text.
Thanks for surfacing this,
On Tue, Aug 30, 2022 at 12:58 PM <wikimedia-l-request(a)lists.wikimedia.org>
> Send Wikimedia-l mailing list submissions to
> To subscribe or unsubscribe, please visit
> You can reach the person managing the list at
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikimedia-l digest..."
> Today's Topics:
> 1. Re: Is GoogleTV violating Wikipedia's license? (Peter Southwood)
> 2. Re: Is GoogleTV violating Wikipedia's license? (Ciell Wikipedia)
> 3. Re: [Small Wiki Toolkit] Writing Wikidata Queries Using WDQS Tool
> Workshop On Tuesday, August 30th, 16:00 UTC
> (Seyram Komla Sapaty)
> Message: 1
> Date: Tue, 30 Aug 2022 11:18:53 +0200
> From: "Peter Southwood" <peter.southwood(a)telkomsa.net>
> Subject: [Wikimedia-l] Re: Is GoogleTV violating Wikipedia's license?
> To: "'F. Xavier Dengra i Grau'" <xavier.dengra(a)protonmail.com>,
> "'Wikimedia Mailing List'" <wikimedia-l(a)lists.wikimedia.org>
> Message-ID: <002201d8bc51$8963c6a0$9c2b53e0$(a)telkomsa.net>
> Content-Type: multipart/alternative;
> If I understand the CC-by-sa licence correctly, Wikipedia and WMF
> themselves do not own the copyright, it is owned by the contributors who
> created the text. They can take this up with Google, the WMF cannot. If you
> are one of those contributors you can approach Google as misusing your
> Cheers, Peter
> From: F. Xavier Dengra i Grau via Wikimedia-l [mailto:
> Sent: 29 August 2022 19:00
> To: Wikimedia Mailing List; legal(a)wikimedia.org
> Cc: F. Xavier Dengra i Grau
> Subject: [Wikimedia-l] Is GoogleTV violating Wikipedia's license?
> Hi all,
> I want to bring a legal concern here on Google's misuse of our content. It
> came up today <
> on Twitter that the GoogleTV app had linked a movie description text in
> Catalan language (which in principle it should be good news regarding
> language normalization). However, shortly after a wikipedian colleague
> realised that the text was fully taken by the Catalan Wikipedia. Once I
> downloaded the app by myself, I double-checked that Google does not specify
> anywhere (or at least that I could find minimally visible) that those lines
> belong to Wikipedia: neither the origin, the license, nor a link to the
> full article or to the CC license.
> I'd like to recall the licensing footpage on Wikipedia (Text is available
> under the Creative Commons Attribution-ShareAlike License 3.0 <
> ) and its conditions, as well as to ask others to check whether there's
> more situations like this one. It's worth noting how wrong this is to
> minoritised language Wikipedias: not only the legal issue itself, but also
> the lack of legitimate clicks and views that we end up losing, the
> confusion and misunderstandings from the readers that think this is a win
> by Google (the example I shared, with both screenshots enclosed), and even
> a subsequent chicken-and-egg situation that can lead to deleted articles by
> some users thinking that the content was stolen from Google and not
> actually the opposite.
> I remember that there was a previous thread here, not so long ago, about
> the problems of Google taking over our data and therefore diminishing
> clicks to the Wikimedia projects. Considering that I am fully against the
> GAFAM-drift that the WMF is increasingly adopting by benefiting from Google
> in our human, economical and digital structures, I prefer to share it here
> as well -and not only to the legal team of the WMF (cced).
> Kind regards,
> Xavier Dengra
> Virus-free. <
The last & final feedback session on the "Small wiki toolkits" (SWT)
workshop series is coming up - it will take place on Friday, October 28th,
at 16:00 UTC. You can find more details on the workshop and a link to join
This workshop will gather feedback on the SWT workshop series around bots
and scripts development, ongoing since January 2022. There will be a
discussion around the following:
- Overall feedback on the workshop series
- Technical topics you would like to see the SWT team focus on by
running workshops or developing resources in 2023
- Your preferred learning formats
This session does not require attendance in previous workshops to
participate. We look forward to your participation!
On behalf of the SWT Workshops Organization team
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
We launched WIKIMOVE six months ago, our first podcast around movement
strategy, and have since then invited over ten guests to discuss the
future of the Wikimedia movement. In the spirit of recommendation #10
‘Evaluate, Iterate, Adapt” we created an evaluation survey that will
help us adapt our podcast to your needs and wishes:
We look forward to hearing your feedback on how to improve our podcast
in the future!
Thank you for your support.
Your WIKIMOVE Team
Nicole, Nikki & Eva
Director Movement Strategy and Global Relations
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 30 577 11 62-0
Keep up to date! Current news and exciting stories about Wikimedia,
Wikipedia and Free Knowledge in our newsletter (in German):
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e.
V. Eingetragen im Vereinsregister des Amtsgerichts
Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig
anerkannt durch das Finanzamt für Körperschaften I Berlin,