Re: [Wikimedia-l] Blocks of new accounts in Angola?

[John]

Let's wait and see what the IP info says. Might be  case of an ISP routing
everyone thru a  single public IP.  Or it might be a range block due to ip
hoping disruption.

On Wed, Feb 22, 2017 at 8:11 AM Vi to  wrote:

> Yep, none of them implied massive and preventive blocks. There's something
> broken needing further investigations then.
>
> Vito
>
> 2017-02-22 16:17 GMT+01:00 Yaroslav Blanter :
>
> > Did not we have some mass vandalism from Angola some time ago, and then
> > measures had to be taken? I do not remember the details.
> >
> > Cheers
> > Yaroslav
> >
> > On Wed, Feb 22, 2017 at 8:57 AM, George William Herbert <
> > george.herb...@gmail.com> wrote:
> >
> > >
> > > Have them hit whatismyip.org and tell us what shows up..,
> > >
> > > Sent from my iPhone
> > >
> > > > On Feb 21, 2017, at 5:58 PM, Rodrigo Tetsuo Argenton <
> > > rodrigo.argen...@gmail.com> wrote:
> > > >
> > > > I've been receiving complains via Facebook from people of Angola
> about
> > > not
> > > > being able to create new accounts, some know something about it? They
> > > > receive the as if the IP was blocked, however we receive more then 5
> > > > complains just in the Commons FB page.
> > > >
> > > > Any ideas?
> > > >
> > > > --
> > > > Rodrigo Tetsuo Argenton
> > > > rodrigo.argen...@gmail.com
> > > > +55 11 979 718 884
> > > > ___
> > > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > > Unsubscribe:
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > 
> > >
> > > ___
> > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > 
> > >
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Blocks of new accounts in Angola?

[John]

I cannot locate the original block in question but
https://en.wikipedia.org/w/index.php?title=Special:Log/block&page=User%3A105.172.16.0%2F20
is now affecting the IP in question and it does look related to the
copyright violation issue previously brought up in this thread.

On Sun, Mar 5, 2017 at 6:16 AM, Rodrigo Tetsuo Argenton <
rodrigo.argen...@gmail.com> wrote:

> In reality:
>
> "Account creation from IP addresses in the range 105.172.0.0/16, which
> includes your IP address (105.172.25.219), has been blocked by
> Steinsplitter. "
>
> That was the message most of them do not have a way to enter in the website
> that you requested, by the lack of mobile data...
>
>
>
> On 3 March 2017 at 14:52, Lucas Teles  wrote:
>
> > They were probably caught on this range block:
> > https://commons.wikimedia.org/w/index.php?title=Special:Log&;
> > page=User%3A105.168.0.0%2F16&type=block
> >
> >
> > *Lucas Teles*
> >
> > *+55 (71) 99707 6409Steward at Wikimedia Foundation. Administrator *
> > *at Portuguese Wikipedia and Wikimedia Commons.*- Member of Wikimedia
> > Community User Group Brasil 
> >
> > 2017-02-22 12:54 GMT-03:00 Olatunde Isaac :
> >
> > > In addition to that thread, see also "https://commons.wikimedia.
> > > org/wiki/User:Teles/Angola_Facebook_Case"
> > >
> > > Best,
> > >
> > > Isaac
> > > Sent from my BlackBerry® wireless handheld from Glo Mobile.
> > >
> > > -Original Message-
> > > From: "Olatunde Isaac" 
> > > Date: Wed, 22 Feb 2017 15:30:06
> > > To: Wikimedia Mailing List
> > > Reply-To: reachout2is...@gmail.com
> > > Subject: Re: [Wikimedia-l] Blocks of new accounts in Angola?
> > >
> > > Yes, there are some mass vandalism from Angola last year. Yaroslav, I
> > > think you may be looking for this thread, "
> https://www.mail-archive.com/
> > > wikimedia-l@lists.wikimedia.org/msg23413.html"
> > >
> > > Best,
> > >
> > > Isaac
> > > Sent from my BlackBerry® wireless handheld from Glo Mobile.
> > >
> > > -Original Message-
> > > From: Yaroslav Blanter 
> > > Sender: "Wikimedia-l" Date:
> > Wed,
> > > 22 Feb 2017 16:17:32
> > > To: Wikimedia Mailing List
> > > Reply-To: Wikimedia Mailing List 
> > > Subject: Re: [Wikimedia-l] Blocks of new accounts in Angola?
> > >
> > > Did not we have some mass vandalism from Angola some time ago, and then
> > > measures had to be taken? I do not remember the details.
> > >
> > > Cheers
> > > Yaroslav
> > >
> > > On Wed, Feb 22, 2017 at 8:57 AM, George William Herbert <
> > > george.herb...@gmail.com> wrote:
> > >
> > > >
> > > > Have them hit whatismyip.org and tell us what shows up..,
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Feb 21, 2017, at 5:58 PM, Rodrigo Tetsuo Argenton <
> > > > rodrigo.argen...@gmail.com> wrote:
> > > > >
> > > > > I've been receiving complains via Facebook from people of Angola
> > about
> > > > not
> > > > > being able to create new accounts, some know something about it?
> They
> > > > > receive the as if the IP was blocked, however we receive more then
> 5
> > > > > complains just in the Commons FB page.
> > > > >
> > > > > Any ideas?
> > > > >
> > > > > --
> > > > > Rodrigo Tetsuo Argenton
> > > > > rodrigo.argen...@gmail.com
> > > > > +55 11 979 718 884
> > > > > ___
> > > > > Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/
> > > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > > wiki/Wikimedia-l
> > > > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > > > Unsubscribe: https://lists.wikimedia.org/
> > mailman/listinfo/wikimedia-l,
> > > > 
> > > >
> > > > ___
> > > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > > wiki/Wikimedia-l
> > > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > > Unsubscribe: https://lists.wikimedia.org/
> mailman/listinfo/wikimedia-l,
> > > > 
> > > >
> > > ___
> > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > 
> > > ___
> > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > 

Re: [Wikimedia-l] Using non-free elements vs our values (Apple Maps vs Wikipedia iOS app)

[John]

This reminds me of en wiki's non-free policy.
https://en.wikipedia.org/wiki/Wikipedia:Non-free_content_criteria#1
highlights the point fairly clearly Usage of non-free materials is often
easier and higher quality than using the free equivalent . However
Wikimedia's mission and goal's are to support and promote free content, yes
you will need to jump thru a few more hoops and adds a little more work.
But without those driving factors we will often see the free options wither
and fail.

On Tue, Mar 21, 2017 at 10:22 AM, Dan Garry  wrote:

> Hey Magnus,
>
> There are a few other factors to consider in addition to those listed. For
> example, development cost. Our maps tile service is not compatible with the
> iOS app out of the box. This isn't surprising; Apple wants you to use
> things like Apple Maps rather than your own solution. Android is, by its
> nature, a more open platform, so I am not too surprised that it was easier
> to integrate our tile server into the Android app than the iOS app. Sadly,
> it's not as simple as just switching over to OSM-based tiles; on the
> contrary, it's a significant amount of work.
>
> Now, using our tile service would also have required the iOS app to use the
> MapBox SDK. This is the size of all their other third party libraries
> combined, significantly increasing app download size. The size of your app
> can significantly reduce downloads [1]. Switch a single feature over to a
> different set of map tiles, and possibly decreasing downloads of the app,
> seems like a dangerous and counterintuitive tradeoff to me.
>
> So the question is, given all this, is switching over the nearby feature to
> use OSM-based tiles instead of Apple Maps worth it? In the long run, if
> these problems could be solved, I'd say it absolutely is worth it. But, in
> the short term, the work would take significant time and effort, and could
> actually decrease app usage by decreasing the app download rate; that
> tradeoff doesn't seem worth it to me.
>
> Thanks,
> Dan
>
> Disclaimers: These are my opinions only. I worked on the apps in the past,
> but haven't for two years; my statements about development costs may be
> wrong, and the apps folks may well disagree with me about things. I work in
> the department responsible for Wikimedia maps, but have only worked on the
> team working on maps for a couple of months.
>
> [1]: https://segment.com/blog/mobile-app-size-effect-on-downloads/
>
> On 15 March 2017 at 09:25, Magnus Manske 
> wrote:
>
> > Hi Josh, all,
> >
> > I am not one hell-bent on "FOSS or death"; I tend to use whatever works
> > best.
> >
> > That said, the cost-benefit analysis of using Apple Maps seems to boil
> > down:
> > * Apple Maps has slightly better rendering (didn't check, but I assume)
> > * Apple Maps uses less mobile bandwidth
> > * Apple Maps is not free (as in freedom)
> >
> > Now, looking at these points:
> >
> > * Somewhat better quality is not an argument. If it were, we would have
> > stayed with Britannica, and skipped that whole Wikipedia nonsense.
> > Wikipedia became better, in part, because people actually used it, saw
> the
> > issues, and fixed them. And OSM rendering might be not quite en par with
> > Apple Maps, it is quite usable, in my experience.
> >
> > * Less bandwidth usage is not an argument either. I doubt we are talking
> > about a significant percentage of an average users' data volume here. If
> > Android users can afford the bandwidth, so can people who buy an iPhone
> > (source: used to have iPhone).
> >
> > * The price tag is the "non-freedom". As far as I can tell, this would be
> > the very first Wikimedia "product" that incorporates non-free technology
> > and data. It sets a precedence. It also has the potential to poison the
> > otherwise great relations between the Wikipedia, Wikidata, and OSM
> > community. It says "OSM is not good enough (at least for Apple users)"
> > quite plainly. How would we feel if OSM started to remove Wikidata tags
> and
> > replace them with Britannica links?
> >
> > All in all, IMHO, the cost is too high for the (at best) flimsy benefits.
> >
> > Cheers,
> > Magnus
> >
> >
> > On Wed, Mar 15, 2017 at 12:52 AM Joshua Minor 
> > wrote:
> >
> > > Hello,
> > >
> > > My name is Josh Minor, and I am the Product Manager for the Wikipedia
> iOS
> > > app. I wanted to speak to a couple specific issues and
> misunderstandings
> > > raised by this email thread.
> > >
> > > First, please take a look at
> > > https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS/Maps_service
> > which
> > > provides some background on this decision. Jonatan linked to it, and it
> > > covers several of the concerns raised on the thread and gives our
> > > reasoning. I'd also suggest subscribing to this ticket:
> > > https://phabricator.wikimedia.org/T157763 which Jonatan filed, and
> where
> > > you can track efforts and issues with replacement maps.
> > >
> > > A few clarifying points:
> > >
> > > 1. The Places tab[1], and its use of A

Re: [Wikimedia-l] Using non-free elements vs our values (Apple Maps vs Wikipedia iOS app)

[John]

As a programmer myself I understand that free vs non-free causes more work
for you. However you cannot ignore one of the foundations of the wikimedia
movement because it makes a little more work for you. I honestly don't
understand why you thought that Apple maps would be acceptable at all. You
have both a breach of our privacy policy and a violation of our free
software enforcement policy. Yes using OSM adds work and increases the
download size, but is a valid option. If OSM or other free software wasn't
possible then we might consider non-free  alternatives but that's not the
case.


On Tue, Mar 21, 2017 at 12:18 PM Dan Garry  wrote:

> On 21 March 2017 at 14:34, Gerard Meijssen 
> wrote:
> >
> > Technical considerations are imho less relevant. What trumps it is
> > functionality.
>
>
> Technical considerations are very relevant if one is doing something
> technical, for example developing an iOS app or a maps tile service.
>
>
> > Our maps have to be good everywhere and as far as I know OSM
> > is superior in places where there is profit to be made from maps.
>
>
> If you choose to ignore the technical difficulties and half of my earlier
> email, then yes, that may be true.
>
>
> > Current maps world wide and historical maps are what we need. How would
> you
> > use the Apple maps for a map of the Ottoman empire?
> >
>
> Given that our maps service does not support this, and will not any time
> soon, this is very off-topic.
>
> Dan
>
> --
> Dan Garry
> Lead Product Manager, Discovery
> Wikimedia Foundation
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Let's set up a Tor onion service for Wikipedia

[John]

enabling read access via Tor shouldn't be an issue, however editing should
not be allowed due to high volume of known abuse from that vector.

On Mon, Jun 5, 2017 at 1:43 PM, David Gerard  wrote:

> Editing may be a tricky one, particularly on en:wp, which has found
> Tor exit points to overwhelmingly be fountains of garbage, and
> automatically blocks them.
>
>
> - d.
>
>
> On 5 June 2017 at 18:30, David Cuenca Tudela  wrote:
> > I think that's an excellent idea and very much aligned with our
> commitment
> > to provide free information also for those who are living under
> unfavorable
> > conditions.
> >
> > I personally endorse it.
> >
> > Thanks Cristian for suggesting it.
> >
> > Regards,
> > Micru
> >
> > On Jun 5, 2017 19:11, "Cristian Consonni"  wrote:
> >
> >> Hi,
> >>
> >> I have written a proposal about setting up an onion (hidden) service to
> >> serve Wikipedia over Tor:
> >>
> >> https://meta.wikimedia.org/wiki/Grants:IdeaLab/A_Tor_
> >> Onion_Service_for_Wikipedia
> >>
> >> I was thinking about this and I also discovered that the Internet
> >> Archive is experimenting with a very similar idea:
> >> www.hackerfactor.com/blog/index.php?/archives/750-
> >> Freedom-of-Information.html
> >>
> >> I would like to have some feedback on this, I am also in contact with
> >> the author of the aforementioned proxy which could be able to give some
> >> help in setting it up.
> >>
> >> Thank you.
> >>
> >> Cristian
> >>
> >> ___
> >> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> >> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> >> wiki/Wikimedia-l
> >> New messages to: Wikimedia-l@lists.wikimedia.org
> >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> >> 
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Let's set up a Tor onion service for Wikipedia

[John]

Im not going to violate BEANS, but even allowing accounts to edit without
further hurdles isn't going to work. Because of the anonymity that tor
provides its fairly easy to cause widespread issues. When the vandals start
actually using tactics the flood gates of TOR will cause massive issues
cross wiki that requires steward level intervention on a regular basis.

On Mon, Jun 5, 2017 at 2:53 PM, Gabriel Thullen  wrote:

> I imagine registered users could edit through TOR. That is how it works
> with my school IP: anonymous edits are blocked, account creation as well,
> but you can sign in an edit.
>
> On Mon, Jun 5, 2017 at 7:47 PM, John  wrote:
>
> > enabling read access via Tor shouldn't be an issue, however editing
> should
> > not be allowed due to high volume of known abuse from that vector.
> >
> > On Mon, Jun 5, 2017 at 1:43 PM, David Gerard  wrote:
> >
> > > Editing may be a tricky one, particularly on en:wp, which has found
> > > Tor exit points to overwhelmingly be fountains of garbage, and
> > > automatically blocks them.
> > >
> > >
> > > - d.
> > >
> > >
> > > On 5 June 2017 at 18:30, David Cuenca Tudela 
> wrote:
> > > > I think that's an excellent idea and very much aligned with our
> > > commitment
> > > > to provide free information also for those who are living under
> > > unfavorable
> > > > conditions.
> > > >
> > > > I personally endorse it.
> > > >
> > > > Thanks Cristian for suggesting it.
> > > >
> > > > Regards,
> > > > Micru
> > > >
> > > > On Jun 5, 2017 19:11, "Cristian Consonni" 
> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> I have written a proposal about setting up an onion (hidden) service
> > to
> > > >> serve Wikipedia over Tor:
> > > >>
> > > >> https://meta.wikimedia.org/wiki/Grants:IdeaLab/A_Tor_
> > > >> Onion_Service_for_Wikipedia
> > > >>
> > > >> I was thinking about this and I also discovered that the Internet
> > > >> Archive is experimenting with a very similar idea:
> > > >> www.hackerfactor.com/blog/index.php?/archives/750-
> > > >> Freedom-of-Information.html
> > > >>
> > > >> I would like to have some feedback on this, I am also in contact
> with
> > > >> the author of the aforementioned proxy which could be able to give
> > some
> > > >> help in setting it up.
> > > >>
> > > >> Thank you.
> > > >>
> > > >> Cristian
> > > >>
> > > >> ___
> > > >> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/
> > > >> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > >> wiki/Wikimedia-l
> > > >> New messages to: Wikimedia-l@lists.wikimedia.org
> > > >> Unsubscribe: https://lists.wikimedia.org/
> mailman/listinfo/wikimedia-l
> > ,
> > > >> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=
> unsubscribe>
> > > > ___
> > > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > > Unsubscribe: https://lists.wikimedia.org/
> mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > >
> > > ___
> > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > >
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> >
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Let's set up a Tor onion service for Wikipedia

[John]

Im not going to violate BEANS, but even allowing accounts to edit without
further hurdles isn't going to work. Because of the anonymity that tor
provides its fairly easy to cause widespread issues. When the vandals start
actually using tactics the flood gates of TOR will cause massive issues
cross wiki that requires steward level intervention on a regular basis.

On Mon, Jun 5, 2017 at 2:53 PM, Gabriel Thullen  wrote:

> I imagine registered users could edit through TOR. That is how it works
> with my school IP: anonymous edits are blocked, account creation as well,
> but you can sign in an edit.
>
> On Mon, Jun 5, 2017 at 7:47 PM, John  wrote:
>
> > enabling read access via Tor shouldn't be an issue, however editing
> should
> > not be allowed due to high volume of known abuse from that vector.
> >
> > On Mon, Jun 5, 2017 at 1:43 PM, David Gerard  wrote:
> >
> > > Editing may be a tricky one, particularly on en:wp, which has found
> > > Tor exit points to overwhelmingly be fountains of garbage, and
> > > automatically blocks them.
> > >
> > >
> > > - d.
> > >
> > >
> > > On 5 June 2017 at 18:30, David Cuenca Tudela 
> wrote:
> > > > I think that's an excellent idea and very much aligned with our
> > > commitment
> > > > to provide free information also for those who are living under
> > > unfavorable
> > > > conditions.
> > > >
> > > > I personally endorse it.
> > > >
> > > > Thanks Cristian for suggesting it.
> > > >
> > > > Regards,
> > > > Micru
> > > >
> > > > On Jun 5, 2017 19:11, "Cristian Consonni" 
> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> I have written a proposal about setting up an onion (hidden) service
> > to
> > > >> serve Wikipedia over Tor:
> > > >>
> > > >> https://meta.wikimedia.org/wiki/Grants:IdeaLab/A_Tor_
> > > >> Onion_Service_for_Wikipedia
> > > >>
> > > >> I was thinking about this and I also discovered that the Internet
> > > >> Archive is experimenting with a very similar idea:
> > > >> www.hackerfactor.com/blog/index.php?/archives/750-
> > > >> Freedom-of-Information.html
> > > >>
> > > >> I would like to have some feedback on this, I am also in contact
> with
> > > >> the author of the aforementioned proxy which could be able to give
> > some
> > > >> help in setting it up.
> > > >>
> > > >> Thank you.
> > > >>
> > > >> Cristian
> > > >>
> > > >> ___
> > > >> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/
> > > >> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > >> wiki/Wikimedia-l
> > > >> New messages to: Wikimedia-l@lists.wikimedia.org
> > > >> Unsubscribe: https://lists.wikimedia.org/
> mailman/listinfo/wikimedia-l
> > ,
> > > >> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=
> unsubscribe>
> > > > ___
> > > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > > Unsubscribe: https://lists.wikimedia.org/
> mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > >
> > > ___
> > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > >
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> >
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] What to do when the WMF is stingy with the community?

[John]

David Cuenca Tudela,

Looking at the proposed grant you only asked for 36000, you get that, then
you decided that the WMF is being greedy and you now want more money. If
you need 72,000 should not your initial request realized that and adjusted
the requesting amount accordingly? I will also note that the WMF is fairly
careful on how they send their money because they are accountable for how
its used. Honestly if I had someone coming to me with a estimated price
tag, only to come back fairly quickly with an updated cost of almost double
I would question the persons competence and re-asses the initial decision
to support them.

On Wed, Jun 28, 2017 at 2:41 PM, David Cuenca Tudela 
wrote:

> Hola Ivan,
>
> Así es, la idea es que la WMF pague las becas de viaje para la gente que no
> se lo puede permitir, y el resto de la conferencia lo pagaría la WMDE.
>
> En este caso la cantidad para la bolsa de viaje me parece demasiada baja
> para hacer que este evento (la primera vez que se realiza) funcione
> adecuadamente.
>
> Saludos,
> David
>
> On Wed, Jun 28, 2017 at 8:09 PM, Ivan Martínez  wrote:
>
> > Hola David.
> >
> > Hasta donde entendí está escrito en la subvención solicitada un total de
> 36
> > 000 euros, y el resto iba a ser cubierto por fondos que provienen de
> WMDE.
> > ¿No es así?. Como voluntario del Comité de Subvenciones a Conferencias,
> > quedo pendiente y en consideración de tú comentario.
> >
> > Saludos,
> >
> > 2017-06-28 13:02 GMT-05:00 Dariusz Jemielniak :
> >
> > > hi David,
> > >
> > >
> > > On Wed, Jun 28, 2017 at 7:52 PM, David Cuenca Tudela <
> dacu...@gmail.com>
> > > wrote:
> > >
> > > > Recently the review for the Wikidata conference grant application has
> > > > started, and I have complained that the funds allocated are
> insuficient
> > > to
> > > > cover the needs of the grants. The requested amount for the grants
> was
> > > > 36,000 EUR, but in my opinion that should be at least 72,000 EUR.
> > > >
> > >
> > > You realize that this is pretty much what an annual budget of a small
> > > Wikimedia chapter is, right?
> > >
> > >
> > > > I have the feeling that the WMF is sitting on a pile of money just
> > giving
> > > > breadcrumbs to the community, and the community has to suffer in
> > silence
> > > > about this stinginess.
> > > >
> > >
> > > The WMF, just as the movement, has a responsibility to our donors, to
> > spend
> > > the money wisely and frugally. We surely do not always do so, but we
> try.
> > >
> > >
> > >
> > > > Why are there two standards? One standard seems to be that everything
> > > that
> > > >
> > > the WMF needs to allocate can go unsupervised, whereas another standard
> > > > seems to apply to community activities where every penny is so
> > supervised
> > > > that it becomes a pain in the ass to organize anything big.
> > > >
> > >
> > > The WMF's spending is actually reviewed and commented on by the
> community
> > > and the FDC.
> > >
> > >
> > >
> > > > The Wikidata Conference needs more funds to be a success and I think
> > that
> > > > in the grand scheme of things, the money requested is just peanuts
> > > compared
> > > > to the money that the WMF has collected from donors.
> > > >
> > >
> > > I believe we have a responsibility to treat our donor's contributions
> > with
> > > respect and care. I don't think that 70k Euro is peanuts, and rarely
> you
> > > will find any foundation or NGO considering such an amount to be
> > > insignificant.
> > >
> > >  best,
> > >
> > > dariusz
> > > ___
> > > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > > wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > 
> > >
> >
> >
> >
> > --
> > *Iván Martínez*
> >
> > *Presidente - Wikimedia México A.C.User:ProtoplasmaKid *
> >
> > // Mis comunicaciones respecto a Wikipedia/Wikimedia pueden tener una
> > moratoria en su atención debido a que es un voluntariado.
> > // Ayuda a proteger a Wikipedia, dona ahora:
> https://donate.wikimedia.org
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> >
>
>
>
> --
> Etiamsi omnes, ego non
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wi

Re: [Wikimedia-l] Why are articles being deleted?

[John]

You are overly simplifying things, One can be both, some things just don't
merit an article, an obscure band working out of a member's garage who have
never had an audience of more than 500 shouldn't have an article because
they really are not notable. On the other hand major artist should have
article. Weighting the balance on that line between what should and
shouldn't be kept is up to the community and which is why they have two
sections of the site dedicated to it (articles for discussion, and deletion
review),

If we do not have checks and balances in place wikipedia will quickly get
overrun with articles on everyone and everything to ever exist regardless
of the actual notability of the person/place/thing/event.

On Sat, Jun 25, 2016 at 7:04 PM, Mitar  wrote:

