Re: [Wikimedia-l] Transition plans for WMF leadership

Pine W writes: > > I would hope that the Board is now planning an executive transition for > WMF. I would like to ask the Board to be transparent about this, including > making timely posts to this mailing list and proactively posting documents > and timelines on Meta and

Re: [Wikimedia-l] Collaboration team reprioritization

MZMcBride mzmcbride.com> writes: > > Forwarding this to wikimedia-l as it doesn't seem to be very technical in > nature, but definitely seems worthy of discussion. > > MZMcBride > > Danny Horn wrote: > >For a while now, the Collaboration team has been working on Flow, the > >structured

Re: [Wikimedia-l] Fundraising banners (again)

phoebe ayers phoebe.wiki@... writes: Hello! Sorry, I didn't realize that's what you were referring to. I haven't looked at all the raw fundraising data, no, and I haven't looked at that set that Lila refers to. (The reports we get are summaries, which is much preferable when you've got a

Re: [Wikimedia-l] Fundraising banners (again)

phoebe ayers phoebe.wiki@... writes: I just re-read this whole thread (!) this morning and here are the themes of points raised that I'm seeing ... I'll add this to the talk of https://meta.wikimedia.org/wiki/Fundraising_principles too. This is great. Thank you! Anything else I missed?

Re: [Wikimedia-l] Fundraising banners (again)

phoebe ayers phoebe.wiki@... writes: With Sam, I'd like to add my thanks to Lila, and to the fundraising team which has done an extraordinary job of testing, optimizing, and running our fundraising campaigns. And thanks to all of you, for being concerned about and invested in our projects'

Re: [Wikimedia-l] Fundraising banners (again)

phoebe ayers phoebe.wiki@... writes: You're asking me to prove a negative. My inability to do so has nothing to do with NDAs or the lack of them. There's no secret data that shows that well, the banners make people hate Wikipedia but they have a good donation rate. And if there was, why

Re: [Wikimedia-l] Fundraising banners (again)

Lila Tretikov lila@... writes: This type of fundraising is -- by its very nature -- obtrusive. We are thinking about other options. But, as with anything, every action has equal and opposite reaction. Anything we do, we have to consider the consequences and we will find flaws. Now for

Re: [Wikimedia-l] Fundraising banners (again)

Lila Tretikov lila@... writes: I would like to expose this more, maybe after this crunch. Just keep in mind that it takes time to anonymize and process -- a time that is otherwise spent on optimizing or collaborating. One bucket of resources, many demands... and I'd like to keep us as lean

Re: [Wikimedia-l] Fundraising banners (again)

svetlana svetlana@... writes: I wrote: it's usually both sides of the conversation at fault for accumulating their rage instead of communicating it early I unintentionally skipped a couple words. I meant to say: it's usually both sides of the conversation at fault, *such* *as* for

Re: [Wikimedia-l] Fundraising banners (again)

model (seriously, do a quick twitter search). - Ryan Lane ___ 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

Re: [Wikimedia-l] WaPo Wikipedia's 'complicated; relationship with net neutrality

sources of information. My biggest wonder here is: why in the world is the HR director for the foundation speaking with the press about this on behalf of the foundation (and the movement)? This seems like the kind of thing the communications department, or the ED (or DD) should be doing. - Ryan

Re: [Wikimedia-l] WaPo Wikipedia's 'complicated; relationship with net neutrality

Mark delirium@... writes: I don't see a distinction here, unless you're extremely naive about economics. Discriminatory pricing in any market can be done in two ways: 1. have a standard rate and add a surcharge to certain disfavored uses; or 2. have a standard rate and give a discount to

Re: [Wikimedia-l] WaPo Wikipedia's 'complicated; relationship with net neutrality

MZMcBride z at mzmcbride.com writes: Ryan Lane wrote: Kim Bruning kim at ... writes (roughly): Washington post article: http://wapo.st/1zUXNXj The response to this is embarrassing and lacking. Wikipedia Zero is an amazing program (and is one of the only excellent non

Re: [Wikimedia-l] Role and size of the Wikimedia Foundation and chapters

MZMcBride z at mzmcbride.com writes: Gerard Meijssen wrote: Do not be daft. The Wikimedia Foundation centralised its fundraising. It said that it would do a better job. Seen from a central periphery model, it probably does, However seen from the Netherlands it is rather silly., Pooh

Re: [Wikimedia-l] [Wikitech-l] Reasonator use in Wikipedias

On Tue, Jan 21, 2014 at 7:17 AM, Gerard Meijssen gerard.meijs...@gmail.comwrote: 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

[Wikimedia-l] Wikimedia labs-tools

On Wed, Sep 11, 2013 at 8:45 AM, Magnus Manske magnusman...@googlemail.comwrote: 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. Indeed. I don't want to get into the debate about this

[Wikimedia-l] Wikimedia labs-tools

On Wed, Sep 11, 2013 at 7:50 AM, John phoenixoverr...@gmail.com wrote: 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

Re: [Wikimedia-l] Disinformation regarding perfect forward secrecy for HTTPS

On Fri, Aug 2, 2013 at 7:23 PM, Anthony wikim...@inbox.org wrote: On Fri, Aug 2, 2013 at 10:07 PM, Anthony wikim...@inbox.org wrote: Anthony wrote: How much padding is already inherent in HTTPS? None, which is why Ryan's Google Maps fingerprinting example works. Citation

Re: [Wikimedia-l] NSA

On Thursday, August 1, 2013, Anthony wrote: On Thu, Aug 1, 2013 at 12:44 AM, Tim Starling tstarl...@wikimedia.orgjavascript:; wrote: On 01/08/13 14:15, Anthony wrote: On Wed, Jul 31, 2013 at 9:27 PM, Ryan Lane rl...@wikimedia.orgjavascript:; wrote: I would be fired and jailed

Re: [Wikimedia-l] Disinformation regarding perfect forward secrecy for HTTPS

: The stuff about 'have to transmit the session key I the clear' is completely bogus, of course. That's what Diffie-Hellman is all about. Ryan Lane tweeted yesterday: It's possible to determine what you've been viewing even with PFS. And no, padding won't help. And he wrote on today's Foundation blog

Re: [Wikimedia-l] Disinformation regarding perfect forward secrecy for HTTPS

On Thursday, August 1, 2013, James Salsman wrote: Ryan Lane wrote: ... Assuming traffic analysis can be used to determine your browsing habits as they are occurring (which is likely not terribly hard for Wikipedia) The Google Maps example you linked to works by building a huge database

Re: [Wikimedia-l] NSA

On Wed, Jul 31, 2013 at 1:00 PM, David Gerard dger...@gmail.com wrote: On 31 July 2013 21:00, David Gerard dger...@gmail.com wrote: On 31 July 2013 20:48, Risker risker...@gmail.com wrote: I believe the concern derives from one of the subpages of the article:

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

On Wed, Jul 24, 2013 at 12:02 PM, Steven Walling steven.wall...@gmail.comwrote: On Wed, Jul 24, 2013 at 11:37 AM, Federico Leva (Nemo) nemow...@gmail.comwrote: Anyway, being able to disband the SF office as regards software development (and perhaps more), and switch to remote work only,

Re: [Wikimedia-l] Use of YouTube videos in fundraising banners

A few clarifications inline. On Tue, Jul 16, 2013 at 10:09 PM, Victor Grigas vgri...@wikimedia.orgwrote: On the fundraising team we had used banners to host still images (.jpgs) in the past. We wanted to make a video we could put into banners but in July 2012 there was no open source HTML5