Hello,
Thank you to everyone who participated and supported the #WeMissTurkey
efforts marking the one-year anniversary of the block in Turkey of all
language versions of Wikipedia. The Wikimedia Foundation remains committed
to restoring access to Wikipedia in full, upholding our values and stance
against censorship, and supporting the local Wikimedia community in Turkey.
As part of our ongoing efforts, we have been monitoring discussions and
mentions in the media around Wikipedia in Turkey. Last Friday, May 18, the
Turkish Minister of Transport, Maritime, and Communications, Ahmet Arslan,
made a number of incorrect comments[0] to the press in Turkey about
Wikimedia and the block of Wikipedia. Minister Arslan’s position includes
oversight of the BTK, the Internet Regulatory Agency that sought the block
of Wikipedia.
The Foundation has replied to the Minister’s statements with an open letter
sent to the Minister and shared with the media who covered the Minister's
statements. The statement has also been shared with the local Wikimedia
community in Turkey, and we have posted it on the Wikimedia Blog in both
English[1] and Turkish[2] to address any further public confusion.
We will continue to keep you updated as we work with the local community to
monitor the situation, and take appropriate actions to restore access to
Wikipedia in Turkey.
Thank you,
Eileen
[0] https://www.ntv.com.tr/teknoloji/bakan-ahmet-arslandan-wikipedia-
aciklamasi,UaPHfIgSq0yDPoVfXo5SOw
[1] https://blog.wikimedia.org/2018/05/22/a-letter-to-
minister-ahmet-arslan/
[2] https://blog.wikimedia.org/tr/2018/05/22/bakan-ahmet-arslan-
vikipedi-dunyadaki-herkes-tarafindan-gelistirilmeye-aciktir-ve-turkiyedeki-
editorler-icin-de-acik-olmalidir/
Hi everyone!
I'm very happy to announce that the Affiliations Committee has recognized
[1] Wikimedia Community User Group Tanzania [2] as a Wikimedia User Group.
The group aims to promote the Wikimedia movement in Tanzania, creating
awareness of Wikimedia projects among Tanzanians and developing
Tanzania-related content on Wikimedia projects in Swahili and English.
Please join me in congratulating the members of this new user group!
Regards,
Kirill Lokshin
Chair, Affiliations Committee
[1]
https://meta.wikimedia.org/wiki/Affiliations_Committee/Resolutions/Recognit…
[2] https://meta.wikimedia.org/wiki/Wikimedia_Community_User_Group_Tanzania
*We at the Wikimedia Foundation are pleased that organizations across the
world are currently rethinking their privacy policies. We have always
strongly valued the privacy of our volunteers, readers, and donors, but
this moment has given us an opportunity to look at our own privacy policy
and see how it can be strengthened.*
We see privacy as an important foundation for intellectual freedom, and we
believe that the trust of our community is deeply linked to several
practices:
* We intentionally collect very little data about readers and contributors,
and provide a transparent view of the data we keep—and do not keep.
* We work with our communities and invite open community vetting of our
privacy-related policies.
* We remain accountable to the community, including a volunteer ombudsman
commission that responds to any reported privacy-related concerns.
* We support our open source platform, which among other benefits, allows
anyone to examine and discover any vulnerabilities in our code.
We do not allow third-party tracking of visitors to our sites. We have
short data retention periods (see our data retention guidelines[1]).
We proactively publish a transparency report[2], informing the public about
requests for data about our contributors. We have a comprehensive privacy
policy[3], developed with community input.
We are always looking for ways to improve our privacy and data security
practices in partnership with our community of contributors and users.
As a result of our most recent review, we are updating our privacy policy,
which now clarifies the definition of “personal information,” and has been
reorganized to improve readability without changing the overall intentions
previously set by the community. As promised[4] in the policy, we are
providing these minor changes with three (3) calendar days’ prior notice.
These changes will go into effect on May 24, 2018. As always, we want your
thoughts and feedback, and invite everyone to comment on the policy talk
page[5] over the next thirty (30) calendar days. We are also grateful to
our volunteer community, who are actively working on translations of this
policy.
We will continue looking for ways to improve and help make clearer to
everyone our privacy practices and policy as technology and the world
change rapidly around us.
Look out for more updates here on the Wikimedia-l mailing list to learn
more about our approach to privacy and data security practices.
[1] https://meta.wikimedia.org/wiki/Data_retention_guidelines
[2] https://transparency.wikimedia.org/
[3] https://meta.wikimedia.org/wiki/Privacy_policy
[4] https://wikimediafoundation.org/wiki/Privacy_policy#Changes_to_
This_Privacy_Policy
[5] https://wikimediafoundation.org/wiki/Talk:Privacy_policy
--
Tony Sebro
Deputy General Counsel
Wikimedia Foundation
1 Montgomery Street, Suite 1600
San Francisco, CA 94104
tsebro(a)wikimedia.org
(415)839-6885 ext. 6784
*NOTICE: This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal and ethical
reasons, I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
<https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer>.*
*We at the Wikimedia Foundation are pleased that organizations across the
world are currently rethinking their privacy policies. We have always
strongly valued the privacy of our volunteers, readers, and donors, but
this moment has given us an opportunity to look at our own privacy policy
and see how it can be strengthened.*
We see privacy as an important foundation for intellectual freedom, and we
believe that the trust of our community is deeply linked to several
practices:
* We intentionally collect very little data about readers and contributors,
and provide a transparent view of the data we keep—and do not keep.
* We work with our communities and invite open community vetting of our
privacy-related policies.
* We remain accountable to the community, including a volunteer ombudsman
commission that responds to any reported privacy-related concerns.
* We support our open source platform, which among other benefits, allows
anyone to examine and discover any vulnerabilities in our code.
We do not allow third-party tracking of visitors to our sites. We have
short data retention periods (see our data retention guidelines[1]).
We proactively publish a transparency report[2], informing the public about
requests for data about our contributors. We have a comprehensive privacy
policy[3], developed with community input.
We are always looking for ways to improve our privacy and data security
practices in partnership with our community of contributors and users.
As a result of our most recent review, we are updating our privacy policy,
which now clarifies the definition of “personal information,” and has been
reorganized to improve readability without changing the overall intentions
previously set by the community. As promised[4] in the policy, we are
providing these minor changes with three (3) calendar days’ prior notice.
These changes will go into effect on May 24, 2018. As always, we want your
thoughts and feedback, and invite everyone to comment on the policy talk
page[5] over the next thirty (30) calendar days. We are also grateful to
our volunteer community, who are actively working on translations of this
policy.
We will continue looking for ways to improve and help make clearer to
everyone our privacy practices and policy as technology and the world
change rapidly around us.
Look out for more updates, both here and on the Wikimedia-l mailing list,
to learn more about our approach to privacy and data security practices.
[1] https://meta.wikimedia.org/wiki/Data_retention_guidelines
[2] https://transparency.wikimedia.org/
[3] https://meta.wikimedia.org/wiki/Privacy_policy
[4]
https://wikimediafoundation.org/wiki/Privacy_policy#Changes_to_This_Privacy…
[5] https://wikimediafoundation.org/wiki/Talk:Privacy_policy
--
Tony Sebro
Deputy General Counsel
Wikimedia Foundation
1 Montgomery Street, Suite 1600
San Francisco, CA 94104
tsebro(a)wikimedia.org
(415)839-6885 ext. 6784
*NOTICE: This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal and ethical
reasons, I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
<https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer>.*
_______________________________________________
Please note: all replies sent to this mailing list will be immediately directed to Wikimedia-l, the public mailing list of the Wikimedia community. For more information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
_______________________________________________
WikimediaAnnounce-l mailing list
WikimediaAnnounce-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
To Whom It May Concern,
I would like to propose to cooperate on the development and maintenance of
Validbook.
The proposal is available at:
https://docs.google.com/document/d/19pJ3_xMyNX-bAZSHTXvnwr5x
LWsV-ShVv3Vy1S4gN6E/edit?usp=sharing
The alpha version of Validbook is available at: http://futurama1x.validboo
k.org/
The code is available at: https://github.com/Validbo
okFoundation/Validbook-Services-Backend and https://github.c
om/ValidbookFoundation/Validbook-Services-Frontend
Validbook definitions
Main definition: Validbook – a universal platform for cooperation.
Functional definition: Validbook is a suite of protocols and services used
to enhance cooperation between things, people and virtual entities.
Validbook slogan: Do important stuff with confidence.
Validbook mission: To improve cooperation between things, people and
virtual entities by making it more transparent and reliable and to support
unalienable human rights among which are the right for Self-Sovereign
Identity, Life, Liberty and the pursuit of Happiness.
The crux of Validbook idea
- Use graph analysis to prove the unique representation of a human
individuals by digital self-sovereign identities
- Distribute tokens among self-sovereign identities that proved to uniquely
represent human individuals, in a such way that incentivizes participation
of people in Validbook tokens distribution and makes tokens valuable
- Use tokens to fund development and maintenance of Validbook services
- Use tokens to align interest of Validbook maintainers and developers with
interests of Validbook users and Validbook mission
This proposal was originally published at W3C Credentials Community Group
mailing list (https://lists.w3.org/Archives/Public/public-credentials/201
8May/0024.html), where technical standards for Self-Sovereign Identity,
Verifiable Credentials are being created.
As Validbook's governance and policies are inspired by Wikipidea/Wikimedia
example, I hope it is suitable to discuss the idea of Validbook and
"Proposal to cooperate on the development and maintenance of Validbook"
here. To discuss technical details of Validbook Statements and Identity
please use W3C CCG mailing list.
See full proposal at:
https://docs.google.com/document/d/19pJ3_xMyNX-bAZSHTXvnwr5x
LWsV-ShVv3Vy1S4gN6E/edit?usp=sharing
--
Bohdan Andriyiv
Validbook Foundation
P.S.
Adding a few clarifications in anticipation of the most likely reservations
and questions:
*- Q.* Is it an ICO scam?
A. No.
*- Q*. The Validbook name sounds a lot like Facebook. Is it an open source
clone of Facebook with a coin attached to it?
A. No, it is not a Facebook clone. Social networking service is only one
part of Validbook that may or may not used by Validbook users. Validbook
Social Service is a social networking service that combines UX features
from Twitter, Pinterest, Facebook. By using Validbook books, Validbook
channels and other Validbook-specific UX features, Validbook Social Service
provides a new, functionally unique, universal, low engaging UX solution
for posting (information dissemintation/signalling) and following
(information consumption/screening).
*- Q.* Who stands behind Validbook? Why did they do it? How did they do it?
What are their incentives?
A. Who? - Validbook was created (designed and speced out) by Bohdan
Andriyiv. Why? - Long story short, about 5-6 years ago I was bored and
wanted to work on something complex from technical and social point of
view. Validbook is a result of continuous evolution of UX design changes
and me trying to understand how people, technology (especially trustworthy
computing) and economics work. At the beginning I was doing it part time
and for the last 10 months full time. How? - It was developed with the help
of small team of freelance and for the last 10 months full time developers.
Incentives? - besides doing something interesting, and having satisfaction
from seeing something cool and useful like Validbook built; Kudos -
afterall, they are forever.
*- Q.* Is Validbook doable? It looks like this idea is too gigantic, not
realistic.
A. Yes, it is doable. Taking into considerations developments in the area
of trustworthy computing (DLT), self-sovereign identity, verifiable
credentials, graph analysis capabilities, and the general state of the
Internet, I do not see reasons why Validbook cannot be done.
*- Q.* Will arbiters, graph analysis work against Sybil attacks?
A. In short – it remains to be seen. Long answer - as of now, there are
no definitive proofs that arbiters and graph analysis will work against
Sybil attacks. It can only be checked in practice. I think, initially,
about 95-98% of identities with SURLHI claim will be real (which is good
enough to deem kudos distribution fair and for kudos to be valued). With
time as practices and tools to do graph analysis and check SURLHI claim
become better, close to 100% of identities with SURLHI claim will be real.
I do not have hard mathematical way to prove it. It is an intuitive
understanding, based on the fact that we can show to an arbiter paths
between identity with SURLHI claim and Giant Component (graph component
that includes known valid and trustworthy identities). It will be the most
important way to eliminate fake identities and communities of fake
identities as they will not have many connections to the Giant Component.
On Facebook real people generally do not add unknown/fake identities to
their friends, this will be even more so when endorsing SURLHI as it is
*much more official*. Also, arbiters will be able to see and evaluate
shortest paths between identity in question and known high trustworthy
identities (for example, path between identity that claims to be a student
of some university and the president of that university). Graph analysis is
a natural, "evolutionary fun" activity for people, so arbiters will have
easy time to uncover false SURLHI claims. Also, the fact that we have quite
precise estimates of human population in different localities and in the
world allows to put an upper limit on possible number of fake identities.
After all, maybe not perfect analogy, but the fact that Wikipedia works,
gives me hope that arbiters and Validbook in general will work also.
*- Q.* Validbook idea looks interesting, but so far it is a private work,
basically a one man job. It needs to be a community work.
A. Definitely, yes. It needs to be developed with community's input and
supervision, and also more directly via open Kudos tenders and bounties.
Development and maintenance of Validbook should be done in open and
transparent way, similar to how Wikipedia is developed.
*Dear participants of the Wikimedia Conference,Dear Wikimedians, I am happy
to announce that we have just published the report for the Movement
Strategy Track at
WMCON.https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018/Documentati…
<https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018/Documentation/Mov…>
The documentation for the other tracks will be coming up within the next
two weeks, and I am currently working with all speakers and hosts to
finalize their session reports. The report is pretty extensive and if you’d
print it, over 100 pages long. This is mostly due to the vast quantity of
data the participants of the Strategy Track have produced together, and of
course also due to the excellent work of our facilitators and harvesters
Bhav, Luis, Rob, Olha and Anna Lena and the unique photos taken by Jason.
**The summary at the beginning will help you find your way through the
report, and through each single session of the track.**The Strategy Core
Team will provide an update on the coming steps in the process following
this email, so stay tuned! Happy reading, and please feel invited to leave
any feedback and questions on the talk page. Best,Cornelius *--
Cornelius Kibelka
Program and Engagement Coordinator (PEC)
for the Wikimedia Conference
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
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, Steuernummer 27/029/42207
The English Wikipedia has finally returned to economics topics:
---------- Forwarded message ----------
From: Weeklypedia Digest <weeklypedia(a)hatnote.com>
Date: Fri, May 18, 2018 at 4:20 AM
Subject: Weeklypedia English #218
the WEEKLYPEDIA
Issue 218, May 18, 2018 (English Wikipedia edition)
Hello there! Welcome to our weekly digest of Wikipedia activity.
ARTICLES
This week, 112,696 authors made 823,694 changes to 396,351 different
articles. The top 20 articles for the week:
1. Corporate haven (766 changes by 4 authors)
2....