> Hi!
>
> On Twitter I was pointed to:
>
> https://en.wikipedia.org/wiki/Deletionism_and_inclusionism_in_Wikipedia
>
> This is amazing. I think John Oliver should make a segment "Wikipedia
> Deletionism - how is this still a thing?"
>
> I mean, is this a failure of Wikipedia community governance? Reading
> about this seems deletionists are just a vocal minority who benefit
> from the fact that deletion is much stronger action than keeping
> things. Destruction is always easier than creation.
>
> There are 1536 inclusionists just on English Wikipedia:
>
> https://en.wikipedia.org/wiki/Category:Inclusionist_Wikipedians
>
> And 280 deletionists:
>
> https://en.wikipedia.org/wiki/Category:Deletionist_Wikipedians
>
> So, how is this still a thing? How can this be put to a vote and
> finally move on? What is Wikipedia's governance process here? Does
> Wikipedia has something like https://petitions.whitehouse.gov/ ?
>
>
> Mitar
>
> On Sat, Jun 25, 2016 at 12:06 PM, Mitar  wrote:
> > Hi!
> >
> > Thank you for your responses.
> >
> > On Fri, Jun 24, 2016 at 11:29 PM, Brill Lyle 
> wrote:
> >> Please include your user name and the name of the article you were
> working
> >> on. Without any context it's impossible to help you. Thankfully I was
> able
> >> to dig and find the page, etc. But include identifying info if you want
> >> help / resolution.
> >
> > I didn't want to include this information because I didn't want to
> > make it about my issue in particular. I wanted to give feedback and
> > discuss principles behind my experience.
> >
> > I otherwise had good experience editing Wikipedia. Other editors were
> > constructive and often with patience helped me learn how to improve
> > the content and related rules of Wikipedia, which also seemed
> > reasonable. But this rule I do not get and cannot relate to, thus I am
> > bringing it here.
> >
> > I read that Wikipedia is trying hard to get new editors and this is
> > why I am sharing this story here. Because from all my experience this
> > one is the most problematic. It really pushes you off.
> >
> > And it is pretty reasonable that it is problematic. Now that most
> > clearly "notable" articles have been already written the one which are
> > left will be increasingly more and more in the "gray zone". And
> > increasingly local, specialized, where such mistakes might be common.
> >
> > Maybe this policy for notability and significance had its historic
> > place. It focused the community on the core set of articles, improving
> > the quality of existing articles and created a name for Wikipedia. But
> > I think maybe it is time that it is relaxed and a new level of
> > articles is invited in. As I said, a warning could be used to tell
> > readers that they are reading such a new article.
> >
> > (Oh, and please improve talk pages, that way of communicating is also
> > a mess, but that one I can understand, it is a technical legacy. It is
> > cumbersome, but I can understand it. But it does influence other
> > issues then, like this one when you have to discuss something about
> > Wikipedia. Why Wikipedia does not simply use some issue-management
> > system where people could be opening issues for articles and other
> > people and have conversation through that? It would also allow much
> > better statistics of how many issues were satisfactory resolved, for
> > example, for all sides.)
> >
> >> Discussion (with reason):
> >>
> https://en.wikipedia.org/wiki/User_talk:DGG#Please_remove_the_tag_from_Poligon_page
> >
> > Yes, it is clear that the editor who deleted it does not understand
> > local importance of the article. They could read the news articles I
> > cited and might get a better picture.
> >

Re: [Wikimedia-l] Why are articles being deleted?

[John]

Like you where told, Having an article not assert notably, and having an
article be non-notable are effectively the same thing for wikipedia.

You provided several examples specifically cities and plant/animal species,
both of those have inherent notability. However companies do not have such
a default status, thus must assert it. forcing the limited ~500
administrators to review and research each of the 5693 deletions performed
yesterday (of which 1196 where in the main namespace) would place too much
burden on them if the article fails to assert notability or isnt notable
there is no effective difference.

On Sun, Jun 26, 2016 at 4:46 PM, Mitar  wrote:

> Hi!
>
> On Sun, Jun 26, 2016 at 2:14 AM, Vi to  wrote:
> > My activity at en.wiki only deals with crosswiki abuse and lta
> > "management". So don't be afraid of me but frainkly I don't find your
> > startup incubator to be notable. In other words I don't find it to be
> > something I expect to find on an encyclopedia.
>
> He he. No, the startup incubator is in the same building, but one
> floor higher. :-)
>
> http://hekovnik.com/
>
> On Sun, Jun 26, 2016 at 10:30 AM, Brill Lyle 
> wrote:
> > Okay, I did a pretty thorough scrub and reworking of the article. I added
> > the logo as well as moved it to the main space. As it stood the article
> > needed help but of course that's typical of new articles.
> >
> > https://en.wikipedia.org/wiki/Poligon_Creative_Centre
>
> Wow! This is amazing! Thank you so much! The article is alive and so
> much better!
>
> Hm, but while I agree that the article has not been of high quality
> from the start, I am really not sure if the best approach was for it
> to be deleted. What would be a better process in such cases? Why
> articles are not asked to be deleted with more time?
>
> My article was speedy deleted based on:
>
> https://en.wikipedia.org/wiki/Wikipedia:Criteria_for_speedy_deletion#A7
>
> What I do not understand is why there is a speedy deletion if article
> does not explain why the subject of the article is not significant,
> instead of deletion if article's subject is not significant? Because
> the first thing could be improved, it is a content issue?
>
> Anyway, what is the process to improve this process? Or should we just
> leave it be and everything is great?
>
>
> Mitar
>
> --
> http://mitar.tnode.com/
> https://twitter.com/mitar_m
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Concerns in general

[John]

I must say the tone of the initial post to this is alarmingly biased and
almost misleading. Yes the incoming president has placed a hold on
releasing additional material. By no means does that imply that they will
start censoring data that they release or in any way affect the private
sector. Because the incoming president holds a opposite view as the
predecessor it's not surprising that they would want to audit the releases
to ensure that the data has a solid factual grounding. I've lost count of
the number of research studies and papers that I have seen that when
actually placed under a microscope don't hold up. However often the
mainstream media takes these and runs with them.

The United States is based on freedom of the press, not freedom of the
government. there is zero chance that the president will be able to censor
the private sector.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Concerns in general

[John]

Im not sure you are reading section 14 correctly. It makes reference to
Privacy Act (Privacy Act of 1974) and the privacy policy of the federal
agencies involved in immigration enforcement and law enforcement agencies.
IE the government can freely share information between agencies with
regards to non-citizens. If you look at the Privacy Act, it lists twelve
cases where data is permitted to be disclosed by federal agencies, with the
new order it allows all governmental data to be shared between governmental
agencies. Again none of this pertains to the Civilian sector. The Privacy
Shield really has nothing to do with the root issue. United States
governmental agencies sharing information about non-citizens with each
other. In the context of the actual document it is referencing sharing data
about non-citizens who are not legal residents of the United States, who
are illegally in the country.

On Fri, Jan 27, 2017 at 6:13 PM, James Salsman  wrote:

> >... there is zero chance that the president will be able to censor
> > the private sector.
>
> If you mean the U.S. private sector, you're right. But otherwise, the
> U.S. President is allowed to take a whole lot of actions which can
> effectively censor non-citizens, and I've got some bad news pertaining
> to one in particular involving compliance with European privacy
> regulations which could potentially result in the deletion of records
> including accounts of European citizens from hosting providers such as
> Google, Apple, Facebook, Twitter, etc. Please see:
>
> https://www.engadget.com/2017/01/26/trump-signs-executive-
> order-stripping-non-citizens-of-privacy-ri/
>
> "Enforcing privacy policies that specifically 'exclude persons who are
> not United States citizens or lawful permanent residents,' while aimed
> at enhancing domestic immigration laws, effectively invalidates
> America's part of the Privacy Shield agreement, opens the current
> administration up to sanctions by the EU and could lead our allies
> across the Atlantic to suspend the agreement outright."
>
> If Google is forced to delete all the personally identifying
> information of European citizens because the President ordered U.S.
> federal agencies to stop enforcing privacy policies, that would
> effectively be an act of censorship on a scale without historical
> precedent, would it not?
>
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Concerns in general

[John]

The question is: Is it a legitimate issue or a sensationalized mole hill?
Given what I researched I am seeing more of a mole hill. Give it a few
days, odds are there will be clarification and this issue will blow over.

On Fri, Jan 27, 2017 at 7:42 PM, Nathan  wrote:

> On Fri, Jan 27, 2017 at 7:39 PM, John  wrote:
>
> > Im not sure you are reading section 14 correctly. It makes reference to
> > Privacy Act (Privacy Act of 1974) and the privacy policy of the federal
> > agencies involved in immigration enforcement and law enforcement
> agencies.
> > IE the government can freely share information between agencies with
> > regards to non-citizens. If you look at the Privacy Act, it lists twelve
> > cases where data is permitted to be disclosed by federal agencies, with
> the
> > new order it allows all governmental data to be shared between
> governmental
> > agencies. Again none of this pertains to the Civilian sector. The Privacy
> > Shield really has nothing to do with the root issue. United States
> > governmental agencies sharing information about non-citizens with each
> > other. In the context of the actual document it is referencing sharing
> data
> > about non-citizens who are not legal residents of the United States, who
> > are illegally in the country.
>
>
> There are plenty of news reports, available with a moment on Google, that
> discuss the possibility that this executive order prevents the Commerce
> department from fulfilling its enforcement role in the law that replaced
> the Safe Harbor data protection agreement between the EU and the U.S. This
> would invalidate the new agreement, jeopardizing the authorization of US
> companies to handle data on European residents.
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Monetizing Wikimedia APIs

[John]

In cases of excessive resource usage we have several options. Contact the
source, throttle them, or flat out disable access depending on what each
case calls for.

I have seen the dev team to this liberally in the past when needed. If any
one person or group is exploiting us by using unproportionate amounts of
resources  thats one thing, if we are just trying to make money by selling
access to what we already have thats another. Limiting abusive sources
shouldnt be an issue, but as soon as we start selling access we loose sight
of our mission.

On Sat, Jan 16, 2016 at 9:11 PM, Denny Vrandecic 
wrote:

> I find it rather surprising, but I very much find myself in agreement with
> most what Andreas Kolbe said on this thread.
>
> To give a bit more thoughts: I am not terribly worried about current
> crawlers. But currently, and more in the future, I expect us to provide
> more complex and this expensive APIs: a SPARQL endpoint, parsing APIs, etc.
> These will be simply expensive to operate. Not for infrequent users - say,
> to the benefit of us 70,000 editors - but for use cases that involve tens
> or millions of requests per day. These have the potential of burning a lot
> of funds to basically support the operations of commercial companies whose
> mission might or might not be aligned with our.
>
> Is monetizing such use cases really entirely unthinkable? Even under
> restrictions like the ones suggested by Andreas, or other such restrictions
> we should discuss?
> On Jan 16, 2016 3:49 PM, "Risker"  wrote:
>
> > Hmm.  The majority of those crawlers are from search engines - the very
> > search engines that keep us in the top 10 of their results (and often in
> > the top 3), thus leading to the usage and donations that we need to
> > survive. If they have to pay, then they might prefer to change their
> > algorithm, or reduce the frequency of scraping (thus also failing to
> catch
> > updates to articles including removal of vandalism in the lead
> paragraphs,
> > which is historically one of the key reasons for frequently crawling the
> > same articles).  Those crawlers are what attracts people to our sites, to
> > read, to make donations, to possibly edit.  Of course there are lesser
> > crawlers, but they're not really big players.
> >
> > I'm at a loss to understand why the Wikimedia Foundation should take on
> the
> > costs and indemnities associated with hiring staff to create a for-pay
> API
> > that would have to meet the expectations of a customer (or more than one
> > customer) that hasn't even agreed to pay for access.  If they want a
> > specialized API (and we've been given no evidence that they do), let THEM
> > hire the staff, pay them, write the code in an appropriately open-source
> > way, and donate it to the WMF with the understanding that it could be
> > modified as required, and that it will be accessible to everyone.
> >
> > It is good that the WMF has studied the usage patterns.  Could a link be
> > given to the report, please?  It's public, correct?  This is exactly the
> > point of transparency.  If only the WMF has the information, then it
> gives
> > an excuse for the community's comments to be ignored "because they don't
> > know the facts".  So let's lay out all the facts on the table, please.
> >
> > Risker/Anne
> >
> >
> >
> > On 16 January 2016 at 15:06, Vituzzu  wrote:
> >
> > > Thank you for sharing this but, above all, to focus on digging real
> data.
> > >
> > > IMHO we shouldn't forget our mission, so licenses must be as free as
> > > possible. Turning into something "more closed" would definitely deplete
> > one
> > > of the most valuable source (the open source world) of volunteering we
> > have.
> > >
> > > Crawlers' owner should definitely share our increasing expenses but any
> > > kind of agreement with them should include ways to improve our
> userbase.
> > > I'm wondering about an agreement with Google (or any other player) to
> add
> > > an "edit" button to knowledge graph. Sort of a "knowledge vs. users"
> > > agreement.
> > >
> > > So, we definitely need a long term strategy which the Foundation will
> > > pursue in *negotiating* with anyone who wants a big scale access to
> *our
> > > resources* (while access to our knowledge will have no limits, as
> usual).
> > >
> > > Vito
> > >
> > >
> > > Il 16/01/2016 19:21, Lila Tretikov ha scritto:
> > >
> > >> To share some context of the discussion the board had around this -- I
> > >> don't think the minutes give enough detail. APIs -- as we are freely
> and
> > >> rapidly creating them today are important, but are not quite at the
> core
> > >> of
> > >> the issue we are facing.
> > >>
> > >> Today Wikimedia is the largest internet channel for open free
> knowledge
> > in
> > >> the world. But the trends are against us. We have to face them
> together.
> > >> We
> > >> have to have the answers on how. The strategic discussion next week
> will
> > >> help guide us.
> > >>
> > >> Over the last year we looked at the t

[Wikimedia-l] Wayback machine

[John]

Does anyone have contact information for the wayback machine? I am trying
to improve one of my tools for wikipedia, and am wondering if we can get a
minor change/feature request implemented.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Most obnoxious banner yet

[John]

David don't get your hopes up. Given the WMF's tendency to shove idiotic,
untested, and often unwanted software changes down the throats of users
this surprises you at all? Just take a look at how either VE or media
viewer where pushed out. It took the introduction of the super protect
right to ensure that the WMF's edicts are carried out regardless of how it
impacts users or their wishes.
On Dec 31, 2014 2:08 PM, "David Gerard"  wrote:

> On 31 December 2014 at 18:56, Megan Hernandez 
> wrote:
>
> > The large banner is set to only show up one time, regardless if a reader
> > closes the banner or not. Most readers are not seeing these banners
> > anymore.
> > The blue banners at the top of the page do show up more than one time.
> If
> > you close these banners, you won't see anymore banners.
>
>
> So Marc was wrong and this *is* deliberate behaviour?
>
>
> > If the description above is not working for you, please let us know at
> > don...@wikimedia.org so we can follow up.
>
>
> It completely fails ethics and makes people want to put our banners
> into AdBlockPlus, where a substantial proportion of the internet won't
> see them, so it's not really me, is it.
>
>
> > You may be noticing more banners because we have increased the traffic
> > today for a final year-end push.  Banners were running at limited traffic
> > the past two weeks.  The campaign will end today.
>
>
> Blatant stunts like this because it's the last day strikes me as
> utterly unethical behaviour, for what that's worth.
>
> Who coded this? Who approved this? Who thought this was a good decision to
> make?
>
>
> - d.
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Funding bot maintenance

[John]

I am a dev and am willing to replace a tool when it dies. I have a fairly
large infrastructure of code that makes it fairly easy

On Sunday, February 22, 2015, WereSpielChequers 
wrote:

> One of the areas that I would like to see the foundation putting in money
> is for the running and maintenance of wanted orphan bots. Wanted in the
> sense that editors are using them or would if they were still running, and
> orphan in the sense that the original developer isn't around or available
> to run them/migrate them to the latest platform.
>
> If we work on the premise that community funds should go for things that
> volunteers want to have happen but aren't volunteering to do, then this is
> a classic and uncontentious niche. Programmers like to write new code and
> solve new problems, but the person with the idea or who writes new code
> doesn't always have the time and motivation to keep maintaining and running
> that code, let alone creating slightly bespoke version for scores of our
> thousand wikis.
>
> Now it may be that we are in an unusual situation that the migration from
> toolserver to labs has cost us a number of bots that would otherwise have
> continued for years. But there will always be demand to localise existing
> bots for wikis where they don't currently run, and in the long run all of
> our volunteer bot writers are likely to move on.
>
> Employing a python programmer or two somewhere cheap like India or South
> America would not be a huge investment for the foundation, but it would be
> a valuable service to the community, and unlike mediawiki development this
> could be completely volunteer driven with wikimedians deciding which bots
> are worth maintaining and their relative priority.
>
> Disclosure: whilst I'm not pitching for the money for this, I would be
> front of the queue to ask such a maintainer to take on bots that I used to
> use the results of and in at least one case which I designed.
>
> Regards
>
> Jonathan/WereSpielChequers
>
>
> > On 22 Feb 2015, at 11:42, wikimedia-l-requ...@lists.wikimedia.org
>  wrote:
> >
> > Send Wikimedia-l mailing list submissions to
> >wikimedia-l@lists.wikimedia.org 
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> > or, via email, send a message with subject or body 'help' to
> >wikimedia-l-requ...@lists.wikimedia.org 
> >
> >
> >
> > --
> >
> > Message: 3
> > Date: Sat, 21 Feb 2015 17:39:31 -0800
> > From: Erik Moeller >
> > To: Wikimedia Mailing List  >
> > Subject: Re: [Wikimedia-l] [Wikitech-l] Types of allowed projects for
> >grant funding (renamed)
> > Message-ID:
> > >
> > Content-Type: text/plain; charset=UTF-8
> >
> >> On Sat, Feb 21, 2015 at 4:19 PM, MZMcBride  > wrote:
> >>
> >> Erik seems to be pushing toward a model that favors using OAuth and the
> >> MediaWiki API over "deep integration" that comes with a MediaWiki
> >> extension. He recently mentioned this here:
> >>
> https://lists.wikimedia.org/pipermail/glamtools/2015-February/000343.html
> >>
> >> He may be right that development for deployment to the Wikimedia
> >> Foundation cluster may not be the best approach for every project, but I
> >> think this view overlooks all the very real benefits that extension
> >> deployment includes.
> >
> > I don't think one size fits all -- every case needs to be judged on
> > its merits, though in the case of GLAMWikiToolset I am definitely
> > arguing for considering separation from the MediaWiki codebase because
> > it is so highly specialized. I also think we sometimes still have a
> > tendency to underestimate the value of non-MediaWiki tools and apps,
> > even though they've contributed millions of edits to Wikimedia wikis
> > already (though to be fair, without Magnus Manske the tally would not
> > be nearly as awesome).
> >
> > Regarding the criteria for grantmaking, I think this initial blanket
> > prohibition against all MediaWiki extension development is indeed
> > something we ought to revisit. These grants can cover tens of
> > thousands of dollars of paid work, so we shouldn't treat the review
> > and integration burden lightly, and avoiding stalled projects that are
> > going nowhere was a reason I advocated for this restriction to begin
> > with. But as long as there is a good plan in place -- either not
> > significantly dependent on WMF or with clear commitments negotiated
> > upfront -- I do agree that the risks can be significantly mitigated.
> >
> > Damon, Luis and members of their teams will need to weigh in on this,
> > and will want to think through the implications for their respective
> > areas, but it's a good conversation to have -- keeping in mind that
> > Luis is just starting in his new role, so please give him at least a
> > few days to get up to speed. ;-)
> >
> > Erik
> > --
> > Erik Möller
> > VP of Product & Strategy, Wikimedia Foundation
> >
> >
> >
> > -

Re: [Wikimedia-l] Copyright status of the mobile application button icons?

[John]

Most logos are copyrighted even from the WMF, for legal reasons. However
this particular icon is well below the copyright threshold, and thus is not
copyrightable.

On Sat, Apr 18, 2015 at 11:42 AM, Aleksey Bilogur  wrote:

> Hello, what is the copyright status of the application icon for Wikipedia
> mobile applications? This one, specifically, as far as I can tell:
>
> https://en.wikipedia.org/wiki/File:WikipediaMobileAppLogo.png
>
> The copyright information lists it as being fair use, but that seems
> strange to me; is this actually correct?
>
> Apologies for not sending this to mobile-l, my message there was
> auto-bounced and I don't want to go through the subscription process just
> to send one email.
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Fwd: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month

[John]

This is something that the pywiki devs need to fix in compat. Please dont
give me shit about moving to core. I have yet to have it not fatally error
out in less than 10 minutes of using it. There are still a lot of features
that core doesnt have, or that are poorly implemented.

On Tue, Jun 2, 2015 at 8:27 PM, Pine W  wrote:

> Forwarding because of the significance of the change for bots. My
> understanding is that this affects all wikis, so please get this
> information out to relevant bot operators on all wikis. Translated messages
> may be very much appreciated.
>
> Pine
> -- Forwarded message --
> From: "Brad Jorsch (Anomie)" 
> Date: Jun 2, 2015 1:43 PM
> Subject: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for
> action=query will change at the end of this month
> To: "Wikimedia developers" , <
> mediawiki-api-annou...@lists.wikimedia.org>
> Cc:
>
> As has been announced several times (most recently at
> https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081559.html),
> the default continuation mode for action=query requests to api.php will be
> changing to be easier for new coders to use correctly.
>
> *The date is now set:* we intend to merge the change to ride the deployment
> train at the end of June. That should be 1.26wmf12, to be deployed to test
> wikis on June 30, non-Wikipedias on July 1, and Wikipedias on July 2.
>
> If your bot or script is receiving the warning about this upcoming change
> (as seen here
> , for
> example), it's time to fix your code!
>
>- The simple solution is to simply include the "rawcontinue" parameter
>with your request to continue receiving the raw continuation data (
>example
><
>
> https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1
> >).
>No other code changes should be necessary.
>- Or you could update your code to use the simplified continuation
>documented at
> https://www.mediawiki.org/wiki/API:Query#Continuing_queries
>(example
><
> https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=
> >),
>which is much easier for clients to implement correctly.
>
> Either of the above solutions may be tested immediately, you'll know it
> works because you stop seeing the warning.
>
> I've compiled a list of bots that have hit the deprecation warning more
> than 1 times over the course of the week May 23–29. If you are
> responsible for any of these bots, please fix them. If you know who is,
> please make sure they've seen this notification. Thanks.
>
> AAlertBot
> AboHeidiBot
> AbshirBot
> Acebot
> Ameenbot
> ArnauBot
> Beau.bot
> Begemot-Bot
> BeneBot*
> BeriBot
> BOT-Superzerocool
> CalakBot
> CamelBot
> CandalBot
> CategorizationBot
> CatWatchBot
> ClueBot_III
> ClueBot_NG
> CobainBot
> CorenSearchBot
> Cyberbot_I
> Cyberbot_II
> DanmicholoBot
> DeltaQuadBot
> Dexbot
> Dibot
> EdinBot
> ElphiBot
> ErfgoedBot
> Faebot
> Fatemibot
> FawikiPatroller
> HAL
> HasteurBot
> HerculeBot
> Hexabot
> HRoestBot
> IluvatarBot
> Invadibot
> Irclogbot
> Irfan-bot
> Jimmy-abot
> JYBot
> Krdbot
> Legobot
> Lowercase_sigmabot_III
> MahdiBot
> MalarzBOT
> MastiBot
> Merge_bot
> NaggoBot
> NasirkhanBot
> NirvanaBot
> Obaid-bot
> PatruBOT
> PBot
> Phe-bot
> Rezabot
> RMCD_bot
> Shuaib-bot
> SineBot
> SteinsplitterBot
> SvickBOT
> TaxonBot
> Theo's_Little_Bot
> W2Bot
> WLE-SpainBot
> Xqbot
> YaCBot
> ZedlikBot
> ZkBot
>
>
> --
> Brad Jorsch (Anomie)
> Software Engineer
> Wikimedia Foundation
> ___
> Wikitech-l mailing list
> wikitec...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] [Wikitech-l] [Pywikipedia-l] Fwd: API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month

[John]

OK, just ones off hand that are already filed phab tickets for:

https://phabricator.wikimedia.org/T57007
https://phabricator.wikimedia.org/T66835
https://phabricator.wikimedia.org/T66833
https://phabricator.wikimedia.org/T59995
https://phabricator.wikimedia.org/T57881

And honestly your response to the last ticket is uncalled for. The user
filed a report about missing features from compat, your response was
basically We dont care, fix it yourself.

On Wed, Jun 3, 2015 at 4:20 AM, Amir Ladsgroup  wrote:

> Can you name one?
>
> On Wed, Jun 3, 2015 at 5:02 AM John  wrote:
>
> > This is something that the pywiki devs need to fix in compat. Please dont
> > give me shit about moving to core. I have yet to have it not fatally
> error
> > out in less than 10 minutes of using it. There are still a lot of
> features
> > that core doesnt have, or that are poorly implemented.
> >
> > On Tue, Jun 2, 2015 at 8:27 PM, Pine W  wrote:
> >
> >> Forwarding because of the significance of the change for bots. My
> >> understanding is that this affects all wikis, so please get this
> >> information out to relevant bot operators on all wikis. Translated
> >> messages
> >> may be very much appreciated.
> >>
> >> Pine
> >> -- Forwarded message --
> >> From: "Brad Jorsch (Anomie)" 
> >> Date: Jun 2, 2015 1:43 PM
> >> Subject: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for
> >> action=query will change at the end of this month
> >> To: "Wikimedia developers" , <
> >> mediawiki-api-annou...@lists.wikimedia.org>
> >> Cc:
> >>
> >> As has been announced several times (most recently at
> >> https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081559.html
> ),
> >> the default continuation mode for action=query requests to api.php will
> be
> >> changing to be easier for new coders to use correctly.
> >>
> >> *The date is now set:* we intend to merge the change to ride the
> >> deployment
> >> train at the end of June. That should be 1.26wmf12, to be deployed to
> test
> >> wikis on June 30, non-Wikipedias on July 1, and Wikipedias on July 2.
> >>
> >> If your bot or script is receiving the warning about this upcoming
> change
> >> (as seen here
> >> <https://www.mediawiki.org/w/api.php?action=query&list=allpages>, for
> >> example), it's time to fix your code!
> >>
> >>- The simple solution is to simply include the "rawcontinue"
> parameter
> >>with your request to continue receiving the raw continuation data (
> >>example
> >><
> >>
> >>
> https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1
> >> >).
> >>No other code changes should be necessary.
> >>- Or you could update your code to use the simplified continuation
> >>documented at
> >> https://www.mediawiki.org/wiki/API:Query#Continuing_queries
> >>(example
> >><
> >>
> https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=
> >> >),
> >>which is much easier for clients to implement correctly.
> >>
> >> Either of the above solutions may be tested immediately, you'll know it
> >> works because you stop seeing the warning.
> >>
> >> I've compiled a list of bots that have hit the deprecation warning more
> >> than 1 times over the course of the week May 23-29. If you are
> >> responsible for any of these bots, please fix them. If you know who is,
> >> please make sure they've seen this notification. Thanks.
> >>
> >> AAlertBot
> >> AboHeidiBot
> >> AbshirBot
> >> Acebot
> >> Ameenbot
> >> ArnauBot
> >> Beau.bot
> >> Begemot-Bot
> >> BeneBot*
> >> BeriBot
> >> BOT-Superzerocool
> >> CalakBot
> >> CamelBot
> >> CandalBot
> >> CategorizationBot
> >> CatWatchBot
> >> ClueBot_III
> >> ClueBot_NG
> >> CobainBot
> >> CorenSearchBot
> >> Cyberbot_I
> >> Cyberbot_II
> >> DanmicholoBot
> >> DeltaQuadBot
> >> Dexbot
> >> Dibot
> >> EdinBot
> >> ElphiBot
> >> ErfgoedBot
> >> Faebot
> >> Fatemibot
> >> FawikiPatroller
> >> HAL
> >> HasteurBot
> >> HerculeBot
> >> Hexabot
>

Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS

[John]

Comets, I can answer that. From the dev who switched HTTPS on during prime
usage times, complained about working 60+ hours this week, then left for
the day.

I get the impression that the WMF doesn't give a shit about those users who
choose to opt-out of HTTPS for one reason or another. It's basically your
now screwed, it works for us so figure it out without us.

On Friday, June 12, 2015, Comet styles  wrote:

> Congrats, you just made internet shitty for all 3rd world countries
> and did you people even bother to find out how it will affect users in
> China or Iran where HTTPS is BANNED?.
>
> On 6/13/15, Tito Dutta > wrote:
> > Great job. :)
> > Thanks for informing
> > [PS. to members, you may read the WP:VPT
> > <
> https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#HTTPS_by_default
> >
> > discussion too]
> >
> > On 13 June 2015 at 03:05, Habib M'henni  > wrote:
> >
> >> This is really fantastic.
> >>
> >> Thanks,
> >>
> >> Habib
> >>
> >> Le 12 juin 2015 21:22:26 CET, Juliet Barbara  > a
> >> écrit :
> >> >The Wikimedia Foundation is pleased to announce that we have begun the
> >> >transition of the Wikimedia projects and sites to the secure HTTPS
> >> >protocol. You may have seen our blog post from this morning; it has
> >> >also
> >> >been posted to relevant Village Pumps (Technical).
> >> >
> >> >This post is available online here:
> >> >
> >>
> https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/
> >> >
> >> >Securing access to Wikimedia sites with HTTPS
> >> >
> >> >BY YANA WELINDER ,
> >> >VICTORIA
> >> >BARANETSKY 
> AND
> >> >BRANDON
> >> >BLACK  ON JUNE 12TH
> >> >
> >> >
> >> >To be truly free, access to knowledge must be secure and uncensored. At
> >> >the
> >> >Wikimedia Foundation, we believe that you should be able to use
> >> >Wikipedia
> >> >and the Wikimedia sites without sacrificing privacy or safety.
> >> >
> >> >Today, we’re happy to announce that we are in the process of
> >> >implementing
> >> >HTTPS  to encrypt all Wikimedia
> >> >traffic. We will also use HTTP Strict Transport Security
> >> > (HSTS)
> >> >to
> >> >protect against efforts to ‘break’ HTTPS and intercept traffic. With
> >> >this
> >> >change, the nearly half a billion people who rely on Wikipedia and its
> >> >sister projects every month will be able to share in the world’s
> >> >knowledge
> >> >more securely.
> >> >
> >> >The HTTPS protocol creates an encrypted connection between your
> >> >computer
> >> >and Wikimedia sites to ensure the security and integrity of data you
> >> >transmit. Encryption makes it more difficult for governments and other
> >> >third parties to monitor your traffic. It also makes it harder for
> >> >Internet
> >> >Service Providers (ISPs) to censor access to specific Wikipedia
> >> >articles
> >> >and other information.
> >> >
> >> >HTTPS is not new to Wikimedia sites. Since 2011, we have been working
> >> >on
> >> >establishing the infrastructure and technical requirements, and
> >> >understanding the policy and community implications of HTTPS for all
> >> >Wikimedia traffic, with the ultimate goal of making it available to all
> >> >users. In fact, for the past four years
> >> ><
> >>
> https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/
> >> >,
> >> >Wikimedia users could access our sites with HTTPS manually, through
> >> >HTTPS
> >> >Everywhere , and when directed
> to
> >> >our
> >> >sites from major search engines. Additionally, all logged in users
> >> ><
> >>
> https://blog.wikimedia.org/2013/08/28/https-default-logged-in-users-wikimedia-sites/
> >> >
> >> >have been accessing via HTTPS since 2013.
> >> >
> >> >Over the last few years, increasing concerns about government
> >> >surveillance
> >> >prompted members of the Wikimedia community to push
> >> ><
> https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/>
> >> >for more broad protection through HTTPS. We agreed, and made this
> >> >transition a priority for our policy and engineering teams.
> >> >
> >> >
> >> >We believe encryption makes the web stronger for everyone. In a world
> >> >where
> >> >mass surveillance has become a serious threat to intellectual freedom,
> >> >secure connections are essential for protecting users around the world.
> >> >Without encryption, governments can more easily surveil sensitive
> >> >information, creating a chilling effect, and deterring participation,
> >> >or in
> >> >extreme cases they can isolate or discipline citizens. Accounts may
> >> >also be
> >> >hijacked, pages may be censored, other security flaws could expose
> >> >sensitive user information and communications. Because of these
> >> >

Re: [Wikimedia-l] [Wikimedia Announcements] Securing access to Wikimedia sites with HTTPS

[John]

This reminds me of the VE rollout debacle

On Friday, June 12, 2015, John  wrote:

> Comets, I can answer that. From the dev who switched HTTPS on during prime
> usage times, complained about working 60+ hours this week, then left for
> the day.
>
> I get the impression that the WMF doesn't give a shit about those users
> who choose to opt-out of HTTPS for one reason or another. It's basically
> your now screwed, it works for us so figure it out without us.
>
> On Friday, June 12, 2015, Comet styles  > wrote:
>
>> Congrats, you just made internet shitty for all 3rd world countries
>> and did you people even bother to find out how it will affect users in
>> China or Iran where HTTPS is BANNED?.
>>
>> On 6/13/15, Tito Dutta  wrote:
>> > Great job. :)
>> > Thanks for informing
>> > [PS. to members, you may read the WP:VPT
>> > <
>> https://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#HTTPS_by_default
>> >
>> > discussion too]
>> >
>> > On 13 June 2015 at 03:05, Habib M'henni  wrote:
>> >
>> >> This is really fantastic.
>> >>
>> >> Thanks,
>> >>
>> >> Habib
>> >>
>> >> Le 12 juin 2015 21:22:26 CET, Juliet Barbara 
>> a
>> >> écrit :
>> >> >The Wikimedia Foundation is pleased to announce that we have begun the
>> >> >transition of the Wikimedia projects and sites to the secure HTTPS
>> >> >protocol. You may have seen our blog post from this morning; it has
>> >> >also
>> >> >been posted to relevant Village Pumps (Technical).
>> >> >
>> >> >This post is available online here:
>> >> >
>> >>
>> https://blog.wikimedia.org/2015/06/12/securing-wikimedia-sites-with-https/
>> >> >
>> >> >Securing access to Wikimedia sites with HTTPS
>> >> >
>> >> >BY YANA WELINDER <https://blog.wikimedia.org/author/ywelinder/>,
>> >> >VICTORIA
>> >> >BARANETSKY <https://blog.wikimedia.org/author/victoria-baranetsky/>
>> AND
>> >> >BRANDON
>> >> >BLACK <https://blog.wikimedia.org/author/brandon-black/> ON JUNE 12TH
>> >> >
>> >> >
>> >> >To be truly free, access to knowledge must be secure and uncensored.
>> At
>> >> >the
>> >> >Wikimedia Foundation, we believe that you should be able to use
>> >> >Wikipedia
>> >> >and the Wikimedia sites without sacrificing privacy or safety.
>> >> >
>> >> >Today, we’re happy to announce that we are in the process of
>> >> >implementing
>> >> >HTTPS <https://en.wikipedia.org/wiki/HTTPS> to encrypt all Wikimedia
>> >> >traffic. We will also use HTTP Strict Transport Security
>> >> ><https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security> (HSTS)
>> >> >to
>> >> >protect against efforts to ‘break’ HTTPS and intercept traffic. With
>> >> >this
>> >> >change, the nearly half a billion people who rely on Wikipedia and its
>> >> >sister projects every month will be able to share in the world’s
>> >> >knowledge
>> >> >more securely.
>> >> >
>> >> >The HTTPS protocol creates an encrypted connection between your
>> >> >computer
>> >> >and Wikimedia sites to ensure the security and integrity of data you
>> >> >transmit. Encryption makes it more difficult for governments and other
>> >> >third parties to monitor your traffic. It also makes it harder for
>> >> >Internet
>> >> >Service Providers (ISPs) to censor access to specific Wikipedia
>> >> >articles
>> >> >and other information.
>> >> >
>> >> >HTTPS is not new to Wikimedia sites. Since 2011, we have been working
>> >> >on
>> >> >establishing the infrastructure and technical requirements, and
>> >> >understanding the policy and community implications of HTTPS for all
>> >> >Wikimedia traffic, with the ultimate goal of making it available to
>> all
>> >> >users. In fact, for the past four years
>> >> ><
>> >>
>> https://blog.wikimedia.org/2011/10/03/native-https-support-enabled-for-all-wikimedia-foundation-wikis/
>> >> >,
>> >> >Wikimedia users could access our s

Re: [Wikimedia-l] 24 TB for User:Dispenser on Tool Labs please

[John]

Im mobile right now, do this will be short. He is throwing a tantrum
because WMF won't give him 24TB of storage for a project that has legal
questionablity. So he is using his existing tools as leverage aka hostages
to force the issue. I find that very bad behavior on his part

On Thursday, July 3, 2014, Strainu  wrote:

> 2014-07-03 14:12 GMT+03:00 James Salsman  >:
> > Can someone please explain to me why the Foundation can't give
> > User:Dispenser 24 TB on Tool Labs?
>
>
> Context please?
>
> Strainu
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>  ?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] 24 TB for User:Dispenser on Tool Labs please

[John]

I'm in the process of working with Dispenser to get said proposal written
and the ball rolling. However this process will take some time

On Thu, Jul 3, 2014 at 2:16 PM, Gregory Varnum 
wrote:

> That all seems logical, appropriate, and aligned with our current
> procedures. So..what's the problem?
>
> -greg aka varnent
>
>
> On Thu, Jul 3, 2014 at 1:49 PM, Marc A. Pelletier 
> wrote:
>
> > On 07/03/2014 07:12 AM, James Salsman wrote:
> > > Can someone please explain to me why the Foundation can't give
> > > User:Dispenser 24 TB on Tool Labs?
> >
> > To make matters a bit clearer, Dispenser's current Reflinks tool (and
> > all his others) do not need 24T of storage (nor would toolserver have
> > had that storage to give him, even if it were possible). His demands for
> > the storage are for a new version of the tool he is yet to write that is
> > meant to actually cache the external link's webpages - a request he has
> > yet to actually make to WMF Engineering. He was never told no; he was
> > told (by me, inter alia) that he'd need to make a proposal with
> > explanation and rationale before we would commit several thousand
> > dollars of resources towards an unspecified, future project of his
> > (especially one that is likely to need Legal to look into).
> >
> > That he has not in fact moved his existing tools to Tool Labs is
> > unrelated to this; there is no technical impediment to him running his
> > tools in Labs today if he chooses to.
> >
> > Also, 24T is a significant chunk of the space available to Labs in
> > general; storage is nowhere near as inexpensive in our context as would
> > be with off-the-shelf customer-grade disks.  There's nothing that
> > prevents us from allocating significant resources to a project that
> > needs it (to wit: open street maps tile generator) but we're not going
> > to do that site unseen and without supervision.
> >
> > -- Marc
> >
> >
> > ___
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> > Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] 24 TB for User:Dispenser on Tool Labs please

[John]

Ill be blunt here, Dispenser's existing tools do not need more than a few
hundred megabytes of space for storage. He however does have an idea for a
set of tools (or one super massive depending on your perspective) which is
a resource hog and will need a consult with WMF legal to OK it. Up until
today Dispenser failed to articulate what his idea was or what resources he
needed for his idea. I did some basic math and your looking at about 15
thousand dollars US as a starting point for the project. Dispenser falls
into the standard category of a programmer who doesnt work well with
non-programmers and sucks at writing specs/documentation.

However I spent some time with him and chiseled out a few things, have a
grasp on exactly what Dispenser wants to accomplish and the resources
necessary to do it. (probably upwards of 25-30k dollars) I wrote up a rough
outline and both shorter term and longer term goals of the project. I have
already forwarded it to Coren for review, feedback and comments. I suspect
something more official will be announced after a quick sanity check by the
legal team. At which point I suspect it will be thrown up for community
discussion, and legal will be doing a more in depth review behinds the
scene.

On Thu, Jul 3, 2014 at 8:00 PM, James Salsman  wrote:

> >  I don't think it's a donation if you're getting something (a survey) in
> return.
>
> How could the Foundation possibly not benefit from understanding
> contributors' opinions about general strategic goals for improving
> participation?
>
> I also want development of accuracy review. If there are any reasons
> that the Foundation would not benefit from that, the survey, or a
> reflinks cache which includes enough room to fit a category adjacency
> map in, then please bring them to my attention.
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] 24 TB for User:Dispenser on Tool Labs please

[John]

As I said I'm waiting for feedback first. What I sent to Coren is just a
rough draft. It will be posted to a wiki and more input will be requested.

On Thu, Jul 3, 2014 at 8:56 PM, Samuel Klein  wrote:

> Hello John,
>
> On Thu, Jul 3, 2014 at 8:39 PM, John  wrote:
>
> > However I spent some time with him and chiseled out a few things, have a
> > grasp on exactly what Dispenser wants to accomplish and the resources
> > necessary to do it. (probably upwards of 25-30k dollars) I wrote up a
> rough
> > outline and both shorter term and longer term goals of the project. I
> have
> > already forwarded it to Coren for review, feedback and comments.
>
> Thank you for doing this.
> Would you mind publishing this on one of the wikis as well?
>
> > I suspect something more official will be announced after a quick sanity
> > check by the legal team.
>
> I think the main question is whether these new tools are a significant
> step forward for improving our knowledgebase, and worth this
> investment compared with related work that might achieve similar
> results.  If yes, then together we should make it happen.
>
> The questions of which individuals and groups host, maintain, and
> accept associated legal risk are secondary: many organizations share
> our mission, some (like IA) quite eager to push the boundaries of the
> law in ways that improve global access to information.
>
> Sam
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Blocking of HTTPS connection by China

[John]

Wow, what a complete mis-understanding and misrepresenting of facts my that
blog author

On Friday, June 7, 2013, Benjamin Chen wrote:

> Hi,
>
> Since 31 May, China's Great Firewall has blocked the HTTPS connection to
> all language versions of Wikipedia, by blocking port 443 on two of our IPs.
> I was also told that service to Wikimedia Commons may be affected. Other
> projects, such as en.wikisource are not affected by this block (but they
> may still be subjected to keyword censoring on HTTP).
>
> Compared to the previous short-lived half-day block, this time the block
> has been in place for a week and as usual no one knows if it will last for
> long.
>
> Here is an article that has some explanation, some comments, and (their)
> opinions and suggestions for the Foundation.
>
>
> https://en.greatfire.org/blog/2013/jun/wikipedia-drops-ball-china-not-too-late-make-amends
>
> Regards,
>
> Benjamin Chen / [[User:Bencmq]]
>
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org 
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Some of Wikipedia's most important tools are broken

[John]

Actually the toolserver's practice is not deactivating inactive users.
Users accounts are active for 6 months. One month before the account is set
to expire they start to receive email notifications . There are no less
than 6 reminders sent out before the account is disabled. It takes less
than 3 minutes to log into the toolserver and renew your account Its just a
single command. If a tool author cannot do that, the odds are the tool is
no longer being supported and that issues about the tool are not being
fixed. In most cases disabling the account is the correct thing to do.


On Mon, Sep 9, 2013 at 1:26 PM, Sarah Stierch wrote:

> Yeah..I've noticed that with a lot of tools, whether on the toolserver or
> on labs. The tool I use monthly is:
>
> http://tools.wmflabs.org/glamtools/treeviews/
>
> I ping Magnus all the time and he does his best to fix any issues and now i
> just feel like a broken record each month. It is stifling my reports as a
> Wikipedian in Residence to UNESCO and the Library of Congress :(
>
> It's really tough to function without it, and so many other tools anymore.
>
> -Sarah
>
>
> On Mon, Sep 9, 2013 at 10:24 AM, James Heilman  wrote:
>
> > Some of the key tool's which I use on a daily basis (and their
> workarounds)
> > no longer work.
> >
> > The tool I use the most of any is the autofill for PMID and ISBN's. The
> one
> > in the edit box has not worked for some time and the backup
> > http://diberri.crabdance.com/cgi-bin/templatefiller/index.cgi? stopped
> > working today. The second backup still works a bit thankfully
> > https://toolserver.org/~holek/cite-gen/index.php
> >
> > Another great tool is the dashboard. Its toolserver account has expired.
> > http://wikidashboard.appspot.com/enwiki/wiki/Obesity I find this strange
> > that if a users account has expired all the tools stop working. This
> would
> > be like if I stopped editing Wikipedia for a couple of months than all my
> > contributions would be deleted.
> >
> > So the question is should the WMF be helping keep some of these tools up
> > and running? Many of us long term editors have come to heavily rely on
> > them.
> > --
> > James Heilman
> > MD, CCFP-EM, Wikipedian
> >
> > The Wikipedia Open Textbook of Medicine
> > www.opentextbookofmedicine.com
> > ___
> > Wikimedia-l mailing list
> > Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
>
>
>
>
> --
> --
> *Sarah Stierch*
> *Museumist, open culture advocate, and Wikimedian*
> *www.sarahstierch.com*
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

[Wikimedia-l] Wikimedia labs-tools

[John]

tools.wmflabs.org is supposed to be the replacement for the toolserver
which the wmf is basically forcefully shutting down. I started the
migration several months ago but got fed up with the difficulties and
stopped. In the last month I have moved most of my tools to labs, and I
have discovered that there are some serious issues that need addressed.

The toolserver was a fairly stable environment. I checked my primary host I
connect to and it has been up for 4 months with continuous operations.

tools however is being treated like the red-headed step child. According to
the people in charge of labs they dont care about ensuring stability and
that if stuff breaks Oh well well get to it when we can. They say that
tools is not a production service so we really don't give a <>, if it
breaks it breaks, we will fix it when we can but since its not production
its not a priority.

One good example of this is that a tool cannot connect to
tools.wmflabs.orgdue to a host configuration issue. This is a known
bug, we have a way of
fixing it, but its still not implemented

Given that tools is replacing the toolserver I would expect at worst labs
is just as good, however what I am seeing and hearing is that the wmf is
throwing away one of their best assets, and driving away a lot of
developers due to the management of tools.

I do want to give Coren credit as he is doing what he can to support the
migration.

My question is why has the wmf decided to degrade the environment where
tool developers design and host tools (quite a few of them are long term
stable projects)? and what can we do to remedy this?

John
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] [Labs-l] Wikimedia labs-tools

[John]

Petr I apologize for forgetting to hightlight your good work, however as
you have stated you dont have the access needed to fix the issues as you
are just a volunteer and dont have sufficient rights on the boxes. Between
you and coren I know you two care, however Ryan and others have made it a
point to say if stuff breaks it is not a big deal, its not an emergency,
and that they will get around to fixing it when they do. Because tools isnt
a production server it has the lowest priority.


On Wed, Sep 11, 2013 at 12:01 PM, Fæ  wrote:

> On 11 September 2013 16:45, Magnus Manske 
> wrote:
> > There was a recent mail saying that Labs is not considered "production"
> > stability. Mainly a disagreement about how many 9s in the 99.9% that
> > represents.
>
> 
> A familiar rookie error in adding meaningless commitments in
> operational support contracts. No matter how many (fantasy) 9's
> recurring after the decimal reassures you that the risk lower than an
> asteroid wiping out the human race tomorrow, when you ask what damages
> you get back if the system goes down for an actual day or an actual
> week, the answer tends to be zero.
>
> I remember the 1980's when us software engineers used to talk about
> hot-swapping, triple-redundancy and service level guarantees. Out of
> vogue now I guess in the new world of Agile response teams, zero-hour
> contracted support etc.
>
> Fae
> --
> fae...@gmail.com http://j.mp/faewm
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Someone wants to put their promotional photo on Wikipedia. What's best practices?

[John]

http://en.wikipedia.org/wiki/Wikipedia:Requesting_copyright_permission is
from the otherside of the table but might be useful

On Fri, Oct 11, 2013 at 3:49 PM, Strainu  wrote:

> For this category of people we have OTRS:
>
> https://commons.wikimedia.org/wiki/OTRS#Licensing_images:_when_do_I_contact_OTRS.3F
> :)
>
> If you want to cut the queue, just contact a volunteer to have the
> ticket processed.
>
> Strainu
>
> 2013/10/11 David Gerard :
> > I just got a phone call and followup email today asking about how to
> > upload a photo to be on a Wikipedia article.
> >
> > This has got to be an incredibly common request. What's a standardised
> > way to handle it?
> >
> > Here's the text I wrote back with:
> >
> > ===
> > OK - the key point with contributing a picture to Wikipedia, or rather
> > to Wikimedia Commons, is that you are contributing it to the world -
> > under a free licence.
> >
> > (You can't contribute a picture "for use in Wikipedia" - Wikipedia
> > doesn't accept those. It needs pictures of living people to be under a
> > licence where literally anyone can use it.)
> >
> > So, you need the person or body who owns the copyright in the picture
> > to contribute it under a free licence. This means you lose control
> > over the picture, but it does contribute it to the world. This does
> > not control unpleasant reuses - so be very sure you think this is a
> > good idea.
> >
> >https://commons.wikimedia.org/wiki/Commons:Contributing_your_own_work
> >
> > This works quite well in my experience for promotional photos. It will
> > rapidly become *the* picture people use.
> >
> > Creative Commons by-sa is a good licence, I think - anyone can use it,
> > but anyone can reuse it.
> >
> > Once a picture is uploaded to Commons, it can be used on Wikipedia
> articles.
> > ===
> >
> > - But there's got to be a better text and/or page I could refer them to
> ...
> >
> > Assume the person this is for knows very little about Wikipedia or
> > content freedom.
> >
> >
> > - d.
> >
> > ___
> > Wikimedia-l mailing list
> > Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Someone wants to put their promotional photo on Wikipedia. What's best practices?

[John]

and http://en.wikipedia.org/wiki/Wikipedia:Donating_copyrighted_materials

On Fri, Oct 11, 2013 at 3:52 PM, David Gerard  wrote:

> On 11 October 2013 20:49, Strainu  wrote:
>
> > For this category of people we have OTRS:
> >
> https://commons.wikimedia.org/wiki/OTRS#Licensing_images:_when_do_I_contact_OTRS.3F
> > :)
> > If you want to cut the queue, just contact a volunteer to have the
> > ticket processed.
>
>
> Yes, there's that :-)
>
> I suppose I'm wondering more about how to explain free content, in
> most of its frightening implications, to people who I strongly suspect
> have never even considered the concept of putting a work completely
> beyond their control. Something in less than several kilobytes.
>
>
> - d.
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

I know from experience that a wiki can be re-built from any one of the
dumps that are provided, (pages-meta-current) for example contains
everything needed to reboot a site except its user database
(names/passwords ect). see
http://www.mediawiki.org/wiki/Manual:Moving_a_wiki

On Wed, May 16, 2012 at 10:01 PM, Kim Bruning  wrote:

> >
> > We at Archive Team are attempting to download all the 700,000 Knols.[3]
> For
> > the sake of history. Join us, #archiveteam EFNET.
> >
>
> I did some followup. I'm not sure I can help out with Knol
> anymore, but I discovered that AT is having some trouble
> making good archives of wikimedia sites.
>
> Theoretically, wikipedia et al SHOULD be easy to
> reconstitute, right?  That's why we're using CC licenses
> and all. Else if we drop the ball, WP will be gone.
> This seems like a priority to me!
>
> The main problem seems to be obtaining commons images:
> http://archiveteam.org/index.php?title=Wikiteam
>
> So at the very least, we don't appear to have very good
> documentation. Who could best help Archive Team out? Has
> anyone done/written documentation on completely restoring 1
> or more wikimedia wikis from 'public backup' [1]?
>
> What can we do to help them?
>
> sincerely,
>Kim Bruning
>
> [1] "Real Men don't make backups. They upload it via ftp and
> let the world mirror it." - Linus Torvalds
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

Except for files, getting a content clone up is relativity easy, and can be
done in a fairly quick order (aka less than two weeks for everything). I
know there is talk about getting a rsync setup for images.
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

that two week estimate was given worst case scenario. Given the best case
we are talking as little as a few hours for the smaller wikis to 5 days or
so for a project the size of enwiki. (see
http://lists.wikimedia.org/pipermail/xmldatadumps-l/2012-May/000491.htmlfor
progress on image dumps`)

On Wed, May 16, 2012 at 11:10 PM, Kim Bruning  wrote:

> On Thu, May 17, 2012 at 12:03:02AM -0400, John wrote:
> > Except for files, getting a content clone up is relativity easy, and can
> be
> > done in a fairly quick order (aka less than two weeks for everything). I
> > know there is talk about getting a rsync setup for images.
>
> Ouch, 2 weeks. We need the images to be replicable too though.  head>
>
>
> sincerely,
>Kim Bruning
>
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

take a look at http://www.mediawiki.org/wiki/Manual:Importing_XML_dumps for
exactly how to import an existing dump, I know the process of re-importing
a cluster for the toolserver is normally just a few days when they have the
needed dumps.

On Thu, May 17, 2012 at 12:13 AM, John

> wrote:

> that two week estimate was given worst case scenario. Given the best case
> we are talking as little as a few hours for the smaller wikis to 5 days or
> so for a project the size of enwiki. (see
> http://lists.wikimedia.org/pipermail/xmldatadumps-l/2012-May/000491.htmlfor 
> progress on image dumps`)
>
>
> On Wed, May 16, 2012 at 11:10 PM, Kim Bruning wrote:
>
>> On Thu, May 17, 2012 at 12:03:02AM -0400, John wrote:
>> > Except for files, getting a content clone up is relativity easy, and
>> can be
>> > done in a fairly quick order (aka less than two weeks for everything). I
>> > know there is talk about getting a rsync setup for images.
>>
>> Ouch, 2 weeks. We need the images to be replicable too though. > head>
>>
>>
>> sincerely,
>>Kim Bruning
>>
>>
>> ___
>> Wikimedia-l mailing list
>> Wikimedia-l@lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>>
>
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

Toolserver is a clone of the wmf servers minus files. they run a database
replication of all wikis. these times are dependent on available hardware
and may very, but should provide a decent estimate


On Thu, May 17, 2012 at 12:23 AM, Anthony  wrote:

> On Thu, May 17, 2012 at 12:18 AM, John  wrote:
> > take a look at http://www.mediawiki.org/wiki/Manual:Importing_XML_dumpsfor
> > exactly how to import an existing dump, I know the process of
> re-importing
> > a cluster for the toolserver is normally just a few days when they have
> the
> > needed dumps.
>
> Toolserver doesn't have full history, does it?
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

Ill run a quick benchmark and import the full history of simple.wikipedia
to my laptop wiki on a stick, and give an exact duration


On Thu, May 17, 2012 at 12:26 AM, John  wrote:

> Toolserver is a clone of the wmf servers minus files. they run a database
> replication of all wikis. these times are dependent on available hardware
> and may very, but should provide a decent estimate
>
>
>
> On Thu, May 17, 2012 at 12:23 AM, Anthony  wrote:
>
>> On Thu, May 17, 2012 at 12:18 AM, John  wrote:
>> > take a look at http://www.mediawiki.org/wiki/Manual:Importing_XML_dumpsfor
>> > exactly how to import an existing dump, I know the process of
>> re-importing
>> > a cluster for the toolserver is normally just a few days when they have
>> the
>> > needed dumps.
>>
>> Toolserver doesn't have full history, does it?
>>
>
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

*Simple.wikipedia is nothing like en.wikipedia* I care to dispute that
statement, All WMF wikis are setup basically the same (an odd extension
here or there is different, and different namespace names at times) but for
the purpose of recovery simplewiki_p is a very standard example. this issue
isnt just about enwiki_p but *all* wmf wikis. Doing a data recovery for
enwiki vs simplewiki is just a matter of time, for enwiki a 5 day estimate
would be fairly standard (depending on server setup) and lower times for
smaller databases. typically you can explain it in a rate of X revisions
processed per Y time unit, regardless of the project. and that rate should
be similar for everything given the same hardware setup.

On Thu, May 17, 2012 at 12:37 AM, Anthony  wrote:

> On Thu, May 17, 2012 at 12:30 AM, John  wrote:
> > Ill run a quick benchmark and import the full history of
> simple.wikipedia to
> > my laptop wiki on a stick, and give an exact duration
>
> Simple.wikipedia is nothing like en.wikipedia.  For one thing, there's
> no need to turn on $wgCompressRevisions with simple.wikipedia.
>
> Is $wgCompressRevisions still used?  I haven't followed this in quite a
> while.
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

Anthony the process is linear, you have a php inserting X number of rows
per Y time frame. Yes rebuilding the externallinks, links, and langlinks
tables will take some additional time and wont scale. However I have been
working with the toolserver since 2007 and Ive lost count of the number of
times that the TS has needed to re-import a cluster, (s1-s7) and even
enwiki can be done in a semi-reasonable timeframe. The WMF actually
compresses all text blobs not just old versions. complete download and
decompression of simple only took 20 minutes on my 2 year old consumer
grade laptop with a standard home cable internet connection, same download
on the toolserver (minus decompression) was 88s. Yeah Importing will take a
little longer but shouldnt be that big of a deal. There will also be some
need cleanup tasks. However the main issue, archiving and restoring wmf
wikis isnt an issue, and with moderately recent hardware is no big deal. Im
putting my money where my mouth is, and getting actual valid stats and
figures. Yes it may not be an exactly 1:1 ratio when scaling up, however
given the basics of how importing a dump functions it should remain close
to the same ratio

On Thu, May 17, 2012 at 12:54 AM, Anthony  wrote:

> On Thu, May 17, 2012 at 12:45 AM, John  wrote:
> > Simple.wikipedia is nothing like en.wikipedia I care to dispute that
> > statement, All WMF wikis are setup basically the same (an odd extension
> here
> > or there is different, and different namespace names at times) but for
> the
> > purpose of recovery simplewiki_p is a very standard example. this issue
> isnt
> > just about enwiki_p but *all* wmf wikis. Doing a data recovery for
> enwiki vs
> > simplewiki is just a matter of time, for enwiki a 5 day estimate would be
> > fairly standard (depending on server setup) and lower times for smaller
> > databases. typically you can explain it in a rate of X revisions
> processed
> > per Y time unit, regardless of the project. and that rate should be
> similar
> > for everything given the same hardware setup.
>
> Are you compressing old revisions, or not?  Does the WMF database
> compress old revisions, or not?
>
> In any case, I'm sorry, a 20 gig mysql database does not scale
> linearly to a 20 terabyte mysql database.
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Fire Drill Re: Wikimedia sites not easy to archive (Was Re: Knol is closing tomorrow )

[John]

On Thu, May 17, 2012 at 1:52 AM, Anthony  wrote:

> On Thu, May 17, 2012 at 1:22 AM, John  wrote:
> > Anthony the process is linear, you have a php inserting X number of rows
> per
> > Y time frame.
>
> Amazing.  I need to switch all my databases to MySQL.  It can insert X
> rows per Y time frame, regardless of whether the database is 20
> gigabytes or 20 terabytes in size, regardless of whether the average
> row is 3K or 1.5K, regardless of whether I'm using a thumb drive or a
> RAID array or a cluster of servers, etc.
>

When refering to X over Y time, its an average of a of say 1000 revisions
per 1 minute, any X over Y period must be considered with averages in mind,
or getting a count wouldnt be possible.



> > Yes rebuilding the externallinks, links, and langlinks tables
> > will take some additional time and wont scale.
>
> And this is part of the process too, right?

That does not need to be completed prior to the site going live, it can be
done after making it public

> That part isnt
> > However I have been working
> > with the toolserver since 2007 and Ive lost count of the number of times
> > that the TS has needed to re-import a cluster, (s1-s7) and even enwiki
> can
> > be done in a semi-reasonable timeframe.
>
> Re-importing how?  From the compressed XML full history dumps?


> > The WMF actually compresses all text
> > blobs not just old versions.
>
> Is http://www.mediawiki.org/wiki/Manual:Text_table still accurate?  Is
> WMF using gzip or object?
>
> > complete download and decompression of simple
> > only took 20 minutes on my 2 year old consumer grade laptop with a
> standard
> > home cable internet connection, same download on the toolserver (minus
> > decompression) was 88s. Yeah Importing will take a little longer but
> > shouldnt be that big of a deal.
>
> For the full history English Wikipedia it *is* a big deal.
>
> If you think it isn't, stop playing with simple.wikipedia, and tell us
> how long it takes to get a mirror up and running of en.wikipedia.
>
> Do you plan to run compressOld.php?  Are you going to import
> everything in plain text first, and *then* start compressing?  Seems
> like an awful lot of wasted hard drive space.
>

If you setup your sever/hardware correctly it will compress the text
information during insertion into the database and compressOld.php is
actually designed only for cases where you start with an uncompressed
configuration


> > There will also be some need cleanup tasks.
> > However the main issue, archiving and restoring wmf wikis isnt an issue,
> and
> > with moderately recent hardware is no big deal. Im putting my money
> where my
> > mouth is, and getting actual valid stats and figures. Yes it may not be
> an
> > exactly 1:1 ratio when scaling up, however given the basics of how
> importing
> > a dump functions it should remain close to the same ratio
>
> If you want to put your money where your mouth is, import
> en.wikipedia.  It'll only take 5 days, right?
>

If I actually had a server or the disc space to do it I would, just to
prove your smartass comments as stupid as they actually are. However given
my current resource limitations (fairly crappy internet connection, older
laptops, and lack of HDD) I tried to select something that could give
reliable benchmarks. If your willing to foot the bill for the new hardware
Ill gladly prove my point
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Update on IPv6

[John]

Wow Risker, you obviously don't read any mailing lists/ blogs or sign
posts. I just did a quick search of my email records for wiki tech and ipv6
the first result that I see is from July 2007. Almost 5 years ago, I also
remember a big push last year about this same time for ipv6.

On Friday, June 1, 2012, Risker wrote:

> Indeed, a long time. Discussed on Mediawiki and bugzilla; it's not even
> discussed on Wikitech-L.  Neither of which 99.9% of users, including
> many volunteer developers, have time to follow.  This is not just a
> technical change, it's a cultural one.
>
> I've long stood up for the Engineering Department when it is making changes
> that have only minor effects on the public face of the project; I know that
> sometimes users can be hyperactive about minor points.  But this isn't a
> minor point.  I'd compare it to Vector - something that there was longterm,
> active communication about throughout its development cycle, with lots of
> outreach to volunteer developers and to the community, and opportunities to
> test things out.
>
> I can't stand up for them this time, though. It's not even discussed well
> on Mediawiki, and is mostly in passing on the Roadmap.[1]  And the few
> community-based questions that have come up, specifically on Erik's meta
> userpage, have not been given the courtesy of a reply.
>
> Risker
>
>
>
>
> [1] http://www.mediawiki.org/wiki/Roadmap
>
> On 1 June 2012 19:35, David Gerard >
> wrote:
>
> > On 2 June 2012 00:08, Risker > wrote:
> >
> > Fully enabling IPv6 has been coming a *long* time - over a year, with
> > months of planning and work before even that - as Erik's first message
> > in this thread notes, and it was hardly a secret. Your objections may
> > be entirely too late - it is vanishingly unlikely that two years'
> > effort will suddenly be thrown away. Were you literally unaware until
> > now that this was in the works?
> >
> >
> > - d.
> >
> > ___
> > Wikimedia-l mailing list
> > Wikimedia-l@lists.wikimedia.org 
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> >
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org 
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Update on IPv6

[John]

Multiple sign posts January 17 this year. There was also a May 2011
foundation announcement along with countless other notes

On Friday, June 1, 2012, Risker wrote:

> I've got about 18 months worth of Wikitech-L in my archives, and there are
> two threads that talk about IPv6; one from March, that didn't provide a lot
> of information, and this one. There may be others, but they're not popping
> up on my search.
>
> Forgive me for failing to read this week's signpost from cover to cover
> yet; it refers to the previous coverage from June 2011, and quotes Erik
> Moeller from some unknown and unspecified source.  I don't know where he
> told "the community" that. Do you?
>
> Risker
>
> On 1 June 2012 20:10, John >
> wrote:
>
> > Wow Risker, you obviously don't read any mailing lists/ blogs or sign
> > posts. I just did a quick search of my email records for wiki tech and
> ipv6
> > the first result that I see is from July 2007. Almost 5 years ago, I also
> > remember a big push last year about this same time for ipv6.
> >
> > On Friday, June 1, 2012, Risker wrote:
> >
> > > Indeed, a long time. Discussed on Mediawiki and bugzilla; it's not even
> > > discussed on Wikitech-L.  Neither of which 99.9% of users,
> including
> > > many volunteer developers, have time to follow.  This is not just a
> > > technical change, it's a cultural one.
> > >
> > > I've long stood up for the Engineering Department when it is making
> > changes
> > > that have only minor effects on the public face of the project; I know
> > that
> > > sometimes users can be hyperactive about minor points.  But this isn't
> a
> > > minor point.  I'd compare it to Vector - something that there was
> > longterm,
> > > active communication about throughout its development cycle, with lots
> of
> > > outreach to volunteer developers and to the community, and
> opportunities
> > to
> > > test things out.
> > >
> > > I can't stand up for them this time, though. It's not even discussed
> well
> > > on Mediawiki, and is mostly in passing on the Roadmap.[1]  And the few
> > > community-based questions that have come up, specifically on Erik's
> meta
> > > userpage, have not been given the courtesy of a reply.
> > >
> > > Risker
> > >
> > >
> > >
> > >
> > > [1] http://www.mediawiki.org/wiki/Roadmap
> > >
> > > On 1 June 2012 19:35, David Gerard  > > >
> > > wrote:
> > >
> > > > On 2 June 2012 00:08, Risker  > > > >
> > wrote:
> > > >
> > > > Fully enabling IPv6 has been coming a *long* time - over a year, with
> > > > months of planning and work before even that - as Erik's first
> message
> > > > in this thread notes, and it was hardly a secret. Your objections may
> > > > be entirely too late - it is vanishingly unlikely that two years'
> > > > effort will suddenly be thrown away. Were you literally unaware until
> > > > now that this was in the works?
> > > >
> > > >
> > > > - d.
> > > >
> > > > ___
> > > > Wikimedia-l mailing list
> > > > Wikimedia-l@lists.wikimedia.org  
> > > > Unsubscribe:
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> > > >
> > > ___
> > > Wikimedia-l mailing list
> > > Wikimedia-l@lists.wikimedia.org  
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> > >
> > ___
> > Wikimedia-l mailing list
> > Wikimedia-l@lists.wikimedia.org 
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> >
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org 
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

[Wikimedia-l] CheckUser openness

[John]

This is something that has been bugging me for a while. When a user has
been checkusered they should at least be notified of who preformed it and
why it was preformed. I know this is not viable for every single CU action
as many are for anons. But for those users who have been around for a
period, (say autoconfirmed) they should be notified when they are CU'ed and
any user should be able to request the CU logs pertaining to themselves
(who CU'ed them, when, and why) at will. I have seen CU's refuse to provide
information to the accused.

See the Rich Farmbrough ArbCom case where I suspect obvious fishing, where
the CU'ed user was requesting information and the CU claimed it would be a
violation of the privacy policy to release the time/reason/performer of the
checkuser.

This screams of obfuscation and the hiding of information. I know the
ombudsman committee exists as a check and balance, however before something
can be passed to them evidence of inappropriate action is needed. Ergo
Catch-22

I know checkusers  keep a private wiki
https://checkuser.wikimedia.org/wiki/Main_Page and I know according to our
privacy policy we are supposed to purge our information regularly (on wiki
CU logs exist for 90 days) however who oversees the regular removal of
private information on the wiki?

My proposal would be for all users who are at least auto confirmed to be
notified and be able to request all CU logs regarding themselves at any
point, and any mentions of themselves on the CU wiki should be retrievable.

John
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] CheckUser openness

[John]

I am not a checkuser, I do not have access to checkuser-l, the CU wiki, or
any other private information. This goes far beyond the one case, I was
just using it as a recent example

On Wed, Jun 13, 2012 at 7:34 PM, Risker  wrote:

> On 13 June 2012 19:18, John  wrote:
>
> > This is something that has been bugging me for a while. When a user has
> > been checkusered they should at least be notified of who preformed it and
> > why it was preformed. I know this is not viable for every single CU
> action
> > as many are for anons. But for those users who have been around for a
> > period, (say autoconfirmed) they should be notified when they are CU'ed
> and
> > any user should be able to request the CU logs pertaining to themselves
> > (who CU'ed them, when, and why) at will. I have seen CU's refuse to
> provide
> > information to the accused.
> >
> > See the Rich Farmbrough ArbCom case where I suspect obvious fishing,
> where
> > the CU'ed user was requesting information and the CU claimed it would be
> a
> > violation of the privacy policy to release the time/reason/performer of
> the
> > checkuser.
> >
> > This screams of obfuscation and the hiding of information. I know the
> > ombudsman committee exists as a check and balance, however before
> something
> > can be passed to them evidence of inappropriate action is needed. Ergo
> > Catch-22
> >
> > I know checkusers  keep a private wiki
> > https://checkuser.wikimedia.org/wiki/Main_Page and I know according to
> our
> > privacy policy we are supposed to purge our information regularly (on
> wiki
> > CU logs exist for 90 days) however who oversees the regular removal of
> > private information on the wiki?
> >
> > My proposal would be for all users who are at least auto confirmed to be
> > notified and be able to request all CU logs regarding themselves at any
> > point, and any mentions of themselves on the CU wiki should be
> retrievable.
> >
> >
> >
> Perhaps some full disclosure should be made here John.  You are a checkuser
> yourself, have access to the checkuser-L mailing list and the checkuser
> wiki, helped to set up the Audit Subcommittee on the English Wikipedia
> (which carries out reviews of checkuser/oversighter actions on request);
> you are also a member of the English Wikipedia functionaries mailing list
> because you are a former arbitrator, a checkuser and an oversighter on
> enwp. (so have access there to express your concerns or suggest changes in
> standards),   It seems you are complaining about a specific case, and
> instead of talking things out about this specific case, you've decided to
> propose an entirely different checkusering standard.  I'll point out  in
> passing that half of the spambots blocked in recent weeks by checkusers
> were autoconfirmed on one or more projects, and even obvious vandals can
> hit the autoconfirmed threshold easily on most projects.
>
> Full disclosure on my part: I am also an Enwp checkuser and a member of the
> Arbitration Committee.
>
> Risker
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] CheckUser openness

[John]

PS I am not a former arb, do not have access to functionaries mailing list,
I do not have access nor have ever had access to any of the above including
Oversight. I was just throwing out autoconfirmed as a line in the sand, we
can adjust the line so that normal users can be notified while excluding
spambots. One point could be say 50 edits and at least a month old account?
The nature and required secrecy for such a open project is scary in this
regards.

John

On Wed, Jun 13, 2012 at 7:37 PM, John  wrote:

> I am not a checkuser, I do not have access to checkuser-l, the CU wiki, or
> any other private information. This goes far beyond the one case, I was
> just using it as a recent example
>
>
> On Wed, Jun 13, 2012 at 7:34 PM, Risker  wrote:
>
>> On 13 June 2012 19:18, John  wrote:
>>
>> > This is something that has been bugging me for a while. When a user has
>> > been checkusered they should at least be notified of who preformed it
>> and
>> > why it was preformed. I know this is not viable for every single CU
>> action
>> > as many are for anons. But for those users who have been around for a
>> > period, (say autoconfirmed) they should be notified when they are CU'ed
>> and
>> > any user should be able to request the CU logs pertaining to themselves
>> > (who CU'ed them, when, and why) at will. I have seen CU's refuse to
>> provide
>> > information to the accused.
>> >
>> > See the Rich Farmbrough ArbCom case where I suspect obvious fishing,
>> where
>> > the CU'ed user was requesting information and the CU claimed it would
>> be a
>> > violation of the privacy policy to release the time/reason/performer of
>> the
>> > checkuser.
>> >
>> > This screams of obfuscation and the hiding of information. I know the
>> > ombudsman committee exists as a check and balance, however before
>> something
>> > can be passed to them evidence of inappropriate action is needed. Ergo
>> > Catch-22
>> >
>> > I know checkusers  keep a private wiki
>> > https://checkuser.wikimedia.org/wiki/Main_Page and I know according to
>> our
>> > privacy policy we are supposed to purge our information regularly (on
>> wiki
>> > CU logs exist for 90 days) however who oversees the regular removal of
>> > private information on the wiki?
>> >
>> > My proposal would be for all users who are at least auto confirmed to be
>> > notified and be able to request all CU logs regarding themselves at any
>> > point, and any mentions of themselves on the CU wiki should be
>> retrievable.
>> >
>> >
>> >
>> Perhaps some full disclosure should be made here John.  You are a
>> checkuser
>> yourself, have access to the checkuser-L mailing list and the checkuser
>> wiki, helped to set up the Audit Subcommittee on the English Wikipedia
>> (which carries out reviews of checkuser/oversighter actions on request);
>> you are also a member of the English Wikipedia functionaries mailing list
>> because you are a former arbitrator, a checkuser and an oversighter on
>> enwp. (so have access there to express your concerns or suggest changes in
>> standards),   It seems you are complaining about a specific case, and
>> instead of talking things out about this specific case, you've decided to
>> propose an entirely different checkusering standard.  I'll point out  in
>> passing that half of the spambots blocked in recent weeks by checkusers
>> were autoconfirmed on one or more projects, and even obvious vandals can
>> hit the autoconfirmed threshold easily on most projects.
>>
>> Full disclosure on my part: I am also an Enwp checkuser and a member of
>> the
>> Arbitration Committee.
>>
>> Risker
>> ___
>> Wikimedia-l mailing list
>> Wikimedia-l@lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>>
>
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] CheckUser openness

[John]

Yet another attempt from a checkuser to make monitoring their actions and
ensuring our privacy more difficult.

On Wed, Jun 13, 2012 at 9:10 PM, Risker  wrote:

> Each project has its own standards and thresholds for when checkusers may
> be done, provided that they are within the limits of the privacy policy.
> These standards vary widely.  So, the correct place to discuss this is on
> each project.
>
> Risker
>
> On 13 June 2012 21:02, Thomas Dalton  wrote:
>
> > Why shouldn't spambots and vandals be notified? Just have the software
> > automatically email anyone that is CUed. Then the threshold is simply
> > whether you have an email address attached to your account or not.
> >
> > This seems like a good idea. People have a right to know what is being
> done
> > with their data.
> > On Jun 14, 2012 12:35 AM, "Risker"  wrote:
> >
> > > On 13 June 2012 19:18, John  wrote:
> > >
> > > > This is something that has been bugging me for a while. When a user
> has
> > > > been checkusered they should at least be notified of who preformed it
> > and
> > > > why it was preformed. I know this is not viable for every single CU
> > > action
> > > > as many are for anons. But for those users who have been around for a
> > > > period, (say autoconfirmed) they should be notified when they are
> CU'ed
> > > and
> > > > any user should be able to request the CU logs pertaining to
> themselves
> > > > (who CU'ed them, when, and why) at will. I have seen CU's refuse to
> > > provide
> > > > information to the accused.
> > > >
> > > > See the Rich Farmbrough ArbCom case where I suspect obvious fishing,
> > > where
> > > > the CU'ed user was requesting information and the CU claimed it would
> > be
> > > a
> > > > violation of the privacy policy to release the time/reason/performer
> of
> > > the
> > > > checkuser.
> > > >
> > > > This screams of obfuscation and the hiding of information. I know the
> > > > ombudsman committee exists as a check and balance, however before
> > > something
> > > > can be passed to them evidence of inappropriate action is needed.
> Ergo
> > > > Catch-22
> > > >
> > > > I know checkusers  keep a private wiki
> > > > https://checkuser.wikimedia.org/wiki/Main_Page and I know according
> to
> > > our
> > > > privacy policy we are supposed to purge our information regularly (on
> > > wiki
> > > > CU logs exist for 90 days) however who oversees the regular removal
> of
> > > > private information on the wiki?
> > > >
> > > > My proposal would be for all users who are at least auto confirmed to
> > be
> > > > notified and be able to request all CU logs regarding themselves at
> any
> > > > point, and any mentions of themselves on the CU wiki should be
> > > retrievable.
> > > >
> > > >
> > > >
> > > Perhaps some full disclosure should be made here John.  You are a
> > checkuser
> > > yourself, have access to the checkuser-L mailing list and the checkuser
> > > wiki, helped to set up the Audit Subcommittee on the English Wikipedia
> > > (which carries out reviews of checkuser/oversighter actions on
> request);
> > > you are also a member of the English Wikipedia functionaries mailing
> list
> > > because you are a former arbitrator, a checkuser and an oversighter on
> > > enwp. (so have access there to express your concerns or suggest changes
> > in
> > > standards),   It seems you are complaining about a specific case, and
> > > instead of talking things out about this specific case, you've decided
> to
> > > propose an entirely different checkusering standard.  I'll point out
>  in
> > > passing that half of the spambots blocked in recent weeks by checkusers
> > > were autoconfirmed on one or more projects, and even obvious vandals
> can
> > > hit the autoconfirmed threshold easily on most projects.
> > >
> > > Full disclosure on my part: I am also an Enwp checkuser and a member of
> > the
> > > Arbitration Committee.
> > >
> > > Risker
> > > ___
> > > Wikimedia-l mailing list
> > > Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> > >
> > ___
> > Wikimedia-l mailing list
> > Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> >
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] CheckUser openness

[John]

Risker comment was basically "lets not set a global accountability and
ability to get CU related logs of our self on a global level, instead take
it to each project and fight it out there" to me that reeks of obfuscation.
Realistically this should be a global policy, just like our privacy policy
is. Why shouldnt users know when they have been checkusered and why?

On Wed, Jun 13, 2012 at 9:24 PM, Philippe Beaudette, Wikimedia Foundation <
pbeaude...@wikimedia.org> wrote:

> I dunno, John, you almost had me convinced until that email. I saw in that
> mail a reasonable comment from Risker based on long time precedent.
>
> As you may know, there are a number of checks and balances in place.
> First, the CUs watch each other. With a broad group, you can be assured
> they don't all always agree and there is healthy debate and dialogue.
> Second, enwp has an audit subcommittee that routinely audits the logs with
> a fine toothed comb.  They are NOT all previous checkusers, to avoid the
> sort of groupthink that appears to concern you. Then, the WMF has an
> ombudsman commission, which also may audit with commission from the Board.
> Those people take their role very seriously. And last, anyone with genuine
> privacy concerns can contact the WMF:  me, Maggie, anyone in the legal or
> community advocacy department.
>
> Is it an iron clad assurance of no misbehavior?  Probably not, and we will
> continue to get better at it: but I will say that in 3 years of being
> pretty closely involved with that team, I'm impressed with how much they
> err on the side of protection of privacy. I have a window into their world,
> and they have my respect.
>
> Best, PB
> ---
> Philippe Beaudette
> Director, Community Advocacy
> Wikimedia Foundation, Inc
>
>
> Sent from my Verizon Wireless BlackBerry
>
> -Original Message-
> From: John 
> Sender: wikimedia-l-boun...@lists.wikimedia.org
> Date: Wed, 13 Jun 2012 21:17:09
> To: Wikimedia Mailing List
> Reply-To: Wikimedia Mailing List 
> Subject: Re: [Wikimedia-l] CheckUser openness
>
> Yet another attempt from a checkuser to make monitoring their actions and
> ensuring our privacy more difficult.
>
> On Wed, Jun 13, 2012 at 9:10 PM, Risker  wrote:
>
> > Each project has its own standards and thresholds for when checkusers may
> > be done, provided that they are within the limits of the privacy policy.
> > These standards vary widely.  So, the correct place to discuss this is on
> > each project.
> >
> > Risker
> >
> > On 13 June 2012 21:02, Thomas Dalton  wrote:
> >
> > > Why shouldn't spambots and vandals be notified? Just have the software
> > > automatically email anyone that is CUed. Then the threshold is simply
> > > whether you have an email address attached to your account or not.
> > >
> > > This seems like a good idea. People have a right to know what is being
> > done
> > > with their data.
> > > On Jun 14, 2012 12:35 AM, "Risker"  wrote:
> > >
> > > > On 13 June 2012 19:18, John  wrote:
> > > >
> > > > > This is something that has been bugging me for a while. When a user
> > has
> > > > > been checkusered they should at least be notified of who preformed
> it
> > > and
> > > > > why it was preformed. I know this is not viable for every single CU
> > > > action
> > > > > as many are for anons. But for those users who have been around
> for a
> > > > > period, (say autoconfirmed) they should be notified when they are
> > CU'ed
> > > > and
> > > > > any user should be able to request the CU logs pertaining to
> > themselves
> > > > > (who CU'ed them, when, and why) at will. I have seen CU's refuse to
> > > > provide
> > > > > information to the accused.
> > > > >
> > > > > See the Rich Farmbrough ArbCom case where I suspect obvious
> fishing,
> > > > where
> > > > > the CU'ed user was requesting information and the CU claimed it
> would
> > > be
> > > > a
> > > > > violation of the privacy policy to release the
> time/reason/performer
> > of
> > > > the
> > > > > checkuser.
> > > > >
> > > > > This screams of obfuscation and the hiding of information. I know
> the
> > > > > ombudsman committee exists as a check and balance, however before
> > > > something
> > > > > can be passe

Re: [Wikimedia-l] CheckUser openness

[John]

I am not asking for checkuser results, rather the basic logs about
when/why/who may have checkusered the account. I am not asking CUs to
release IP/user-agent/other info, but to let users know that they are being
CUed, by whom and why. and to be able to request that historical
information from the CU logs

On Wed, Jun 13, 2012 at 9:54 PM, James Alexander wrote:

> To be honest the biggest problem is that releasing this information can
> hurt quite a lot. It can give away the techniques the checkuser (or
> checkusers, more then one working together is very common to make sure
> they're right) used to draw the connections. This is especially true for
> technical information where it can easily give away 'tell-tale' signs used
> as part of the determination.
>
> Almost every time I've ever seen the information demanded it was quite
> clear (usually even with out any type of technical information) that the
> user was guilty as charged and now they just wanted one of those two
> things: A target (the CU) or the information (to find out where they went
> wrong).
>
> Yes, if a horrible checkuser was checking you you wouldn't know instantly
> but that's why we have so many checks and balances. Giving all of this
> information to everyone, especially automatically, would make it almost
> infinitely harder for checkusers to do their job.
>
> James
>
> On Wed, Jun 13, 2012 at 6:30 PM, John  wrote:
>
> > Risker comment was basically "lets not set a global accountability and
> > ability to get CU related logs of our self on a global level, instead
> take
> > it to each project and fight it out there" to me that reeks of
> obfuscation.
> > Realistically this should be a global policy, just like our privacy
> policy
> > is. Why shouldnt users know when they have been checkusered and why?
> >
> > On Wed, Jun 13, 2012 at 9:24 PM, Philippe Beaudette, Wikimedia
> Foundation <
> > pbeaude...@wikimedia.org> wrote:
> >
> > > I dunno, John, you almost had me convinced until that email. I saw in
> > that
> > > mail a reasonable comment from Risker based on long time precedent.
> > >
> > > As you may know, there are a number of checks and balances in place.
> > > First, the CUs watch each other. With a broad group, you can be assured
> > > they don't all always agree and there is healthy debate and dialogue.
> > > Second, enwp has an audit subcommittee that routinely audits the logs
> > with
> > > a fine toothed comb.  They are NOT all previous checkusers, to avoid
> the
> > > sort of groupthink that appears to concern you. Then, the WMF has an
> > > ombudsman commission, which also may audit with commission from the
> > Board.
> > > Those people take their role very seriously. And last, anyone with
> > genuine
> > > privacy concerns can contact the WMF:  me, Maggie, anyone in the legal
> or
> > > community advocacy department.
> > >
> > > Is it an iron clad assurance of no misbehavior?  Probably not, and we
> > will
> > > continue to get better at it: but I will say that in 3 years of being
> > > pretty closely involved with that team, I'm impressed with how much
> they
> > > err on the side of protection of privacy. I have a window into their
> > world,
> > > and they have my respect.
> > >
> > > Best, PB
> > > ---
> > > Philippe Beaudette
> > > Director, Community Advocacy
> > > Wikimedia Foundation, Inc
> > >
> > >
> > > Sent from my Verizon Wireless BlackBerry
> > >
> > > -Original Message-
> > > From: John 
> > > Sender: wikimedia-l-boun...@lists.wikimedia.org
> > > Date: Wed, 13 Jun 2012 21:17:09
> > > To: Wikimedia Mailing List
> > > Reply-To: Wikimedia Mailing List 
> > > Subject: Re: [Wikimedia-l] CheckUser openness
> > >
> > > Yet another attempt from a checkuser to make monitoring their actions
> and
> > > ensuring our privacy more difficult.
> > >
> > > On Wed, Jun 13, 2012 at 9:10 PM, Risker  wrote:
> > >
> > > > Each project has its own standards and thresholds for when checkusers
> > may
> > > > be done, provided that they are within the limits of the privacy
> > policy.
> > > > These standards vary widely.  So, the correct place to discuss this
> is
> > on
> > > > each project.
> > > >
> > > > Risker
> > > >
> > > > On 13 June 2012 21:02, Thomas Dalton 
> wrote:
&g

Re: [Wikimedia-l] CheckUser openness

[John]

I am not asking for full disclosure, what I am asking is that established
user have the right to be notified when and why they are being checkusered.
The evidence checkusers get do not need to be disclosed, Its as simple as:

 X performed a checkuser on you because Y at Z UTC

that provides clarity and openness while keeping the information checkusers
use confidential. A note like that would provide vandals with very little
information. And the second step of defining a threshold would eliminate
most of the vandal checks.

To me this screams of lets keep oversight of checkuser to a minimum. Right
now there is the ombudsman committee globally (to ask for review from them
we need evidence, realistically only other checkusers can provide that)
and on enwp there is the Audit Subcommittee, which 75% of are either arbcom
members (be defacto are granted CU ), former arbcom, or former CU. To me
that really reeks of lack of independent oversight. Notifying an
established user that they are subject to a CU doesnt harm the CU's ability
to do their job unless they themselves have something to hide. Its not like
I am asking for CU's to release IP addresses/user-agents or anything else
that could assist me in avoiding scrutiny.

On Thu, Jun 14, 2012 at 3:48 AM, Stephanie Daugherty
wrote:

> On Thu, Jun 14, 2012 at 3:36 AM, David Richfield
> wrote:
>
> > So User:mfgaowener should get an automated mail saying "because you
> > did a pagemove with edit summary "Haers!" you were checkusered.
> > Please be more subtle in your vandalism next time."
> >
> > I trust the current checks and balances, and I don't think the system
> > is getting significant levels of abuse.
> >
> > +1 on this. The methods that checkusers have are heavily constrained as
> it
> is by privacy concerns, and they are very fragile. They only work
> effectively within the tight privacy restrictions with a certain amount of
> security through obscurity. For one, a checkuser needs to be able to
> monitor a situation sometimes to be sure that they are casting a wide
> enough net for a block to be effective. For another, the standard of
> reasonable suspicion placed on the checkuser tool is high enough that with
> enough practice, vandals would learn to be careful to never justify a
> checkuser request within the privacy guidelines.
>
> We're between a rock and a hard place, because to give the transparency
> being asked for, we'd enter an arms race where we'd quickly have to relax
> the checkuser standards to the point where it becomes "anything goes so
> long as you don't disclose it".
>
> -Stephanie
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] CheckUser openness

[John]

Wow I am utterly in shock, while trying to dig up the diff that En Pine
requested I get this comment from a checkuser

*Checkusers are accountable to your representatives on the AUSC, to the
Foundation's ombudsmen, and to one another—not to you.*
-User:AGK

when a user was looking into possible mis-use of checkuser tools. This
basically screams fuck you to the community, when the actions of a CU are
questioned. Keep in mind that this is coming from a
1) a active CheckUser
2) enwiki ArbCom member
3) AUSC member.

A independent user had then notified the ombudsmen committee only to get
zero response from them. This is supposed to make me trust them with my
private data why?

On Thu, Jun 14, 2012 at 5:46 PM, Nathan  wrote:

> On Thu, Jun 14, 2012 at 5:35 PM, En Pine  wrote:
>
> >
> > I'm inclined to agree with Risker here. Telling someone that a CU has
> been
> > performed on their account, at the time that a CU is performed, might
> alert
> > a disruptive user that some part of their recent activity has triggered
> the
> > attention of SPI. This information could be used to the advantage of the
> > disruptive user.
> >
> > If someone believes that CU may have been used improperly, various groups
> > can investigate the use of CU.
> >
> > John, you said in your original email, "See the Rich Farmbrough ArbCom
> > case where I suspect obvious fishing, where the CU'ed user was requesting
> > information and the CU claimed it would be a violation of the privacy
> > policy to release the time/reason/performer of the checkuser." Can you
> > provide a link to the relevant diffs? I would be interested in reading
> the
> > diffs to get a fuller understanding of what was said, particularly
> > regarding the Wikimedia-wide Privacy Policy.
> >
> > Thanks,
> >
> > Pine
> >
>
> Here are some problems with that rationale:
>
> 1) If a sock confirmation results from a CU check, the person is blocked,
> which is a pretty big tip off all its own. If a case is filed at SPI, then
> tons of evidence is submitted, then a CU check is performed in public, then
> a block is or is not imposed. That whole process is a pretty big tip off
> too, but we haven't shut it down for providing a road map to abusers.
>
> 2) You can't dispute the use of CU on your information if you don't know
> that it was used. It's kind of like secret wiretapping with a FISA warrant;
> if you never know you've been wiretapped, how are you supposed to challenge
> it or know whether it was used improperly? As for "various groups can
> investigate", to some extent that's true. Most of them are checkusers,
> however, and they still tend not to disclose all relevant information. I'm
> not saying that any CU is doing anything improper or that it's likely, but
> such allegations have been made in the past, and it seems like a pretty cut
> and dried case of people having a right to know how their own information
> is being used. If Wikimedia were based in Europe, it would most likely be
> required by law.
>
> Nathan
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Throttling (was: Re: Please can someone put 50p in the meter)

[John]

If you are planning an event it is fairly easy to get your IP address
temporarily whitelisted from the account creation throttle. You just
need to know your IP address that will be used.

On Sun, Oct 14, 2012 at 8:55 AM, Craig Franklin  wrote:
> Can I second this one, we've run into it occasionally in WMAU outreach
> sessions as well, and it's always fun explaining why it's said "no" to
> someone without a foundation in computers or internet culture.  A brief
> explanation of why it's happened and what to do in order to not lose your
> edit, made in simple language, would be lovely.
>
> We do find that the best way to get around the account creation throttle is
> to get people to create their accounts beforehand.  In a given class,
> there's usually one or two who don't get the message or are unable to do
> it, but they can usually be dealt with by the instructor without triggering
> anything.
>
> Cheers,
> Craig
>
> Date: Sat, 13 Oct 2012 18:33:54 +0100
>> From: Andrew Gray 
>> To: Wikimedia Mailing List ,
>> Philippe Beaudette 
>> Subject: Re: [Wikimedia-l] Please can someone put 50p in the meter
>> Message-ID:
>> > fljhrgck+9ftttqmhsx1cgd+ob50vxtom0+qcjrih...@mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> I evade account creation by always making them log in first...
>>
>> Periodically, with a roomful of users, we'll get told that an edit has been
>> "throttled"; no further details, I think. It seems to happen with one or at
>> most two editors at a time out of a dozen, but it can happen to different
>> people later on. This happened several times in a couple of weeks in the
>> summer (I only started workshops in June), and then occasionally since -
>> including yesterday. I originally assumed it was related to external-link
>> additions by new users, but I've seen it for no-link sandbox edits as well.
>>
>> My guess is that this entails something to do with checking for multiple
>> edits from the same IP at once, but I don't know if this is actually the
>> reason, or if it can be disabled/whitelisted.
>>
>> (It's the one I give, though! Corrections gratefully appreciated)
>>
>> - Andrew.
>> On 13 Oct 2012 17:25, "Philippe Beaudette"  wrote:
>>
>> > On Sat, Oct 13, 2012 at 9:07 AM, WereSpielChequers
>> >  wrote:
>> > > As it is this combined with the "throttling feature" made for
>> > > quite a bit of disruption to a session where we had ten people having
>> an
>> > > introduction to editing.
>> >
>> > By "throttling feature", do you mean the account creation
>> > restrictions?  If so, you know there are ways around that, right?
>> > Email me offlist, so as not to clutter the list, and I'll give you a
>> > pointer.
>> >
>> > If you mean something different, disregard :)
>> >
>> > pb
>> > ___
>> > Philippe Beaudette
>> > Director, Community Advocacy
>> > Wikimedia Foundation, Inc.
>> >
>> > 415-839-6885, x 6643
>> >
>> > phili...@wikimedia.org
>> >
>> > ___
>> > Wikimedia-l mailing list
>> > Wikimedia-l@lists.wikimedia.org
>> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
>> >
>>
>>
>>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Throttling (was: Re: Please can someone put 50p in the meter)

[John]

IPs shouldnt get hit with an edit throttle, (it is really really high)

On Sun, Oct 14, 2012 at 10:04 AM, Andrew Gray  wrote:
> On 14 October 2012 13:59, John  wrote:
>> If you are planning an event it is fairly easy to get your IP address
>> temporarily whitelisted from the account creation throttle. You just
>> need to know your IP address that will be used.
>
> Is it possible to whitelist IPs from the "edit throttle", though? That
> one's the killer, and it's not really possible to workaround.
>
> --
> - Andrew Gray
>   andrew.g...@dunelm.org.uk
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Throttling (was: Re: Please can someone put 50p in the meter)

[John]

Next time you get said message can you take a screenshot and let us
know, (it is by default somewhere over 60/edits per minute)

On Sun, Oct 14, 2012 at 11:25 AM, Andrew Gray  wrote:
> On 14 October 2012 15:50, John  wrote:
>> IPs shouldnt get hit with an edit throttle, (it is really really high)
>
> It doesn't seem it! Over the past few months, I've had it triggered
> four times in an hour in two workshops, and one or two times in
> perhaps four more. They're not all at the same location or using the
> same machines, though they were all using institutional networks.
> These are all new logged-in contributors editing from - presumably -
> the same IP; I've not had it happen to me in the same sessions, but
> that might just be chance.
>
> These aren't very busy networks, however, and I can't imagine there's
> a vast flood of active editing coming from them at the same time as
> the workshop...
>
> Is it possible to see where this is configured?
>
> --
> - Andrew Gray
>   andrew.g...@dunelm.org.uk
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

[Wikimedia-l] Wikimedia Sverige vs. the Visual Copyright Society in Sweden (BUS)

[John Andersson]

Today we received some bad news in Sweden. The Swedish Patent and Market
Court ruled against Wikimedia Sverige in a lawsuit filed by Visual
Copyright Society in Sweden <http://bus.se/en> (BUS). The case concerns
images of public art online, more specifically in the case of our website
Offentligkonst.se <http://offentligkonst.se/>, a service created by
Wikimedia Sverige using images from Wikimedia Commons.

The ruling means that Freedom of Panorama is eroded and the public space is
diminished. It is a detrimental loss for our projects. Next we will talk to
our lawyers and WMF legal team to see what our remaining legal options are.
Our lawyers however believe that success is not very likely if we would
decide to move forward.

Intensive efforts to advocate for our elected officials to change the
outdated and problematic clauses in Swedish copyright law will be initiated
during the year.

We have also started a crowdfunding campaign to cover some of the cost of
the legal expenses and fines of about 750,000 SEK stated in the verdict
(around 89,000 USD) and for future national and international lobbying
efforts. Please consider making a donation at http://wikimedia.se/en/donera,
<http://wikimedia.se/en/donera>ev <http://wikimedia.se/en/donera>en
<http://wikimedia.se/en/donera> i <http://wikimedia.se/en/donera>f
<http://wikimedia.se/en/donera>it <http://wikimedia.se/en/donera> i
<http://wikimedia.se/en/donera>s <http://wikimedia.se/en/donera>a
<http://wikimedia.se/en/donera>sy <http://wikimedia.se/en/donera>mb
<http://wikimedia.se/en/donera>ol <http://wikimedia.se/en/donera>ic
<http://wikimedia.se/en/donera> s <http://wikimedia.se/en/donera>um
<http://wikimedia.se/en/donera>. Simply  add “BUS” in the comment, and all
the money will be used for these costs.

Some useful links (in Swedish):

   -

   The legal argumentation from the court:
   
<http://www.hogstadomstolen.se/Domstolar/hogstadomstolen/Avgoranden/2016/2016-04-04%20%C3%96%20849-15%20Beslut.pdf>
   http://www.bildupphovsratt.se/sites/default/files/upload/
   stockholms_tr_pmt_8448-14_dom_2017-07-06.pdf
   
<http://www.bildupphovsratt.se/sites/default/files/upload/stockholms_tr_pmt_8448-14_dom_2017-07-06.pdf>
   
<http://www.hogstadomstolen.se/Domstolar/hogstadomstolen/Avgoranden/2016/2016-04-04%20%C3%96%20849-15%20Beslut.pdf>
   -

   Our press release:
   
<http://www.mynewsdesk.com/se/pressreleases/hoegsta-domstolen-vaeljer-att-krympa-det-offentliga-rummet-istaellet-foer-att-gaa-paa-wikimedia-sveriges-linje-1360834>
   https://www.mynewsdesk.com/se/wikimedia-sverige/
   pressreleases/domslut-krymper-det-offentliga-rummet-i-sverige-2054679
   
<https://www.mynewsdesk.com/se/wikimedia-sverige/pressreleases/domslut-krymper-det-offentliga-rummet-i-sverige-2054679>
   
<http://www.mynewsdesk.com/se/pressreleases/hoegsta-domstolen-vaeljer-att-krympa-det-offentliga-rummet-istaellet-foer-att-gaa-paa-wikimedia-sveriges-linje-1360834>
   -

   A timeline of what has happened: https://se.wikimedia.org/wiki/
   Offentligkonst.se/Stämning


Best,

John

- - - -

John Andersson

Executive Director
Wikimedia Sverige

Phone: +46(0)73-3965189 <073-396%2051%2089>

Email: john.anders...@wikimedia.se

Skype: johnandersson86
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Re: Recognition of Wikimedia Community User Group Rwanda

[John ADEKUNLE]

This is massive...

Congratulations

John. A

On Thu, Feb 10, 2022, 9:44 AM Camelia Boban  wrote:

> Hi everyone!
>
> I'm very happy to announce that the Affiliations Committee has recognized
> [1] *Wikimedia Community User Group* *Rwanda *[2] as a Wikimedia User
> Group. The group aims to improve articles on Wikimedia Foundation project
> websites and promote free and open access to knowledge locally in
> Kinyarwanda & English. They also invest in projects that sensitize and
> train different communities in Rwanda about Wikipedia with much emphasis on
> Kinyarwanda Wikipedia*.*
>
> Please join me in congratulating the members of this new user group!
>
> [1]
> https://meta.wikimedia.org/wiki/Affiliations_Committee/Resolutions/Recognition_of_Wikimedia_Community_User_Group_Rwanda
>
> [2] https://meta.wikimedia.org/wiki/Wikimedia_Community_User_Group_Rwanda
>
>
> Regards,
>
>
>
> *Camelia Boban*
> *Chair*
>
> *Affiliation <https://meta.wikimedia.org/wiki/Affiliations_Committee>*
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MFA2FLU676R43VFKRHHEW6X63M6LOBXI/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/TICMPUUUNISN3TJRIJRC2LQEZZJFO73P/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Information on "Multiple failed attempts to log in" emails

[John Bennett]

Hello,

Many of you may have been receiving emails in the last 24 hours warning you
of "Multiple failed attempts to log in" with your account. I wanted to let
you know that the Wikimedia Foundation's Security team is aware of the
situation, and working with others in the organization on steps to decrease
the success of attacks like these.

The exact source is not yet known, but it is not originating from our
systems. That means it is an external effort to gain unauthorized access to
random accounts. These types of efforts are increasingly common for
websites of our reach. A vast majority of these attempts have been
unsuccessful, and we are reaching out personally to the small number of
accounts which we believe have been compromised.

While we are constantly looking at improvements to our security systems and
processes to offset the impact of malicious efforts such as these, the best
method of prevention continues to be the steps each of you take to
safeguard your accounts. Because of this, we have taken steps in the past
to support things like stronger password requirements,[1] and we continue
to encourage everyone to take some routine steps to maintain a secure
computer and account. That includes regularly changing your passwords,[2]
actively running antivirus software on your systems, and keeping your
system software up to date.

My team will continue to investigate this incident, and report back if we
notice any concerning changes. If you have any questions, please contact
the Support and Safety team (susa{{@}}wikimedia.org).

John Bennett
Director of Security, Wikimedia Foundation

[1] https://meta.wikimedia.org/wiki/Password_strength_requirements
[2] https://meta.wikimedia.org/wiki/Special:ChangePassword
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Wikimedia-l Digest, Vol 172, Issue 4

[John Andersson]

Thank you WM RepublikaSrpska for sharing your report. Well done! I know
that it is a lot of work creating a report, but I find it to be a great
opportunity to reflect and learn. It is interesting for us other affiliates
to understand more about what you do. From my perspective you seem to have
a good mix of activities and I hope you will be able to scale even further
in the years to come. I must also say that I am impressed by the large
number of media mentions you've already managed to achieve.

Best,

John
- - - -
John Andersson
Executive Director
Wikimedia Sverige

Phone: +46(0)73-3965189
Email: john.anders...@wikimedia.se 
Visiting address: Goto10, Hammarby Kaj 10D, 120 32 Stockholm


Den tis 3 juli 2018 12:38  skrev:

> Send Wikimedia-l mailing list submissions to
> wikimedia-l@lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> or, via email, send a message with subject or body 'help' to
> wikimedia-l-requ...@lists.wikimedia.org
>
> You can reach the person managing the list at
> wikimedia-l-ow...@lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikimedia-l digest..."
>
>
> Today's Topics:
>
>1. Re: [Affiliates] Recognition of Wikimedia Community User
>   Group Uganda (Tanweer Morshed)
>2. [Wikimedia Announcements] The Signpost – Volume 14, Issue 7
>   – 29 June 2018 (Wikipedia Signpost)
>3. Final Report WM Community of the Republic of Srpska
>   (WМ RepublikaSrpska)
>4. Response to recent developments of United States  travel ban
>   (Katherine Maher)
>5. Re: Response to recent developments of United States travel
>   ban (Mardetanha)
>6. Re: Response to recent developments of United States travel
>   ban (David Cuenca Tudela)
>
>
> --
>
> Message: 1
> Date: Mon, 2 Jul 2018 23:17:50 +0600
> From: Tanweer Morshed 
> To: Wikimedia Mailing List 
> Cc: Wikimedia Movement Affiliates discussion list
> 
> Subject: Re: [Wikimedia-l] [Affiliates] Recognition of Wikimedia
> Community User Group Uganda
> Message-ID:
>  gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Congratulations to the Wikimedians from Uganda! All the best :)
>
> Regards,
> Tanweer
>
>
> On Sun, Jul 1, 2018 at 1:20 PM, Sam Oyeyele  wrote:
>
> > Congratulations to the Ugandan team. Welcome to the club! :)
> >
> > Sam.
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> >
>
>
> --
>
> Message: 2
> Date: Fri, 29 Jun 2018 21:16:03 -0400
> From: Wikipedia Signpost 
> To: wikimediaannounce-l 
> Subject: [Wikimedia-l] [Wikimedia Announcements] The Signpost –
> Volume 14, Issue 7 – 29 June 2018
> Message-ID:
>  gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> >From the editor: The Admin Ship is still barely afloat, while a Foundation
> project risks sinking
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
> 2018-06-29/From_the_editor
>
> Special report: NPR and AfC – The Marshall Plan: an engagement and a
> marriage?
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
> 2018-06-29/Special_report
>
> Op-ed: What do admins do?
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2018-06-29/Op-ed
>
> Opinion: Google isn't responsible for Wikipedia's mistakes
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
> 2018-06-29/Opinion
>
> News and notes: Money, milestones, and Wikimania
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
> 2018-06-29/News_and_notes
>
> In the media: Much wikilove from the Mayor of London, less from Paekākāriki
> or a certain candidate for U.S. Congress
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
> 2018-06-29/In_the_media
>
> Discussion report: Deletion, page moves, and an update to the main page
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
> 2018-06-29/Discussion_report
>
> Featured content: New promotions
> http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/
&g

[Wikimedia-l] Social media cards for sharing from the Wikipedia app

[John Lubbock]

Just wanted to make you all aware of a useful new feature of the Wikipedia
mobile app. You can share text from any Wikipedia page as a nice image by
highlighting it, pressing share, and then choosing the app you want to
share it to, like Twitter. See the images attached. Hope you all find this
useful.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

[Wikimedia-l] Wikimedia Sverige receives $65k+ in funding for our Library Data project

[John Andersson]

*Hi everybody and sorry for crossposting,Wikimedia Sverige is proud to be
the recipient of $65,500 in support from the Swedish National Library for
our project Library Data.We will work in collaboration with the Swedish
National Library to include a number of datasets onto Wikidata, such as
data about authors, libraries and different special databases of
bibliographies[1]. This is a pilot project where we aim to discuss with the
community what to include and what to exclude. Based on the discussions and
the requests from the community we will design a continuation of this
project (if this first part is deemed successful continuous funding is
possible for 3-4 more years).We started investigating a possible long term
partnership with the National Library in 2017 when Wikimedia Sverige
delivered inputs to the new National Strategy for the Library Sector on how
Sweden's libraries can work with Wikimedia for mutual benefits.[2] The
National Library has just made history as the world's first national
library to fully transition to Linked Open Data (BIBFRAME 2.0),[3] so the
timing could not have been better; we are now in position to examine how
this move can benefit Wikidata and other Wikimedia projects.Please contact
the project manager André Costa (andre.co...@wikimedia.se
) or the developer Alicia Fagerving
(alicia.fagerv...@wikimedia.se ) if you have
any questions. As always, you can find the full application on our wiki (in
Swedish):
https://se.wikimedia.org/wiki/Projekt:Strategisk_inkludering_av_biblioteksdata_på_Wikidata_2018/Ansökan
<https://se.wikimedia.org/wiki/Projekt:Strategisk_inkludering_av_biblioteksdata_p%C3%A5_Wikidata_2018/Ans%C3%B6kan>[1]
https://libris.kb.se/deldatabas.jsp <https://libris.kb.se/deldatabas.jsp>
[2]
https://commons.wikimedia.org/wiki/File:Wikimedia_Sverige_-_Wikipedia_och_biblioteken_i_Sverige.pdf
<https://commons.wikimedia.org/wiki/File:Wikimedia_Sverige_-_Wikipedia_och_biblioteken_i_Sverige.pdf>
(in Swedish)[3]
http://www.mynewsdesk.com/se/kungliga_biblioteket/pressreleases/kb-becomes-the-first-national-library-to-fully-transition-to-linked-data-2573975
<http://www.mynewsdesk.com/se/kungliga_biblioteket/pressreleases/kb-becomes-the-first-national-library-to-fully-transition-to-linked-data-2573975>
*
Kind regards,

John
- - - -
John Andersson
Executive Director
Wikimedia Sverige

Phone: +46(0)73-3965189
Email: john.anders...@wikimedia.se 
Visiting address: Goto10, Hammarby Kaj 10D, 120 32 Stockholm
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Updates for failed logins and OurMine

[John Bennett]

Hello,

The Security team will be putting together a brief summary of events
for both of these incidents and plan on sharing an overview by Sept
7th.  

Thanks
John Bennett

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] [GLAM] Wikimedia Sverige receives $65k+ in funding for our Library Data project

[John Andersson]

Hi Giselle,

You can read more about the project in English here:
https://se.wikimedia.org/wiki/Projekt:Strategisk_inkludering_av_biblioteksdata_på_Wikidata_2018/Background

Best,

John


Den mån 27 aug. 2018 18:24Wikimedia Argentina 
skrev:

> Congrats! Open data is the present and future of cultural projects :)
> I would love to read more about the project. This is the only link in
> english that I found [1]
> Have you got something else John?
>
>
> Best,
> Giselle
>
> [1]
> http://www.mynewsdesk.com/se/kungliga_biblioteket/pressreleases/kb-becomes-the-first-national-library-to-fully-transition-to-linked-data-2573975
>
> Giselle Bordoy
> Responsable de Comunicación y Cultura
> Communications and Cultural Manager
> *A. C. Wikimedia Argentina*
>
> 2018-08-27 11:08 GMT-03:00 Alex Stinson :
>
>> Congratulations John! Library data is such a powerful first step for
>> engaging partners, and we definitely need more case studies on this!
>>
>> Cheers,
>>
>> Alex
>>
>> On Mon, Aug 27, 2018 at 9:48 AM, John Andersson <
>> john.anders...@wikimedia.se> wrote:
>>
>>> *Hi everybody and sorry for crossposting,Wikimedia Sverige is proud to be
>>> the recipient of $65,500 in support from the Swedish National Library for
>>> our project Library Data.We will work in collaboration with the Swedish
>>> National Library to include a number of datasets onto Wikidata, such as
>>> data about authors, libraries and different special databases of
>>> bibliographies[1]. This is a pilot project where we aim to discuss with
>>> the
>>> community what to include and what to exclude. Based on the discussions
>>> and
>>> the requests from the community we will design a continuation of this
>>> project (if this first part is deemed successful continuous funding is
>>> possible for 3-4 more years).We started investigating a possible long
>>> term
>>> partnership with the National Library in 2017 when Wikimedia Sverige
>>> delivered inputs to the new National Strategy for the Library Sector on
>>> how
>>> Sweden's libraries can work with Wikimedia for mutual benefits.[2] The
>>> National Library has just made history as the world's first national
>>> library to fully transition to Linked Open Data (BIBFRAME 2.0),[3] so the
>>> timing could not have been better; we are now in position to examine how
>>> this move can benefit Wikidata and other Wikimedia projects.Please
>>> contact
>>> the project manager André Costa (andre.co...@wikimedia.se
>>> ) or the developer Alicia Fagerving
>>> (alicia.fagerv...@wikimedia.se ) if you
>>> have
>>> any questions. As always, you can find the full application on our wiki
>>> (in
>>> Swedish):
>>>
>>> https://se.wikimedia.org/wiki/Projekt:Strategisk_inkludering_av_biblioteksdata_på_Wikidata_2018/Ansökan
>>> <
>>> https://se.wikimedia.org/wiki/Projekt:Strategisk_inkludering_av_biblioteksdata_p%C3%A5_Wikidata_2018/Ans%C3%B6kan
>>> >[1]
>>> https://libris.kb.se/deldatabas.jsp <https://libris.kb.se/deldatabas.jsp
>>> >
>>> [2]
>>>
>>> https://commons.wikimedia.org/wiki/File:Wikimedia_Sverige_-_Wikipedia_och_biblioteken_i_Sverige.pdf
>>> <
>>> https://commons.wikimedia.org/wiki/File:Wikimedia_Sverige_-_Wikipedia_och_biblioteken_i_Sverige.pdf
>>> >
>>> (in Swedish)[3]
>>>
>>> http://www.mynewsdesk.com/se/kungliga_biblioteket/pressreleases/kb-becomes-the-first-national-library-to-fully-transition-to-linked-data-2573975
>>> <
>>> http://www.mynewsdesk.com/se/kungliga_biblioteket/pressreleases/kb-becomes-the-first-national-library-to-fully-transition-to-linked-data-2573975
>>> >
>>> *
>>> Kind regards,
>>>
>>> John
>>> - - - -
>>> John Andersson
>>> Executive Director
>>> Wikimedia Sverige
>>>
>>> Phone: +46(0)73-3965189
>>> Email: john.anders...@wikimedia.se 
>>> Visiting address: Goto10, Hammarby Kaj 10D, 120 32 Stockholm
>>> ___
>>> Wikimedia-l mailing list, guidelines at:
>>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>>> https://meta.wikimedia.org/wiki/Wikimedia-l
>>> New messages to: Wikimedia-l@lists.wikimedia.org
>>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>>> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
>>
>>
>>
>&g

[Wikimedia-l] Wikimedia Sverige receives $324k+ in funding for the project FindingGLAMs

[John Andersson]

Wikimedia Sverige is proud to be the recipient of $324,500 in support from
the Swedish Postcode Foundation for our project FindingGLAMs
<https://meta.wikimedia.org/wiki/FindingGLAMs>.

We will work in collaboration with UNESCO and the Wikimedia Foundation to
achieve a number of ambitious goals over the 15 month long project. We will
work to:

   - Collect and include data about GLAM[1] institutions around the world
   on Wikidata (e.g. where they are located). This will be done both through a
   campaign and from batch uploads of datasets;
   - Batch upload collections of media files, in collaboration with the
   Structured Data on Commons program;
   - Organize networks of experts to discuss issues with disseminating
   different types of material through the Wikimedia projects;
   - Create a white paper consisting of a number of case studies based on
   the work and discussions outlined above;
   - Communicate about the Wikimedia movement’s work with GLAMs at
   conferences;
   - Organize a number of activities both on- and offline to use the
   material. This include some work around Wikimania 2019 that will take place
   in Stockholm, Sweden.

We hope many of you would like to get involved in the project and work with
us to connect to GLAM partners in your countries. At this point we are
looking for your help to identify institutions that maintain lists of GLAM
institutions (similar to the collection of monuments lists for WLM) and
later to identify GLAM institutions with specific types of collections that
would like to work with the Wikimedia movement.

Please contact the project manager John Andersson (
john.anders...@wikimedia.se) if you have any questions. If you are
interested to take part, please sign up on the project portal at Meta:
https://meta.wikimedia.org/wiki/FindingGLAMs

As always, you can find the full application on our wiki (in Swedish):
https://se.wikimedia.org/wiki/Projekt:FindingGLAMs_2018/Ansökan

[1] GLAM is an acronym for Galleries, Libraries, Archives and Museums.

We look forward working with you!

Best regards,

John
- - - -
John Andersson
Executive Director
Wikimedia Sverige

Phone: +46(0)73-3965189
Email: john.anders...@wikimedia.se 
Visiting address: Goto10, Hammarby Kaj 10D, 120 32 Stockholm
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Updates for failed logins and OurMine

[John Bennett]

Hello,

Additional details for the May dictionary attack and the 2016 OurMine
attack have been provided at:

https://phabricator.wikimedia.org/phame/blog/view/13/

Thanks
John Bennett

On Mon, 2018-08-27 at 12:13 -0500, John Bennett wrote:
> Hello,
> 
> The Security team will be putting together a brief summary of events
> for both of these incidents and plan on sharing an overview by Sept
> 7th.  
> 
> Thanks
> John Bennett


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Monthly skill share idea

[John Lubbock]

Hi all, after talking to community members at the London meetup yesterday,
I want to suggest that we start running a monthly skillshare after work at
the Wikimedia UK office. It would be good to organise a 12 month programme
with skillshares on things like 'getting an article to featured article
status', AWB, Wikidata infoboxes, something on commons or photography
perhaps.

Would anybody like to suggest other subjects which it would be good to have
a workshop on? We need a list of 12 which would have some broad appeal to
the community and chapter members.

I would suggest Tuesday, Wednesday or Thursday, maybe first week of the
month. How does that sound to everyone?
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

[Wikimedia-l] Wikimedia Sverige receives $55k+ in funding for project on audio files

[John Andersson]

Wikimedia Sverige is proud to be the recipient of $55,000 in support from
the grant-giving organization Kulturbryggan (Culture Bridge) for a project
investigating how to best include audio files on Wikimedia Commons.

Our work will focus on batch uploading audio files onto Wikimedia Commons
(with a focus on music recordings). In preparations for this, we will
investigate how the metadata can be included in a way that is best suited
for Structured Data once it gets deployed. This is a pilot project where we
aim to discuss with the community what to include and what to exclude. The
discussions and the requests from the community will form our planning
around future work with uploading audio files onto Wikimedia Commons. We
look forward working with the community and with the Structured Data team
at Wikimedia Foundation on how metadata about audio files can be included
in a well-structured and useful way.

This project will connect very closely to the FindingGLAMs project[1] and
will form one of the case studies included in it. In the case study we will
provide guidance for other GLAMs and Wikimedia affiliates who want to
upload audio files in the future.

The project also connects closely to Wikimedia Sverige’s planned project
aimed at building tools to collect speech recordings. The recordings,
illustrating how words are pronounced etc., will then be used to improve
the quality of Wikispeech[2], a text-to-speech (TTS) system that converts
written text into speech. We want to see what type of speech recordings can
and should be stored on Wikimedia Commons and what kind of metadata should
be included there; this project will help us clarify the needs.

Please contact John Andersson (john.anders...@wikimedia.se) if you have any
questions.

As always, you can find the full application available on our wiki (in
Swedish).[3]

[1] https://meta.wikimedia.org/wiki/FindingGLAMs

[2] https://www.mediawiki.org/wiki/Wikispeech

[3]
https://se.wikimedia.org/wiki/Projekt:Fri_musik_p%C3%A5_Wikipedia_2019/Ans%C3%B6kan

Best,

John

- - - -

John Andersson

Executive Director

Wikimedia Sverige

Phone: +46(0)73-3965189

Email: john.anders...@wikimedia.se

Visiting address: Goto10, Hammarby Kaj 10D, 120 32 Stockholm
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] GLAM Digest, Vol 89, Issue 11

[John Andersson]

Thank you all for your kind words and excitement!


@Gnangarra, Ben:

Indeed one of the exciting possibilities working with audio is oral
histories. That our team now will be able to think, discuss and prepare for how
audio files best can be included on the Wikimedia projects should give us
relevant insights for future work.

I am also very much looking forward to see how the *Wikipeech Speech Data
Collector* (WSDC) tools might contribute to the collection of oral
histories.[1]

If funded we aim for WSDC to have a set of tools to crowdsource CC0
licensed speech data for the Wikimedia platforms and to become a service to
the entire FOSS community and to many others working with accessibility
online. Over time WSDC should allow us to add more languages to Wikispeech
and improve diversity on all platforms using MediaWiki. The same WSDC tools
could potentially also be useful for collecting, annotating and
disseminating e.g. oral histories or historical recordings.

To develop WSDC in 2019-2021 Wikimedia Sverige, together with a large
number of GLAM and university partners (with wonderful support from our
friends at Wikimedia Deutschland[2]), have recently sent in a major grant
application of 440,000 USD. We should get an answer about the funding in
February next year. (We are now among the last teams competing for the
funds and it looks very promising.) Please send positive thoughts!

[1] For the 75 page application detailing the project, see here (in
Swedish): https://se.wikimedia.org/wiki/Projekt:Wikispeech_2019/Ansökan
[2] WMDE's and WMSE's tech teams will share knowledge and insights
ongoingly as part of the project - I am very excited about more
inter-affiliate cooperation.

Kind regards and happy holidays,

John

PS. If funded we will be looking to hire at least one new developer with
expertise in speech data or other relevant skills. Drop me an email if you
are interested or if you know some great person.



> Den ons 19 dec. 2018 09:20 skrev :
>
>> Send GLAM mailing list submissions to
>> g...@lists.wikimedia.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.wikimedia.org/mailman/listinfo/glam
>> or, via email, send a message with subject or body 'help' to
>> glam-requ...@lists.wikimedia.org
>>
>> You can reach the person managing the list at
>> glam-ow...@lists.wikimedia.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of GLAM digest..."
>>
>>
>> Today's Topics:
>>
>>1. Re: [Wikimedia-l] Wikimedia Sverige receives $55k+ in funding
>>   for project on audio files (Gnangarra)
>>2. Re: [Wikimedia-l] Wikimedia Sverige receives $55k+ in funding
>>   for project on audio files (Ben Vershbow)
>>
>>
>> --
>>
>> Message: 1
>> Date: Wed, 19 Dec 2018 00:23:42 +0800
>> From: Gnangarra 
>> To: "Wikimedia & GLAM collaboration [Public]"
>> 
>> Cc: Wikimedia Mailing List 
>> Subject: Re: [GLAM] [Wikimedia-l] Wikimedia Sverige receives $55k+ in
>> funding for project on audio files
>> Message-ID:
>> > kbk6v0oeyw9ad8x1ux2x_1ikpn6vfklrpqt87+usehf...@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> As some who is working with oral histories this sounds interesting,
>>
>> On Wed, 19 Dec 2018 at 00:08, Sailesh Patnaik <
>> sailesh.patnaik...@gmail.com>
>> wrote:
>>
>> > Congratulations, John!
>> > It's really nice to see that Wikimedia Sweden is bringing such amazing
>> > initiatives to the movement.
>> >
>> > Regards!
>> >
>> > *Sailesh Patnaik *"*ଶୈଳେଶ ପଟ୍ଟନାୟକ**"*
>> > *Community Advocate, The Centre for Internet and Society*
>> > https://www.linkedin.com/in/sailesh-patnaik-551a10b4
>> > *Twitter*: @saileshpat
>> >
>> >
>> >
>> > On Tue, Dec 18, 2018 at 9:09 PM John Andersson <
>> > john.anders...@wikimedia.se> wrote:
>> >
>> >> Wikimedia Sverige is proud to be the recipient of $55,000 in support
>> from
>> >> the grant-giving organization Kulturbryggan (Culture Bridge) for a
>> project
>> >> investigating how to best include audio files on Wikimedia Commons.
>> >>
>> >> Our work will focus on batch uploading audio files onto Wikimedia
>> Commons
>> >> (with a focus on music recordings). In preparations for this, we will
>> >> investigate how the metadata can be included in a way that i

[Wikimedia-l] Security Notification: Malware creating fake Wikipedia donation banner

[John Bennett]

Hello,

In order to keep the community informed of threats against Wikimedia
projects and users, the Wikimedia Security team has some information to
share.

Malware installed via pirated contented downloaded from sites such as the
Pirate Bay can cause web browsers compromised by the malware to create a
fake donation banner for Wikipedia users. While the actual malware is not
installed or distributed via Wikipedia, unaware visitors may be confused or
tricked by it's activities.

The malware seeks to trick visitors to Wikipedia by looking like a
legitimate Wikipedia banner asking for donations. Once the user clicks on
the banner, they are then taken to a portal that leads them to transfer
money to a fraudulent bitcoin account that is not controlled by the
Foundation.

The current version of this malware is only infecting Microsoft Windows
users at the time of this notification. To date, the number of people
affected is small. The fraudulent accounts have taken approximately $700
from infected users. However, we strongly encourage all users to use and
update their antivirus software.


Additional details and a screenshot of the fake donation banner on can be
found at Bleepingcomputer.com. [0]

[0]
https://www.bleepingcomputer.com/news/security/fake-movie-file-infects-pc-to-steal-cryptocurrency-poison-google-results/

Thanks,

John Bennett
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Wikimedia Sverige receives a total of USD 500, 000+ in funding for three new projects, and a cost reduction of USD 30, 000/year

[John Andersson]

Wikimedia Sverige is proud to be the recipient of three new grants totaling
around USD 500,000. We hope to work with many of you as part of these
projects. If you are interested in getting involved or receiving updates
please let me know.

Furthermore, the chapter also has a new heavily subsidized agreement for
our office space.

Project 1: Wikispeech – The Speech Data Collector

The first project is a continuation of the Wikispeech[1] project, a
text-to-speech (TTS) system that converts written text into speech. From
September 2019 to April 2021 we aim to finalize building the MediaWiki
extension and to build tools to collect speech data to add pronunciations
to Wikipedia, Wiktionary and Wikidata and to add more languages to the
text-to-speech solution. The tools should also be possible to use for oral
citations.

The work happens in partnership with the Royal Technical Institute, STTS (a
language processing company), Mozilla Foundation, Wikimedia Deutschland and
the Swedish Dyslexia Association.

As always, you can find the full application on our wiki (in Swedish):
https://se.wikimedia.org/wiki/Projekt:Wikispeech_–_Talresursinsamlaren_2019/Ansökan

Project 2: Wikipedia in Libraries

From 2019 to 2020 Wikimedia Sverige, together with the National Library of
Sweden, will develop an online training module for Swedish librarians
focused around free knowledge and the Wikimedia platforms. This will be a
mandatory training for all of Sweden's 5,000 public librarians. Our hope is
to give all of them a basic understanding of the Wikimedia projects, as
well as to complement the online training with advanced courses for the
most dedicated. The advanced courses will give them the tools to ongoingly
organize activities and events independently at their libraries across the
country.

Furthermore, the librarians will be engaged in the #1Lib1Ref and
FindingGLAMs campaigns.

There is a great potential to receive continuous funding over the coming 3
years if successful.

As always, you can find the full application on our wiki (in Swedish):
https://se.wikimedia.org/wiki/Projekt:Wikipedia_i_biblioteken_2019/Ansökan

Project 3: Bibliographical data on Wikidata

We continue our work to include bibliographical data on Wikidata. The
project details are still being negotiated with the funder. The project
will start in mid-2019 and last until 2020.

Cost reduction

Starting from March 2019 we have a new agreement in place for a heavily
subsidized coworking space office from the Swedish Internet Foundation.
Through the agreement we will save us around USD 30,000 per year compared
to when we had an office of our own.

We have received this generous subsidy because Wikipedia is considered so
important for the infrastructure of the Internet. We are very happy that
the agreement does not have an end date and that we have the possibility to
grow significantly over time as well (while keeping the generous subsidy).

Please contact John Andersson (john.anders...@wikimedia.se) if you have any
questions.

[1] https://www.mediawiki.org/wiki/Wikispeech

Best,

John

- - - -

John Andersson

Executive Director

Wikimedia Sverige

Phone: +46(0)73-3965189

Email: john.anders...@wikimedia.se

Visiting address: Goto10, Hammarby Kaj 10D, 120 32 Stockholm
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Invitation to the July 2019 Wikimedia Monthly Activities Meeting: Thursday, July 25th, 18:00 UTC

[John DeBruyn]

Where, at what web address or URL would I be able confirm that what I
posted during the meeting was received and sent out to the other folks who
were participating in the meeting? Thanks, much appreciated, John DeBruyn
On Thu, Jul 25, 2019, 11:39 AM Sasha Redkina  wrote:

This meeting is starting in 20 min
>
> Sasha Redkina
> Front Office Coordinator
> *The Wikimedia Foundation*
> www.wikimediafoundation.org
>
>
> On Tue, Jul 23, 2019 at 3:25 PM Sasha Redkina 
> wrote:
>
> > Hello everyone,
> > The next Wikimedia Monthly Activities meeting will take place on
> Thursday,
> > July 25th, 2019 at 18:00  UTC (11 AM PDT). The IRC channel is
> > #wikimedia-office on https://webchat.freenode.net, and the meeting will
> > be broadcast as a live YouTube stream:
> > https://www.youtube.com/watch?v=kHnso8LvL_Q
> > We’ll post the video recording publicly after the meeting.
> >
> > Agenda
> >
> > Facilitator: TBA
> >
> >- Welcome and introduction to agenda - 2 minutes
> >- Movement update - 3 minutes
> >- Talk Pages Consultation presentation - 10 minutes
> >- Wikimedia Foundation updated website design demonstration - 10
> >minutes
> >- Wikimedia movement strategy update - 15 minutes
> >- Questions and discussion - 10 minutes
> >- Wikilove - 5 minutes
> >
> >
> >
> > Please review the meeting's Meta-Wiki page for further information about
> > the meeting and how to participate:
> > https://meta.wikimedia.org/wiki/Wikimedia_monthly_activities_meetings
> >
> >
> >
> > Thank you!
> > Sasha Redkina
> > Front Office Coordinator
> > *The Wikimedia Foundation*
> > www.wikimediafoundation.org
> >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Announcing the extension of funding by the Basque Government

[John DeBruyn]

Most extraordinary, all involved are to be congratulated, and
most importantly the Basque People and their Representatives who have
through their Government rendered such generous financial support, an
Example to the World.

With Personal and Warm Regards, Sincerely, John, John DeBruyn, Denver,
Colorado, United States of America, debruynlawoff...@gmail.com,
http://debruyn.com

On Wed, Sep 18, 2019, 8:17 AM Galder Gonzalez Larrañaga <
galder...@hotmail.com> wrote:

Dear wikimedians,
> Three years have gone since we started with the Basque Wikimedians User
> Group Education Program, funded by the Basque Government. After two years
> and a half of great enhancing of Basque Wikipedia (more than 2.500 students
> adding more than 1.5 million words on fundamental topics) the Basque
> Government has announce us today the extension of the funding for four more
> years.
>
> In this four years we will try to strengthen our Educaton Program but also
> open to new areas in order to make our knowledge equity vision possible. By
> 2024 we will have taken sure steps towards creating a free knowledge
> ecosystem centered at Wikimedia.
>
> Sincerely,
>
> Galder
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Multimedia projects & Wiktionary Cognate Dashboard at upcoming Wikipedia & Education Open Meeting September 30!

[John DeBruyn]

I tried several times to work my way through the password routine this
Monday morning, Denver, CO USA time, all to no avail, perhaps the routine
is more difficult than routine needs to be. I managed to join and
participate last week or the week before, hopefully I will eventually be
able to surmount the barriers to join in that I am now facing. John, John
DeBruyn, HTTP://debruyn.com, 303-919-4840

On Sun, Sep 29, 2019, 3:44 PM LiAnna Davis  wrote:

Reminder: This meeting is tomorrow: Monday, September 30, from 17:00 UTC to
> 18:30 UTC
>
> Join here: https://zoom.us/j/876197184
>
> On Sat, Sep 14, 2019 at 10:31 AM LiAnna Davis  wrote:
>
> > (usual cross-posting apologies!)
> >
> > TL;DR version:
> > * What: Wikipedia & Education User Group Open Meeting
> > * Who: Guest speakers Florencia Claes and Goran Milovanović
> > * When: Monday, September 30, from 17:00 UTC to 18:30 UTC
> > * Where: https://zoom.us/j/876197184
> > * Why: Be inspired about programs related to Commons and Wiktionary
> >
> > Full version:
> > On behalf of the Wikipedia & Education User Group, we cordially invite
> you
> > to attend our next Open Meeting on Monday, September 30, from 17:00 UTC
> to
> > 18:30 UTC. While our name includes Wikipedia, we support the use of all
> > Wikimedia projects in educational contexts. Our guest speakers this month
> > showcase that well!
> >
> > Florencia Claes, Communication and Journalism professor at Rey Juan
> Carlos
> > University in Madrid, Spain, will speak about how she's helped her
> students
> > contribute multimedia projects to Wikimedia Commons and add them to
> > Wikipedia, and her current project to collaborate with a documentary
> > filmmaking class to have students shoot videos for Commons. Florencia's
> > talk should be inspiring for anyone who has noticed a trend of students
> > preferring video over text, as we can all learn from her experiences!
> >
> > Goran S. Milovanović, PhD, Data Scientist, Software Department, Wikimedia
> > Deutschland, will speak about the Wiktionary Cognate Dashboard [1], and
> how
> > it can be used for identifying places for improvement on your language
> > Wiktionary. This is super relevant for anyone running programs on
> > Wiktionary!
> > [1] http://wmdeanalytics.wmflabs.org/Wiktionary_CognateDashboard/
> >
> > To join the meeting on the 30th, click this link:
> > https://zoom.us/j/876197184
> >
> > To add the invite to your calendar:
> > * Google Calendar:
> >
> https://zoom.us/meeting/tZMrduCvrzMup3tg0j_JqfZsHGec7RZlUw/calendar/google/add
> > * Outlook Calendar:
> > https://zoom.us/meeting/tZMrduCvrzMup3tg0j_JqfZsHGec7RZlUw/ics
> > * Yahoo Calendar:
> >
> http://calendar.yahoo.com/?v=60&VIEW=d&TITLE=Wikipedia%20%26%20Education%20User%20Group%20Monthly%20Open%20Meeting&in_loc=https%3A%2F%2Fzoom.us%2Fj%2F876197184&URL=https%3A%2F%2Fzoom.us%2Fj%2F876197184&ST=20190930T17Z&DUR=0130&DESC=Wiki%20Education%20is%20inviting%20you%20to%20a%20scheduled%20Zoom%20meeting.%0D%0A%0D%0AJoin%20Zoom%20Meeting%0D%0Ahttps%3A%2F%2Fzoom.us%2Fj%2F876197184%0D%0A
> >
> > Full agenda:
> > * Intros
> > * Update from UG board
> > * Updates from Wikimania
> > * Updates from working groups
> > * Featured speakers: Florencia Claes, Goran Milovanović
> > * Q & A
> >
> >
> >
>
> --
> LiAnna Davis
> Chief Programs Officer; Deputy Director
> Wiki Education
> www.wikiedu.org
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Movement Strategy: Outcomes of the Harmonization Sprint in Tunis

[John DeBruyn]

Job well done, high five, John, John DeBruyn, cell phone 303-919-4840,
Http://debruyn.com, wiki booster

On Mon, Sep 30, 2019, 10:27 AM Nicole Ebber 
wrote:

Hi everyone,
>
> We recently held the harmonization sprint in Tunis [1], where
> representatives from each working group met in person to continue bringing
> nine separate sets of draft recommendations into one set. The event also
> brought together staff members from the Wikimedia Foundation and Wikimedia
> Deutschland, the WMF Chair of the Board of Trustees, and members of the
> core team. A longer narrative report will be published in the coming weeks;
> in the meantime, see a short day-by-day report on Meta, photos on commons
> [2], and check out the hashtag #hs2030 on Twitter [3].
>
> In the lead up to the meeting, the working groups were busy refining their
> draft recommendations based on feedback received at in person events from
> Wikimedians across the movement as well as on wiki, via email, and on
> social media since March of this year. They had also begun identifying
> overlaps in each other’s recommendations and content. A second iteration of
> draft recommendations [4] was published on Meta just before the sprint for
> the communities’ information.
>
> At the sprint, we continued to group recommendations based on
> commonalities. From there, we looked at what kinds of structures would need
> to be in place to deliver the Wikimedia 2030 vision. A first, rough
> grouping of recommendations came together at the sprint. But what became
> clear during the event was that before it’s possible to create a coherent
> and actionable set of recommendations, fundamental principles that underpin
> the path towards 2030 need to be formalized.
>
> The core team is currently processing the discussion materials and
> outcomes. Analysis of the current draft recommendations will continue so as
> to create one unified set. The timeline will shift and we are looking into
> options for another round of community input.
>
> I would like to make clear that the reason we were not able to achieve our
> initial goal in Tunis was due to a lack of clarity and guidance on the core
> team’s part. Still, the time was not wasted and important, honest
> conversations were had. The working group members, as ever, devoted an
> enormous amount of energy and care in the lead up to and during the event,
> and demonstrated their deep understanding of the challenges and
> opportunities in our movement. We are extremely grateful for all their
> effort. In short, the harmonization sprint underlined the high level of
> work and dedication every single working group member has put into getting
> the movement strategy to its current point, and the passion to shape the
> future of the diverse and inclusive movement we envision.
>
> We have valuable lessons to take from this event and incorporate into the
> overall process and the next steps. We will share these with you all as
> soon as possible. If you have questions in the meantime, please feel free
> to reach out to me.
>
> Best regards,
> Nicole
>
> [1]
>
> https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recommendations/Harmonization_Sprint
> [2]
>
> https://commons.wikimedia.org/wiki/Category:Wikimedia_2030_Harmonization_Sprint
> [3] https://twitter.com/search?q=%23hs2030
> [4]
>
> https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2018-20/Recommendations
>
>
> --
> Nicole Ebber
> Adviser International Relations
> Program Manager Wikimedia 2030 Movement Strategy
> Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
> Tel. (030) 219 158 26-0
> https://wikimedia.de
>
> Unsere Vision ist eine Welt, in der alle Menschen am Wissen der Menschheit
> teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
> https://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.
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] WikiConference North America live stream

[John DeBruyn]

Re: [Wikimedia-l] WikiConference North America live stream

Good morning Phoebe, Ziko, Pete, James, Gerard, Peter, Samuel and all, it
is 2 am or so my time. Perhaps a YouTube channel offers a solution. I have
used a YouTube channel many times to record conferences, albeit on a much
smaller scale. YouTube, as you likely know, also provides a text channel
that functions in tandem with the video channel for interaction between
attendees and participants in the program. The transcript of the
interaction in the text channel is preserved as part of the records of the
YouTube channel. Here is what I was up to with my mentor, Ward Cunningham
and other pioneers in the early development of wikis and Wikipedia, during
the 1990s and the early 2000s, https://wiki.c2.com/?JohnDeBruyn John, John
DeBruyn, Golden, Colorado USA 80401, my current email address is
debruynlawoff...@gmail.com, my cell phone is 303-919-4840 and is my
preferred means of one on one communication.

On Thu, Nov 21, 2019 at 10:12 PM Samuel Klein  wrote:

We have full copyright over these videos, which are intended to be posted
> to Commons under CC-BY.
> There are a couple of sessions from the live.fsf stream which will not be
> posted online at the request of the participants, but the videos from the
> three main rooms can all be posted to Commons.
>
> Warmly, SJ
>
> On Thu, Nov 21, 2019 at 4:44 PM Pete Forsyth 
> wrote:
>
> > Phoebe and WikiConference team,
> >
> > It was a great conference -- thank you! -- and wonderful to have
> > high-quality video made available. (To answer my earlier question -- the
> > link supplied before still leads to the videos, though you might have to
> > dig around to find any specific session.)
> >
> > QUESTION: Do you know if MIT asserts any copyright over the videos? I'd
> > like to upload a couple to Commons, but want to be sure the copyright
> won't
> > be an issue.
> >
> > -Pete
> > --
> > Pete Forsyth
> > User:Peteforsyth
> >
> > On Thu, Nov 7, 2019 at 11:31 AM phoebe ayers 
> > wrote:
> >
> > > Dear all,
> > > We are looking forward to WikiConference North America here at MIT in
> > > Cambridge, Massachusetts this weekend! We will be welcoming around 250
> > > people over the four-day weekend, with a museum and cultural
> institution
> > > culture crawl on Friday, conference sessions on Saturday and Sunday,
> and
> > > discussion/hackathon focused on reliability and credibility on Monday.
> > >
> > > For those who can't be here with us in person, we have a live stream
> > > planned of three of our session rooms on Saturday and Sunday. To access
> > the
> > > stream, go here:
> > > http://web.mit.edu/webcast/wiki/f19/
> > >
> > > We are looking forward to sharing as much of the conference as we can
> > with
> > > you all! To find out what is when, the schedule is here (all times
> > eastern
> > > time):
> > > https://wikiconference.org/wiki/2019/Schedule
> > >
> > > We have a packed schedule with sessions about education, research,
> > > outreach, and more, as well as a special focus/track in our main
> > auditorium
> > > on credibility and reliability in the news and media, which our
> partners
> > at
> > > the Credibility Coalition are assisting with. As we think about the
> > future
> > > of Wikipedia as a reliable source in a world where social media
> platforms
> > > and media networks are struggling with issues of misinformation and
> > > credibility, we hope that this program will be both timely and helpful.
> > >
> > > Let me know if you have any questions and I hope you are able to tune
> in
> > > online.
> > > Phoebe, for WCNA
> > >
> > >
> > > --
> > > * I use this address for lists; send personal messages to phoebe.ayers
> > 
> > > gmail.com *
> > > ___
> > > Wikimedia-l mailing list, guidelines at:
> > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > > https://meta.wikimedia.org/wiki/Wikimedia-l
> > > New messages to: Wikimedia-l@lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> > ___
> > Wikimedia-l mailing list, guidelines at:
> > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> > https://meta.wikimedia.org/wiki/Wikimedia-l
> > New messages to: Wikim

Re: [Wikimedia-l] Wikimedia-l Digest, Vol 201, Issue 38

[John Andersson]

Hi,

All of the Annual Planning Grants (APGs) to Wikimedia affiliates are next
year paid through Tides Advocacy. Wikimedia Foundation has communicated
this change to all of us affiliates that are affected many months ago, and
there is nothing secretive going on. Please assume good faith.

Best,

John Andersson
Executive Director
Wikimedia Sverige

Den sön 13 dec. 2020 13:02  skrev:

> Send Wikimedia-l mailing list submissions to
> wikimedia-l@lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> or, via email, send a message with subject or body 'help' to
> wikimedia-l-requ...@lists.wikimedia.org
>
> You can reach the person managing the list at
> wikimedia-l-ow...@lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikimedia-l digest..."
>
>
> Today's Topics:
>
>1. Re: WMF transfers $8.7 million to "Wikimedia Knowledge Equity
>   Fund" (Christophe Henner)
>
>
> --
>
> Message: 1
> Date: Sun, 13 Dec 2020 12:39:31 +0100
> From: Christophe Henner 
> To: Wikimedia Mailing List 
> Subject: Re: [Wikimedia-l] WMF transfers $8.7 million to "Wikimedia
> Knowledge Equity Fund"
> Message-ID:
>  w...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> It is the endowment.
>
> Le dim. 13 déc. 2020 à 10:37 AM, Yair Rand  a écrit :
>
> > No, the Wikimedia Endowment is a separate thing.
> >
> > -- Yair Rand
> >
> > ‫בתאריך יום א׳, 13 בדצמ׳ 2020 ב-4:18 מאת ‪Michael Peel‬‏ <‪
> > em...@mikepeel.net‬‏>:‬
> >
> >> https://meta.wikimedia.org/wiki/Wikimedia_Endowment ?
> >>
> >> On 13 Dec 2020, at 08:33, Yair Rand  wrote:
> >>
> >> According to the recent Independent Auditors' Report of the WMF [1], at
> >> some point prior to the end of June 2020, an entity called the
> "Wikimedia
> >> Knowledge Equity Fund" was established, and $8.723 million was
> transferred
> >> to it by the WMF, in the form of an unconditional grant. The Fund is
> >> "managed and controlled by Tides Advocacy" (a 501(c)(4) advocacy
> nonprofit
> >> previously led by the WMF's current General Counsel/Board Secretary, who
> >> served as CEO, Board Secretary, and Treasurer there). Given that a
> Google
> >> search for "Wikimedia Knowledge Equity Fund" yields zero results prior
> to
> >> the release of the report, it is clear that the WMF kept this
> significant
> >> move completely secret for over five months, perhaps over a year. The
> >> Report FAQ additionally emphasizes that the WMF "has no right of return
> to
> >> the grant funds provided, with the exception of unexpended funds."
> >>
> >> The WMF unilaterally and secretly transferred nearly $9 million of
> >> movement funds to an outside organization not recognized by the
> >> Affiliations Committee. No mention of the grant was made in any Board
> >> resolutions or minutes from the relevant time period. The amount was not
> >> mentioned in the public annual plan, which set out rather less than this
> >> amount for the entire grantmaking budget for the year. No application
> was
> >> made through any of the various Wikimedia grants processes. No further
> >> information has been provided on the administration of this new Fund,
> or on
> >> the text of the grant agreement.
> >>
> >> I am appalled.
> >>
> >> -- Yair Rand
> >>
> >> [1]
> >>
> https://upload.wikimedia.org/wikipedia/foundation/f/f7/Wikimedia_Foundation_FY2019-2020_Audit_Report.pdf
> >> ___
> >> Wikimedia-l mailing list, guidelines at:
> >> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> >> https://meta.wikimedia.org/wiki/Wikimedia-l
> >> New messages to: Wikimedia-l@lists.wikimedia.org
> >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <
> >> mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
> >> >
> >>
> >>
> >> ___
> >> Wikimedia-l mailing list, guidelines at:
> >> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> >> https://meta.wikimedia.org/wiki/Wikimedia-l
> >> New mess

[Wikimedia-l] Design the Wikispeech logo until December 4th, vote on designs until the 11th

[john cummings]

Dear all

The Wikispeech project is looking for an official logo. You can submit
designs until the 4th of December and vote on which are you favourite logo
until the 11th.

The Wikispeech project aims to create an open source text-to-speech tool to
make Wikimedia's projects more accessible. You can find out more about the
project, submit new logo designs and vote on existing logo designs here.

https://www.mediawiki.org/wiki/Wikispeech

Many thanks

John
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Superprotect's first birthday

[John Lewis]

On Tuesday, August 11, 2015, Magnus Manske 
wrote:

> Out of curiosity, was it ever used again after that initial action?
>
>
Yes. It was used a few months ago to prevent editing the Germany item on
Wikidata due to a very serious breaking issue. Also on several pages
following legal disputes.

Superprotect in my opinion if used correctly is an essential tool which can
prevent legal and technical issues that can in theory cause wide disruption.

John


-- 
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Announcement

[John Lewis]

It is really sad to see you leave, but your health must be your priority,
and not the community as it has been for the past six years. Everything you
have done was always in the best interests of the wider community and that
will never be forgotten.

You've always worked on opening new doors for people and have entrusted
responsibilities into others as well for the greater benefit of the
community. You're leaving the best legacy possible - even if we ignore the
six years :)

Good luck in future opportunities and your health. No one is more deserving
of a rest than yourself!

And congratulations to Maggie - while she is not Philippe, she definitely
will do her best to be the new Philippe.

Regards,
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] WMF Advanced Permissions

[John Lewis]

I believe they already filled the position as they hired Karen about a week
ago (after the announcement). ca. Staff and contractors page and IRC office
hour.

John Lewis

On Friday, 25 September 2015, Pine W  wrote:

> Speaking of Trust and Safety, is there going to be a back-filled position
> in CA in light of Philippe's departure and Maggie's promotion?
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org 
> ?subject=unsubscribe>



-- 
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Invitation to beta-test HHVM

[John Lewis]

On Friday, 19 September 2014, Todd Allen  wrote:

> This was testing done right. The feature was offered as opt in and clearly
> marked as beta.
>

This genuinely is testing done right. HHVM has been on the beta cluster for
a few months and has been enabled on testwiki by default for a month. In
addition it has been opt-in on production for a week or two already. This
is purely an easy way for people to test as the other way was, sort of
annoying :)

John Lewis


-- 
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

[Wikimedia-l] Looking for feedback on my funding proposal to work with UNESCO as Wikimedian in Residence

[John Cummings]

include as many language Wikimedia
projects as I can.

Many thanks

Mrjohncummings <https://en.wikipedia.org/wiki/User:Mrjohncummings>


-- 
*John Cummings - **Wikimedia UK volunteer*
tweet @mrjohnc

Wikimedia UK is a Charitable Company registered in England and Wales.
Registered Company No. 6741827. Registered Charity No.1144513.
Registered Office: 4th Floor, Development House, 56-64 Leonard Street,
London EC2A 4LT. United Kingdom.
Wikimedia UK is the UK chapter of a global Wikimedia movement. The
Wikimedia projects are run by the Wikimedia Foundation (who operate
Wikipedia, amongst other projects).
Wikimedia UK is an independent non-profit charity with no legal control
over Wikipedia nor responsibility for its contents.

Telephone (0044) 207 065 0990.

Visit http://www.wikimedia.org.uk/ and @wikimediauk




-- 
*John Cummings - **Wikimedia UK volunteer*
tweet @mrjohnc

Wikimedia UK is a Charitable Company registered in England and Wales.
Registered Company No. 6741827. Registered Charity No.1144513.
Registered Office: 4th Floor, Development House, 56-64 Leonard Street,
London EC2A 4LT. United Kingdom.
Wikimedia UK is the UK chapter of a global Wikimedia movement. The
Wikimedia projects are run by the Wikimedia Foundation (who operate
Wikipedia, amongst other projects).
Wikimedia UK is an independent non-profit charity with no legal control
over Wikipedia nor responsibility for its contents.

Telephone (0044) 207 065 0990.

Visit http://www.wikimedia.org.uk/ and @wikimediauk
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Commons / OTRS is broken

[John Cummings]

Depending on where the content is coming from uploading the images to
Flickr and then importing them may be an option. When I worked for the
Science Museum we simply changed the licence of some of the images on their
Flickr account and I used Flickr2Commons to import them, it also records
the attribution and which CC licence the images used. I'm currently working
with UNESCO to release some of their archive and will most probably suggest
this route which as a bonus creates a second large audience for the content
on Flickr.

Hope this is helpful

John
On 2 Feb 2015 22:52, "James Heilman"  wrote:

> OTRS does not even bother replying to the consents I send them. Thus the
> images I have received releases for get deleted. Going forwards I am simply
> uploading to En Wikipedia. Not ideal but not sure what the solution is.
>
> --
> James Heilman
> MD, CCFP-EM, Wikipedian
>
> The Wikipedia Open Textbook of Medicine
> www.opentextbookofmedicine.com
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Reasonator use in Wikipedias

[John Vandenberg]

If I understand you correctly, the redlink wont be touched, but the empty
page will show reasonator data on it (ideally displayed using the
approptiate infobox). That would help readers and (source editor) writers,
as the important facts are on the screen for them to include into the prose
of the new article.
On Jan 21, 2014 10:18 PM, "Gerard Meijssen" 
wrote:

> Hoi,
>
> At this moment Wikipedia "red links" provide no information whatsoever.
> This is not cool.
>
> In Wikidata we often have labels for the missing (=red link) articles. We
> can and do provide information from Wikidata in a reasonable way that is
> informative in the "Reasonator". We also provide additional search
> information on many Wikipedias.
>
> In the Reasonator we have now implemented "red lines" [1]. They indicate
> when a label does not exist in the primary language that is in use.
>
> What we are considering is creating a template {{Reasonator}} that will
> present information based on what is available in Wikidata. Such a template
> would be a stand in until an article is actually written. What we would
> provide is information that is presented in the same way as we provide it
> as this moment in time [2]
>
> This may open up a box of worms; Reasonator is NOT using any caching. There
> may be lots of other reasons why you might think this proposal is evil. All
> the evil that is technical has some merit but, you have to consider that
> the other side of the equation is that we are not "sharing in the sum of
> all knowledge" even when we have much of the missing requested information
> available to us.
>
> One saving (technical) grace, Reasonator loads round about as quickly as
> WIkidata does.
>
> As this is advance warning, I hope that you can help with the issues that
> will come about. I hope that you will consider the impact this will have on
> our traffic and measure to what extend it grows our data.
>
> The Reasonator pages will not show up prettily on mobile phones .. so does
> Wikidata by the way. It does not consider Wikipedia zero. There may be more
> issues that may require attention. But again, it beats not serving the
> information that we have to those that are requesting it.
> Thanks,
>   GerardM
>
>
> [1]
>
> http://ultimategerardm.blogspot.nl/2014/01/reasonator-is-red-lining-your-data.html
> [2] http://tools.wmflabs.org/reasonator/test/?lang=oc&q=35610
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] extend mediawiki software to allow append a "group", and "COI" to an edit

[John Vandenberg]

Hi rupert,

I think this requester feature has merit, as it provides a tool for
communities to use for this purpose (COI) and others.

One possible implementation is the tag system already part of the Abuse
Filter extension. Bug 18670 requests the tag system be more flexible,
allowing false positives to be addessed, and would also allow self-tagging
of edits.

https://bugzilla.wikimedia.org/show_bug.cgi?id=18670
On Feb 22, 2014 10:26 PM, "rupert THURNER"  wrote:

> hi,
>
> could wmf please extend the mediawiki software in the following way:
> 1. it should knows "groups"
> 2. allow users to store an arbitrary number of groups with their profile
> 3. allow to select one of the "group"s joined to an edit when saving
> 4. add a checkbox "COI" to an edit, meaning "potential conflict of
> interest"
> 5. display and filter edits marked with COI in a different color in history
> views
> 6. display and filter edits done for a group in a different color in
> history views
> 7. allow members of a group to receive notifications done on the group
> page,
>or when a group is mentioned in an edit/comment/talk page.
>
> reason:
> currently it is quite cumbersome to participate as an organisation. it is
> quite cumbersome for people as well to detect COI edits. the most prominent
> examples are employees of the wikimedia foundation, and GLAMs. users tend
> to create multiple accounts, and try to create "company accounts". the main
> reason for this behaviour are (examples, but of course valid general):
> * have a feedback page / notification page for the swiss federal archive
> for other users
> * make clear that an edit is done private or as wmf employee
>
> this then would allow the community to create new policies, e.g. the german
> community might cease using company accounts, and switch over to this
> system. this proposal is purely technical. current policies can still be
> applied if people do not need something else, e.g. wmf employees may
> continue to use "sue gardner (wmf)" accounts.
>
> what you think?
>
> best regards,
> rupert
> ---
> swissGLAMour, http://wikimedia.ch
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] next Wikidata IRC office hour

[John Lewis]

The log is now available at
https://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2014-05-19

Thank you to all who attended :)

John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Community RfCs about MediaViewer

[John Lewis]

I don't see any office action at all here. All I see is an administrator
acting per what a WMF staffer has said. The code added as explained on the
page; disables the feature fully and does not allow any opt ins.

John Lewis

On Thursday, 10 July 2014, MZMcBride  wrote:

> Erik Moeller wrote:
> >On Wed, Jul 9, 2014 at 10:03 PM, Pine W  > wrote:
> >> Will WMF deactivate MediaViewer on English Wikipedia
> >
> >No.
>
> Erik has stepped in and employed an office action to re-enable Media
> Viewer on the English Wikipedia.
>
> Erik, can you please explain what emergency necessitated immediate (and
> likely unprecedented) action here?
>
> MZMcBride
>
>
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org 
> ?subject=unsubscribe>



-- 
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Community RfCs about MediaViewer

[John Lewis]

I am aware they are the same.

John Lewis

On Thursday, 10 July 2014, MZMcBride  wrote:

> John Lewis wrote:
> >I don't see any office action at all here. All I see is an administrator
> >acting per what a WMF staffer has said.
>
> Sorry, I have no idea what you're talking about here. I think you may not
> realize that Erik and Eloquence are the same person?
>
> For reference:
>
> ---
> Per Fabrice's explanation, please refrain from further edits to the site
>  JavaScript, or I will have to temporarily revoke your admin privileges.
>  This is a WMF action.--Eloquence* 20:07, 10 July 2014 (UTC)
> ---
>
> Source: https://en.wikipedia.org/w/index.php?diff=616427707&diffonly=1
>
> MZMcBride
>
>
>
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org 
> ?subject=unsubscribe>



-- 
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Superprotect user right, Comming to a wiki near you

[John Lewis]

The people who were actually responsible were the community. Erik was
acting in a preventative role to prevent further disruption not punish
administrators. The community. couldn't take no for an answer and what has
happened?

* Wheel/edit wars
* A new user right to prevent disruption
* A priviledge has been revoked on dewiki
* A user has been desysoped by the community for no reason on dewiki

And who are we blaming? Erik. Why? Because we are a bunch of stubborn
children. We don't get what we want so we are kicking and screaming to get
it but in the end; we don't and we then accuse our parent (WMF) of being
too harsh, mean and taking away something we like but do not deserve.

To be honest - until we as a community learn we are not the overlords, the
masters, god of
Wikimedia, we can work to building a real encyclopedia with awesome feature
where are all work in a good environment and get on as a community and
Foundation.

I am not saying the WMF is perfect and is not in the wrong; they certainly
have some blame to take and I will come onto that shortly, but we can not
blame the Foundation for revoking something we clearly do not deserve.

>
Erik, While I will say you have not been communicating stuff the best you
can and this new user right was proxy deployed by Tim and an advocate and
not your self - you mean well and I see this. I agree with everything you
have done so far as a matter of fact.

Fabrice, Have you attempted to start any discussions with communities in
exactly why they don't want Media Viewer and how exactly it causes so much
dispute that it requires Erik to proxy intervene? It not, please do so.

In a short conclusion - I feel both parties have acted inappropriately and
our bitching at each other does far than solve it. The WMF had to implement
a new right and revoke dewiki's access to their site wide js page because
of their refusal to accept what the WMF said and want to create a
performance killer hack to 'fix it' at the cost of performance. Why did
dewiki have to do this? The WMF refusing to disable Media Viewer. From what
I see, the WMF have backed up by they refused to do this for Wikipedias and
their compromise for Commons is acceptable. I have yet to see a valid
reason why Media Viewer exactly makes Wikipedia go into a 'OMG UNUSABLE
DISABLE IT FUCKING NOW OR I WILL' state. Media Viewer allows you to view
and images without leaving the page - reducing load time for both users and
the WMF. It is hardly the beginning if the end for images.

If we take a quick look at the statistics - 64 voted against Media Viewer
on the English Wikipedia while 6kish users enabled it, this shows 1.1%
consensus for disabling the extension in a whole.

I will not ramble on any more. I just ask the community to stop bitching at
the WMF and accept their decision. Until then - I fully support Erik super
protecting every single js and CSS page on every wiki as most Sysop I feel
are technically incompetent.

John Lewis



-- 
John Lewis
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Odder on moderation?!

[John Lewis]

I'm an administrator for a few lists and personally I feel you are being
far far too generic in saying lists are not managed correctly. A process is
not broken here just a users understanding.  Document don't argue regarding
processes.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

Re: [Wikimedia-l] PRISM

[John Vandenberg]

On Mon, Jun 10, 2013 at 11:00 PM, Anthony  wrote:
> On Mon, Jun 10, 2013 at 6:21 AM, Fred Bauder  wrote:
>> No, massive amounts of information about people doing ordinary
>> things like editing articles about Homer Simpson is kind of the opposite
>> of intelligence; it IS the haystack, not the needle.
>>
>
> And yet, PRISM is exactly about collecting the full haystack.  And it makes
> sense, if you ignore the privacy implications:  Collect everything in your
> multi-zetabyte storage device, even if you aren't going to analyze it right
> away.

And we give every needle a distinct and descriptive name.

> And yeah, editing articles about Homer Simpson is one thing.  Editing
> articles about the Tea Party, on the other hand...

Or DeCSS, or AACS, ..

Or 2012 Benghazi attack, Efforts to impeach Barack Obama, Drone
attacks in Pakistan, ..

Or PRISM (surveillance program), Edward Snowden, Bradley Manning, ..

It would be good *if* the WMF can provide assurances to editors that
they havent received any national security letters or other 'trawling'
requests from any U.S. agency.

If the WMF has received zero such requests, can the WMF say that?
There wouldn't be any gag order.

https://en.wikipedia.org/wiki/National_security_letter says that the
gag orders were struck down, pending appeal.  That means we may have
to wait a while..

--
John Vandenberg

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] PRISM

[John Vandenberg]

On Tue, Jun 11, 2013 at 8:15 AM, Luis Villa  wrote:
> Hi, all-
>
> For your information, we have not been approached to participate in
> PRISM, and we have never received or honored an NSA or FISA subpoena
> or order.  If we were to be approached in the future, we would reject
> participation in any PRISM-type program to the maximum extent possible
> and challenge in court any such demand, since this sort of program, as
> described in the press, contradicts our core values of a free Internet
> and open, neutral access to knowledge.
>
> We should have a blog post up within the next few days to discuss
> PRISM and our values in more detail; we will pass that along here when
> it is posted.

Thanks.

Please put the draft on meta so the volunteers can review it and
identify phrases which are not tight enough.

e.g. "we have never received or honored an NSA or FISA subpoena or
order" is good (and far better than I've seen from Google or
Facebook), but ...

does that exclude all possible orders under the Patriot Act?
does that exclude orders from any U.S. Government agency?  e.g. FBI?

I don't know the answer to those questions, and I am sure the average
reader doesn't either.  It would be helpful to have a response with
has both precise language and broad statements that will ensure the
layman doesnt worry that WMF is dodging the question.

--
John Vandenberg

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] [Advocacy Advisors] WMF response to PRISM?

[John Vandenberg]

On Tue, Jul 9, 2013 at 4:07 PM, James Salsman  wrote:
> Would publicizing these free and open secure alternatives to commercial
> applications known to be under surveillance -- https://prism-break.org/ --
> be sufficiently aligned with out values?

Our values?  ...
Our practise.  No.

SSL is mandatory to avoid surveillance, but TOR is also quite important.

The very first entry on prism-break is TOR, which is blocked on
Wikimedia projects for editing, by explicit blocks and by the TorBlock
extension, which is enabled on all wikis, even Chinese Wikipedia.

https://www.mediawiki.org/wiki/Extension:TorBlock
https://zh.wikipedia.org/wiki/Special:Version

The mobile functionality is very unfriendly for privacy.

Loading a non-mobile HTTPS url (e.g.
https://en.wikipedia.org/wiki/1984), redirects the reader to the
mobile HTTP page.  If they clicked on a https link believing that
their browsing pattern was not able to be monitored, their reading
patterns are in clear text on the internet without them being informed
of this.  The EFF is pushing solutions to send readers from HTTP to
HTTPS sites, and WMF is sending readers from HTTPS to HTTP -
transparently.

https://bugzilla.wikimedia.org/show_bug.cgi?id=35215
(reported March 2012, last comment from WMF tech team in April 2013
indicates this may not be fixed soon)

Admins can bypass the Tor block, however logging in on Mobile is not easy.
In the mobile search type in special:userlogin.  The login screen
appears, and the 'sign in' button replies to the user that there was a
cookie error.

https://bugzilla.wikimedia.org/show_bug.cgi?id=31045
(reported 2011; closed as INVALID the same day)

When using the Orweb browser (part of the tor solution for Android),
trying to log in is even more difficult as you cant go to the Desktop
site without tying in a long url that bypasses the mobile site.

https://bugzilla.wikimedia.org/show_bug.cgi?id=51277
(reported by me today)

--
John Vandenberg

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] [Wikimedia Announcements] 2013-14 Annual Plan of the Wikimedia Foundation

[John Vandenberg]

On Tue, Jul 9, 2013 at 3:00 PM, Tilman Bayer  wrote:
> Hi all,
>
> the Wikimedia Foundation's 2013-14 Annual Plan has just been published at
>
> https://wikimediafoundation.org/wiki/File:2013-2014_WMF_Plan_As_Published.pdf
>
> accompanied by a Q&A:
>
> https://wikimediafoundation.org/wiki/2013-2014_Annual_Plan_Questions_and_Answers
>
> The plan was approved by the Board of Trustees on June 28, 2013.

I have converted it to wiki text.

https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Plan_2013-14

It doesnt have the graphs yet.  Maybe someone at WMF can easily create
those graphs from the original document?  If not, we'll have to
rebuild them.

--
John Vandenberg

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Staff Images

[John Andersson]

As
 a non-native English speaker the only real problem that I can see is 
that the message could be hard to understand for some people. Hence, I 
hope that Brandon would be willing to internationalize himself a bit and
 add proper translations. The Swedish translation of "Courage" is "Mod" - feel 
free 
to add the new tattoo wherever you see fit.  



Best, 

John

- - - -



John Andersson



Wikimedia Sverige



Project Leader Europeana Awareness 







Phone: +46(0)73-3965189





Email: john.anders...@wikimedia.se




Skype: johnandersson86  

  

Be sure to follow us on Twitter at @wikieuropeana

 Would you like to support free knowledge? Please consider becoming a member of 
Wikimedia Sweden!


> Date: Sun, 14 Jul 2013 17:47:08 +0100
> From: geni...@gmail.com
> To: wikimedia-l@lists.wikimedia.org
> Subject: Re: [Wikimedia-l] Staff Images
> 
> On 14 July 2013 00:44, Lucas Teles  wrote:
> 
> > Is that [1] the photo? I was expecting something worse per the opening of
> > this discussion. It seems to be fine for me (in a manly way of saying a
> > photo of another man is fine), expect for the removal of Brandon's fingers.
> > --Teles
> >
> >
> > [1] - https://wikimediafoundation.org/wiki/File:Brandon_Harris_courage.jpg
> >
> >
> Its not fine. Look at the colour blotching under the arm. I wouldn't expect
> that from the 5DII even at ISO 640. Looks like its been pushed a bit too
> far in post. That said looking at Matthew 's other photos the camera seems
> to be struggling to get the light levels right when that EF 100mm f/2.8L
> Macro lens is used. Not sure why though since thats a pretty good lens
> camera combination. Perhaps if the WMF is going to insist on taking photos
> of people indoors under ambient light they should get him a EF 85 mm f/1.2L
> II.
> 
> -- 
> geni
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
  
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Approval of WCUG Greece as Wikimedia User Group

[John Andersson]

Congratulations WCUG! Looking forward working with all of you again in the 
future!

Best, 

John

- - - -



John Andersson



Wikimedia Sverige



Project Leader Europeana Awareness 







Phone: +46(0)73-3965189





Email: john.anders...@wikimedia.se




Skype: johnandersson86  

  

Be sure to follow us on Twitter at @wikieuropeana

Visit http://se.wikimedia.org/wiki/Projekt:Europeana_Awareness/English for more 
information about our
project!

Vill du stödja fri kunskap? Bli medlem i Wikimedia Sverige! / Would you like to 
support free knowledge? Please consider becoming a member of Wikimedia Sweden!


> From: bdamo...@gmail.com
> Date: Sat, 20 Jul 2013 16:08:21 +0200
> To: wikimedia-l@lists.wikimedia.org; wik...@lists.wikimedia.org
> Subject: [Wikimedia-l] Approval of WCUG Greece as Wikimedia User Group
> 
> Dear all,
> 
> I am happy to inform you that the Affiliations Committee has recognized a
> Wikimedia User Group today:  Wikimedia Community User Group Greece
> 
> Please give them a warm welcome, and keep your eyes on the cool Wikimedia
> activities taking place in Greece.
> 
> == WCUG Greece ==
> 
> WCUG Greece is a group of enthusiastic Greek Wikimedians  who are
> interested in organizing and participating in outreach activities on a
> national level. They have been active for the past two years already, doing
> among others workshops, presentations in free software events, educational
> partnerships, Mediawiki Geek Day 2013 and organized an edit-a-thon recently
> on el.wp as part of the World War I edit-a-thons.
> 
> The group is also working towards chapterhood in the future.
> 
> The Affiliations Committee's recognition is valid until 31 July 2014.
> 
> 
> 
> 
> Best regards,
> Bence Damokos
> Chair, Affiliatons Committee
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
  
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] article bytes more meaningful than users or revisions (was Re: Updates on VE data analysis)

[John Vandenberg]

On Sat, Jul 27, 2013 at 6:29 PM, Denny Vrandečić
 wrote:
> Thank you for the observation.
>
> Is the graph <http://i.imgur.com/TfaD99V.png> based on actual data? Because
> it looks just tad bit too linear to me. (I do not disagree with the
> finding, just wondering about the graph itself).
>
> I still would worry, though: our content is increasing linearly, as you
> say, but the number of active contributors is not. If we take for granted
> that active contributors are the ones who provide quality control for the
> articles, this means that since 2006 or so the ratio of content per
> contributor is linearly declining, which would mean that our quality would
> suffer.

There are a few parts of this that I dont think it can be taken for
granted, and I would love to see stats about quality rather than
quantity, as you're talking about quality, and that should be a
significant component of our analysis.

1) 'active contributors are the ones who provide quality control'

   bots do a lot of what used to be done by humans back in 2007,
rolling back most silly edits.
   and it is a small subset of active contributors who do the majority
of the maintenance.

2) the number of active contributors _doing quality control_ has declined.

   we know the number of overall editors is declining, and I think you
are right that those doing quality control is declining, but is there
evidence to support it?  And does it support that this decline is a
problem?

My gut feeling is that the decline in 'quality control' edits is
tightly linked to the increase in bots doing quality control.

i.e. do we have research to support total article-to-editor ratio
having a bearing on average quality of content?
A proxy could be average number of references per article ..?

It seems unlikely, as our content over the last five years has
increased in quality, and our number of editors has declined.

> I see two effects to counter that:
>
> 1) as you already mentioned, contributors are getting increasingly more
> experienced and more effective in fulfilling their tasks.
>
> 2) we continue to have a strong increase in readers and even stronger in
> pageviews (i.e. more and more people consult Wikipedia more and more). They
> probably also provide a layer of quality assurance, even though they might
> not qualify to be counted as active contributors.
>
> I have the gut feeling that 1) cannot be sufficient, and I would be curious
> in the effects of 2) - especially considering that much of the Foundation
> development work can be considered in improving 2 further (visual editor,
> article rating, mobile editing, etc.)

I agree with James that (1) is significant, and (2 - 'the future')
brings many unknowns with it.

(1) consists of our entire potential editor base, which includes of
all our currently active editors, and all of our inactive editors who
are able to resume editing at any time - i.e. not blocked, not ^&%ed
off, etc.  They all know the syntax, and have demonstrated their
commitment to the vision, _and_ the writers have a personal connection
to the articles that they worked on.  I see lots of them come back
occasionally to touch up or expand their work.

(2) brings different editors, for good or ill.  There are some
concerns in the community that simplifying editing will bring more
non-trivial vandalism that bots cant handle, and even more good
meaning editors who are discouraged when they can't understand why
their edit has disappeared, because they dont read the history, the
talk pages, etc, etc.  The ratio of experienced editor to newbie could
be a significant factor in the maintenance of a friendly environment.

More is not always better.

Don't get me wrong; a good VE will be very helpful, and the projects
defensive mechanisms will adapt.  But I predict that if we see lots of
poor quality articles from VE, without adequate references, and the
community backlogs become problematic, the community will want develop
tools to limit new poor quality articles.

Does anyone have stats for the number of blocked users per month over
the years, as that is hurting our potential editor base, and number of
reverts of edits by new users.

--
John Vandenberg

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] About the concentration of resources in SF (it was: "Communication plans for community engagement"

[John Vandenberg]

On Mon, Jul 29, 2013 at 1:36 PM, phoebe ayers  wrote:
> On Sun, Jul 28, 2013 at 8:05 PM, Daniel Mietchen <
> daniel.mietc...@googlemail.com> wrote:
>
>> I could imagine that certain types of bots, tools and gadgets would
>> benefit if handled and developed with support from a chapter.
>>
>> For instance,
>> http://en.wikipedia.org/wiki/User:Citation_bot
>> is used widely but cannot be maintained by its original author.
>> It is currently being ported to Labs (
>> https://github.com/wrought/citation-bot )
>> to restore functionality, but due to ongoing developments in other
>> areas (e.g. citation templates), adaptations are necessary on an
>> ongoing basis. Who should do that? And what about feature requests?
>>
>
> Yes! From a user perspective, that's definitely an area of need, and a
> great example too. Personal note: I LOVE Citation Bot, and I hope it comes
> back soon!

It appears to be operating

https://en.wikipedia.org/wiki/Special:Contributions/Citation_bot

So chapters can offer to help porting tools like this to Labs and
ongoing maintenance of these tools?
Is there a list of such tools that have been identified as needing paid support?

--
John Vandenberg

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] WMF's New Global South Strategy

[John Vandenberg]

'Global Strategy countries'?

I think this aligns with the intention of GS, which is to support
initiatives that help make our movement more global by investing in
areas/languages where editors and/or readers is low but potential is high.

John Vandenberg.
sent from Galaxy Note
On Aug 30, 2013 11:42 AM, "Balázs Viczián" 
wrote:

> What about making it simply global...?
>
> Balázs
> 2013.08.30. 2:44, "Asaf Bartov"  ezt írta:
>
> > On Thu, Aug 29, 2013 at 5:30 PM, MZMcBride  wrote:
> >
> > >
> > > The first section was removed? I got excited to see the term "Global
> > > South" with a line through it (in the agenda index), but I think I
> > > initially misunderstood its meaning.
> >
> >
> > No, the strikethrough was a visual cue that the _term_ "Global South" is
> > emphatically not on the agenda.
> >
> >
> > > The term "Global South" is pretty
> > > awful and deserves a quick death.
> >
> >
> > Agreed...
> >
> >
> > > But based on the title of the
> > > presentation and this e-mail thread... I'm not hopeful that it's dead
> > yet.
> > >
> >
> > ...but what do we replace it with?  This has been rehashed quite a bit,
> but
> > no one has come up with a compelling alternative that's reasonably
> concise
> > and is politically acceptable.  (Personally I am happy with "developing
> > world" and "developing nations", but of course those terms are
> euphemistic
> > as well, and apparently no longer acceptable in some circles.)
> >
> > I have stated before that the term, for us, is just shorthand for a list
> of
> > countries, and we make no essentialist assumptions about some uniformity
> > throughout all these countries.  It is my understanding that most of the
> > consternation (kittens dying etc.) the term causes is due to the
> assumption
> > that we _are_ making an essentialist assumption and treating all GS
> > countries the same.  I hope it is by now evident we are not.
> >
> > Once again, I find no point to debating this.  All who _are_ interested
> are
> > welcome to hash it out somewhere, and submit a consensual term (or a
> > shortlist) to WMF for consideration.  If a superior term arises, I
> promise
> > to make an effort to adopt it across WMF.  Until then, let's focus on the
> > actual work rather than the nomenclature.
> >
> >
> > > I'm a little confused about whether the ongoing programs in Brazil and
> > > India will continue. There's a note that reads "No WMF contractors on
> the
> > > ground any more", but it's unclear whether this means a discontinuation
> > of
> > > the current folks. And the final slides focus on future engagements.
> Does
> > > the "no contractors on the ground" line mean only full-time staff will
> be
> > > working with (engaging with, if you prefer) areas in the future?
> > Full-time
> > > staff and local chapter folks, I guess? And simply no Wikimedia
> > Foundation
> > > contractors?
> > >
> >
> > There are no WMF employees outside the US, so "no contractors on the
> > ground" (in the GS context -- we still have engineers around the world!)
> > means that (once the Brazil transition is complete -- this is in
> progress),
> > no program work in the GS will be done by WMF contractors, but only by
> > local partners (movement affiliates -- chapters, thematic organizations,
> > and user groups -- and unaffiliated partners), some of whom would be WMF
> > grantees.
> >
> > Cheers,
> >
> >A.
> > --
> > Asaf Bartov
> > Wikimedia Foundation <http://www.wikimediafoundation.org>
> >
> > Imagine a world in which every single human being can freely share in the
> > sum of all knowledge. Help us make it a reality!
> > https://donate.wikimedia.org
> > ___
> > Wikimedia-l mailing list
> > Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Wikimedia blog moving to WordPress.com

[John Vandenberg]

How much do we expect to be paying to Wordpress each year for this service?

John Vandenberg.
sent from Galaxy Note
On Sep 6, 2013 8:23 AM, "Erik Moeller"  wrote:

> On Thu, Sep 5, 2013 at 11:46 AM, Leslie Carr  wrote:
>
> > Currently the blog is in a partially maintained by Operations state.  In
> > ops, we have a few concerns - #1 is security (exemplified by our recent
> > security incident) of having a wordpress instance in our production
> > environment.  #2 is support of the blog from a technical standpoint.  We
> > are currently all oversubscribed with trying to keep the production sites
> > up and speedy.  The blog is low priority for us compared to the wiki's,
> and
> > therefore is often neglected.  When we hire about 5 more ops people, it
> may
> > be more sustainable, but right now, it's not - so it would actually be a
> > net positive for the Operations team to move the blog onto a dedicated
> > third party, and will also hopefully prevent any future security
> incidents.
>
> Exactly. Just because we have people who have no trouble maintaining a
> WordPress install doesn't mean we should. Time is always limited, and
> we have to prioritize. Working with a reputable third party that also
> drives development of the same open source software seems like a
> perfectly reasonable choice to me in this instance. And BTW - we do
> get situations where the blog gets a huge spike of traffic every once
> in a while, e.g. during the SOPA/PIPA protest, so hosting it ourselves
> is not as effortless as it may seem, without even accounting for
> customization requests from our communications team, etc.
>
> Erik
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Foundation
>
> ___
> Wikimedia-l mailing list
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>
___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] It's time to reclaim the community logo

[John Vandenberg]

Hi,

Further to our announcement on September 21, the opposition has been
formally filed before the European Union’s Office of Harmonization for
the Internal Market (OHIM) on September 25. You can read the
opposition filing in the documents section of the EU trademark
application[1].

Additionally, an opposition observation has been filed but it is not
yet available to the public at the URL mentioned above; our limited
understanding is that it will be published there in the coming days.
We’ll keep everyone informed on this aspect.

So what is next?

The OHIM will now review the Notice of Opposition to determine that
the opposition is admissible.  This takes a few weeks. If the notice
of opposition is found to be admissible, the 'cooling-off period'
commences.[2]

The 'cooling-off period' allows the parties can either negotiate an
agreement, and either party may withdraw their claim to the mark
without incurring additional costs. This period lasts between two
months and two years. It is important that everyone understands that
there is no need to act hastily. If the WMF and community need time to
find the right solution, we will have two years.

The WMF set the timetable by applying for this trademark, and they
have not withdrawn that application or responded appropriately to
community calls for this to be re-evaluated. The WMF was informed in
March that we viewed the trademark registration as unacceptable. Even
after our announcement on September 21, the WMF has not addressed the
heart of the issue; they have chosen to focus the community attention
on a new approach, a collective trademark, rather than consider the
erosion of the Commons by their trademarking of a public domain logo
against the intentions of the author of the logo.

Contrary to the WMF’s claims on their ‘Request for consultation’[3],
we have never said that the opposition needed to be filed on September
23. We are aware that we could have delayed the opposition until
December. As the opposition process is able to proceed through the
non-adversarial phase for two years, we believe it is appropriate that
a properly focused formal process should commence now.

During the first two months of the cooling-off period, we request that
the WMF provides a brief to the community explaining why they believe
they have a legal claim to the community logo, given that the board
knew it was selected in order that the community did not need to
request authorisation.[4]

We also encourage the WMF to publish their research on collective
trademarks, so that the community can make an informed decision about
the utility of this approach. It is our understanding that, in the EU
at least, the WMF will need to abandon their current trademark
registration if they are to apply for a collective trademark.

Regards,
John Vandenberg

== References ==
* [1] 
http://oami.europa.eu/CTMOnline/RequestManager/en_Detail_NoReg?deno=&idappli=1152038&transition=ResultsDetailed
* [2] http://oami.europa.eu/ows/rw/pages/CTM/regProcess/opposition.en.do
* [3] 
https://meta.wikimedia.org/wiki/Community_Logo/Request_for_consultation#Notes
* [4] 
https://lists.wikimedia.org/pipermail/foundation-l/2008-September/045702.html

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>