Re: [Wikimedia-l] Update on IPv6
On Sat, Jun 2, 2012 at 6:13 AM, Anthony wikim...@inbox.org wrote: On Sat, Jun 2, 2012 at 8:49 AM, Thomas Dalton thomas.dal...@gmail.com wrote: On 2 June 2012 13:44, Anthony wikim...@inbox.org wrote: On Fri, Jun 1, 2012 at 7:27 PM, John Du Hart compwhi...@gmail.com wrote: What personal information do you think is contained in an IPv6 address? Don't they sometimes contain MAC address information? I don't know, but I wouldn't consider my MAC address to be personal information... you might be able to work out what brand of computer I'm using, but I can live with that. I think that having a problem with the implementation of IPv6 is about 10 years too late now ;) The IPv4 space is being exhausted, and we're going to soon run into the opposite problem that IPv4 addresses will be not identifiable enough as ISP's use NAT. If someone cares about their mac address information, they can use privacy extensions - http://en.wikipedia.org/wiki/Ipv6#Privacy . Considering that in the vast, vast majority of the consumer (versus production) world, you have to purposefully enable IPv6 (usually with some sort of tunneling), and that these are turned on in most operating systems by default, mac addressing is starting to only become applicable in production environments. Leslie -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] No access to the Uzbek Wikipedia in Uzbekistan
I wish that http://208.80.154.225/wiki/Bosh_Sahifa and https://208.80.154.225/wiki/Bosh_Sahifa would work, too, but the foundation apparently can't or chooses not to afford separate IP addresses for each language's Wikipedia. As one of the network folks, I will answer this. We do not have enough public IP(v4)s for an address for each language in each project, and unless someone gives us a major donation of IPv4 addresses (anyone have a spare /20 laying around?), I don't think we will be able to make this happen as we are frugal with our existing IPs and the allocating authorities (RIPE and ARIN) are being quite strict with their new IPv4 allocations. If you'd like to read more about IP allocation policies, here's a few links https://www.arin.net/policy/nrpm.html#four3 https://www.arin.net/resources/request/ipv4_depletion.html https://www.ripe.net/ripe/docs/ripe-553 (see section 5.6) Leslie -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] No access to the Uzbek Wikipedia in Uzbekistan
On Thu, Dec 27, 2012 at 1:39 PM, Marco Fleckinger marco.fleckin...@wikipedia.at wrote: Leslie Carr lc...@wikimedia.org schrieb: I wish that http://208.80.154.225/wiki/Bosh_Sahifa and https://208.80.154.225/wiki/Bosh_Sahifa would work, too, but the foundation apparently can't or chooses not to afford separate IP addresses for each language's Wikipedia. As one of the network folks, I will answer this. We do not have enough public IP(v4)s for an address for each language in each project, and unless someone gives us a major donation of IPv4 addresses (anyone have a spare /20 laying around?), I don't think we will be able to make this happen as we are frugal with our existing IPs and the allocating authorities (RIPE and ARIN) are being quite strict with their new IPv4 allocations. If you'd like to read more about IP allocation policies, here's a few links https://www.arin.net/policy/nrpm.html#four3 https://www.arin.net/resources/request/ipv4_depletion.html https://www.ripe.net/ripe/docs/ripe-553 (see section 5.6) Just an idea, which is not very beautiful: What about a router forwarding ports to the correct machine by using iptables? Would that also work in connection with search engines? Are you suggesting we use different nonstandard ports for each different wiki/language combo that resides on the same IP ? Cheers Marco ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] No access to the Uzbek Wikipedia in Uzbekistan
On Thu, Dec 27, 2012 at 2:37 PM, Marco Fleckinger marco.fleckin...@wikipedia.at wrote: Leslie Carr lc...@wikimedia.org schrieb: On Thu, Dec 27, 2012 at 1:39 PM, Marco Fleckinger marco.fleckin...@wikipedia.at wrote: Just an idea, which is not very beautiful: What about a router forwarding ports to the correct machine by using iptables? Would that also work in connection with search engines? Are you suggesting we use different nonstandard ports for each different wiki/language combo that resides on the same IP ? Yes exactly! I guess that is theoretically possible with a more intrusive load balancer in the middle. We need the HOST information from the http header to be added as we have our varnish caches serving multiple services, not one(or more) per language/project combo. I'm pretty sure that lvs doesn't have this ability (which we use). Some large commercial load balancers have the ability to rewrite some headers, but that would be a pretty intensive operation (think lots of cpu needed, since it needs to terminate SSL and then rewrite headers) and would probably be expensive. If you have another way you think we can do this, I am all ears! We may want to move this discussion to wikitech-l as all the technical discussions probably bore most of the people on wikimedia-l Leslie ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] compromise?
On Fri, Dec 28, 2012 at 1:45 PM, James Salsman jsals...@gmail.com wrote: How about for the April fundraiser, instead of setting a dollar value goal, we agree to use multivariate analysis instead of A/B testing to optimize the messaging from volunteer submissions in advance, then run the whole thing for a fixed time frame, say three weeks, and then use the actual amount raised to decide whether salaries should be competitive with area tech firms, I've bit my tongue at this a bunch of times but I need to finally put my foot down. Which tech employees are saying that we need our salaries to be at Bay Area tech standards. Sure, I'd love a big raise (I'm greedy!). I took a pay cut to come work at the Foundation. However, I'm not starving, I'm not living in the ghetto with 20 people huddled into a single room, and most importantly, I knew what my salary was going to be when I joined the foundation. I knew that I wouldn't be getting bonuses, stock options, massages, breakfast, lunch, dinner, baristas, onsite personal trainers, onsite physical therapists, haircuts, dentists, business class everywhere (that might have been the hardest thing to give up!), nutritionists, aeron chairs, dry cleaning, laundry, and all that. And you know what -- if I did get those things, I have a feeling that it wouldn't look too good to our donors, and we'd be having the exact opposite discussion. Plus, I can make my own coffee. How do we even know that salary is a factor in people voluntarily leaving? Has it been established in exit interviews? If I felt strongly about salary, I wouldnt have a problem speaking up, but please don't put words in my mouth. Leslie whether Fellowships should be jettisoned, how much personell to put into the Education Program and engineering, and how much of a reserve to invest, preferably with low risk instruments which pay above the rate of inflation? ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] compromise?
On Wed, Jan 2, 2013 at 2:50 PM, cyrano cyrano.faw...@gmail.com wrote: Le 02/01/2013 18:42, Oliver Keyes a écrit : On 2 January 2013 19:25, cyrano cyrano.faw...@gmail.com wrote: You're comparing your standard of living with extreme ways of life, and you reach the conclusion that yours is moderate. However, if you compare with the rest of mankind, you're still getting things that 99% of them don't get. I think that's probably true, but the fact of the matter is that Leslie is not saying here is an extremity, I get less - she's saying here is an extremity that is Standard Operating Procedure at Facebook/Google/Twitter//insertyourorgofchoice, where almost any of us could get a job...I get less. In the context of a conversation comparing WMF benefits with those of similar orgs in the Bay Area that makes total sense as a statement. I would agree that it is better than 99 percent of humanity, but I'm not sure who *dis*agrees with that statement: you appear to be arguing against a position that hasn't been made. I'm proud of people like Leslie who work for less money than other opportunities but for a cause. They stand for their beliefs and their values, I strongly respect that. Yet the money of the donations, which is given for a universal cause, is paying an incredibly tiny subset of humanity with very expensive standards of life. I think that's something pertinent to consider given the topic. I think you missed my point. I was saying that we don't need those things and it would be irresponsible of us to try to keep up with the average Tech company, as James Salsman had suggested. Leslie ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Editor retention (was Re: Big data benefits and limitations (relevance: WMF editor engagement, fundraising, and HR practices))
On Tue, Jan 8, 2013 at 7:06 AM, Federico Leva (Nemo) nemow...@gmail.com wrote: Nikola Smolenski, 08/01/2013 13:10: In general, as far as we know captchas are currently not stopping spammers at all, while effectively stopping many legitimate (less Care to elaborate? Do we know how are spammers avoiding captchas (by software or by humans)? How come other websites don't have this problem? Are you kidding? All MediaWiki websites suffer from the uselessness of its captchas. For additional information please refer to the discussions linked from https://www.mediawiki.org/wiki/Requests_for_comment/CAPTCHA and others on wikitech-l. It's the worst kept secret in the world that you can hire people to decode your captchas -- http://decaptcha.biz/ for example. Better captchas don't work because you are competing against people and if people can't solve the captcha ... In my experience, some sort of easy captchas do prevent the lowest/stupidest level of spammer (you have to have enough knowledge to integrate an api into your spamming program) Also for major spammers, it's so easy to get a large block of phone numbers in the US (a DID) - but again that does raise the bar a second time for spammers. In my opinion a phone auth may also be raising the bar too high for some users, and you have to balance that risk. I think that technical solutions may be a better call for this (some sort of spam ranking system) Nemo ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] fiction: WMF policy of paying less than market
On Fri, Mar 8, 2013 at 12:17 AM, Peter Gervai grin...@gmail.com wrote: On Thu, Mar 7, 2013 at 7:43 PM, Leslie Carr lc...@wikimedia.org wrote: Though I do feel that the WMF salary is discriminating against my right to fly first class everywhere. My champagne glass won't refill itself, you know! Do you accept donations? Cash, paypal, and of course bottles of champagne ;) g ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] fiction: WMF policy of paying less than market
Though I do feel that the WMF salary is discriminating against my right to fly first class everywhere. My champagne glass won't refill itself, you know! Turns out, I was wrong!! https://commons.wikimedia.org/wiki/File:Mumm_Napa_and_Glasses_2013-03-08.jpg https://commons.wikimedia.org/wiki/File:WMF_Staffers_drinking_Champagne_3.jpg https://commons.wikimedia.org/wiki/File:WMF_Staffers_Drinking_Champagne_2013-03-08.jpg https://commons.wikimedia.org/wiki/File:Sue_and_WMF_Staffers_drinking_champagne_2013-03-08.jpg https://commons.wikimedia.org/wiki/File:Sue_with_Champagne_bottle_2013-03-08.jpg Thanks to a generous anonymous benefactor :) -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Lack of community involvement in WMF budget planning
On Tue, Apr 23, 2013 at 2:26 AM, Tomasz W. Kozlowski tom...@twkozlowski.net wrote: Hi Sam, first of all, let me thank you for your involvement in this—it's appreciated! Other comments follow in-line. By the time we see a final-draft plan in April/May, there is already little leeway for significant change. This probably means that there is something wrong with the process and the timing; we all know that getting community feedback (and replying to it) is a lengthy procedure, so I guess we should start it much earlier next time, probably around the New Year. Gah! As someone who works for the foundation and has had to deal with budget issues in engineering (though this is my personal opinion) the budget process is already incredibly long, drawn out, and stressful. If I had to start the planning in November to get a draft out by Jan 1, then keep revising it until May... not only would that take up a large amount of staff time, it'd also cause a stressful process to be even more stressful. Wouldn't it be better if, say, a draft of the budget and plan is submitted for community feedback, and only then brought up at a Board meeting so that the Board can include community feedback, too? -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] The case for supporting open source machine translation
(FYI this is me speaking with my personal hat on, none of these opinions are official in any way or the opinions of the foundation as an organization) personal_hat While Wikimedia is still only a medium-sized organization, it is not poor. With more than 1M donors supporting our mission and a cash position of $40M, we do now have a greater ability to make strategic investments that further our mission, as communicated to our donors. That's a serious level of trust and not to be taken lightly, either by irresponsibly spending, or by ignoring our ability to do good. Could open source MT be such a strategic investment? I don't know, but I'd like to at least raise the question. I think the alternative will be, for the foreseeable future, to accept that this piece of technology will be proprietary, and to rely on goodwill for any integration that concerns Wikimedia. Not the worst outcome, but also not the best one. I think that while supporting open source machine translation is an awesome goal, it is out of scope of our budget and the engineering budget could be better spent elsewhere, such as with completing existing tools that are in development, but not deployed/optimized/etc. I think that putting a bunch of money into possibilities isn't the right thing to do when we have a lot of projects that need to be finished and deployed yesterday. Maybe once there's a closer actual project we could support them with text streams, decommissioned machines, and maybe money, but only after it's a pretty sure investment /personal_hat Leslie Are there open source MT efforts that are close enough to merit scrutiny? In order to be able to provide high quality result, you would need not only a motivated, well-intentioned group of people, but some of the smartest people in the field working on it. I doubt we could more than kickstart an effort, but perhaps financial backing at significant scale could at least help a non-profit, open source effort to develop enough critical mass to go somewhere. All best, Erik [1] http://stats.wikimedia.org/wikimedia/animations/growth/AnimationProjectsGrowthWp.html [2] https://developers.google.com/translate/v2/pricing -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Wikipedia and our other projects reach more than 500 million people every month. The world population is estimated to be 7 billion. Still a long way to go. Support us. Join us. Share: https://wikimediafoundation.org/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Go away, community (from WMF wiki at least)
Sent from my mobile. Please excuse the brevity and typos. On May 11, 2013 4:36 PM, MZMcBride z...@mzmcbride.com wrote: Deryck Chan wrote: Given the foundation's recent tsunami of centralisation I'm not surprised by this at all. The message is clear - the community doesn't belong here. Go back to meta. Yeah, I think you're right. It seems to be part of a larger pattern. * Blog access has been restricted (as noted). * Bugzilla adminship has been restricted to staff only. * wikimediafoundation.org adminship is now restricted to staff and Board Members. * Shell access has been restricted to staff only (no more volunteer sysadmins). Someone better tell that to domas and his ssh key. As someone tasked with protecting the servers,ssh keys should be restricted as much as possible, both with staff and volunteers. that is technical and not political. Relatedly, the Toolserver is being slowly killed in favor of a controlled sandbox called Wikimedia Labs and all Wikimedia accounts are being unified (with forceable usurps/renames) to make it easier to track and control users across all Wikimedia wikis. It's very surprising that the Board has been so quiet about all of this. Generally, a few staff members (notably Philippe and his team) have tried to create tiers in which paid staff are above volunteers. Even the most trusted volunteers are no longer allowed to hold positions of trust within the Wikimedia community. This is very bad. Are there ways to address this? But to blame this on Gayle is kind of insane. It seems clear to me that she's being used as a pawn here. There are very few indications that this has anything to do with her, aside from a few log entries (from... Philippe) inexplicably pointing to her name. And the curt e-mail she sent out to affected users. Her involvement with the wiki would charitably be described as negligible. The director of _community advocacy_ (Philippe) is stripping nearly every community member of user rights. And yet there's still no provided rationale for the change in policy, other than it being based on a series of private discussions. Meanwhile, the home page of wikimediafoundation.org stresses how transparent the organization is. This is a pretty disappointing day. I'd be interested to hear what Gayle, Philippe, or the Board has to say. MZMcBride ___ 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] Go away, community (from WMF wiki at least)
On Sat, May 11, 2013 at 4:59 PM, K. Peachey p858sn...@gmail.com wrote: On Sun, May 12, 2013 at 12:56 AM, Leslie Carr lc...@wikimedia.org wrote: ... As someone tasked with protecting the servers,ssh keys should be restricted as much as possible, both with staff and volunteers. that is technical and not political. That same argument can also be used for restricting all but even a smaller circle of staff from root. Probably not the best example to lead with... Actually it is the perfect example to lead with -- very few people with shell access have root. -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Go away, community (from WMF wiki at least)
On Sat, May 11, 2013 at 5:04 PM, MZMcBride z...@mzmcbride.com wrote: Leslie Carr wrote: * Shell access has been restricted to staff only (no more volunteer sysadmins). Someone better tell that to domas and his ssh key. As someone tasked with protecting the servers, ssh keys should be restricted as much as possible, both with staff and volunteers. that is technical and not political. That was just sloppy wording on my part, apologies. Shell/root access has been indeed been restricted to staff only. About four users have been grandfathered in (Domas, Jens, River, Robert S.). I'll note that these users have all contributed an enormous amount (for free!) to the Wikimedia movement. They deserve only our appreciation for the volunteer work they've done. And they serve as a model of what trusted volunteers can do. Please don't suggest that this has anything to do with technical decisions. Even a child can see that this is pure politics. Leslie, do you agree with these policies that remove all non-staff from positions of trust? Do you agree with creating tiers between staff and everyone else? I have no opinion on all the other policies - my concern, expertise, and really the only place I think my opinion even matters is for the servers. My opinion is that we should restrict any ssh access on the cluster to those who have demonstrated that they both need it and can handle the responsibility. If a volunteer has been very responsible in labs and has a demonstratable need, I'd be fine with that. The reason that ops staff get ssh access and root is that we (hopefully) during our interview and references have demonstrated the ability to handle the access responsibly, have a need, and on top of that have signed a big stack of paperwork. But the more that we can do on labs without ever touching production, the better off the stability of the cluster. Also I believe that several analytics folks ( under admins::restricted in admins.pp ) are not employees but do have some ssh access. Leslie MZMcBride ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Re: [Wikimedia-l] Fwd: [Wikimania-l] git.wikimedia.org dead due to wikimania ; )
http://status.wikimedia.org is from external monitors Sent from my mobile. Please excuse the brevity and typos. On Aug 14, 2013 4:44 AM, Federico Leva (Nemo) nemow...@gmail.com wrote: Chris McKenna, 14/08/2013 00:00: On Tue, 13 Aug 2013, Oliver Keyes wrote: I'd like to think Engineering do a pretty good job at uptime for core services - when was the last time you saw Wikipedia down for any extended period of time? - regardless of what day of the week it is. Wikipedia uptime is certianly much better these days than it was around 2005/6 when there were at least two websites dedicated to reporting its status. Back then it wasn't uncommon to experience major slowdowns, periods of non-responsiveness, extended read only periods and edits failing (sometimes silently) due to (iirc) overloaded servers. I can't remember the last time I saw anything like that, but it certainly wasn't 2013. Btw it would be nice to have stats on uptime, or at least some assessment of the progress for the stabilizing infrastructure 5 years strategic goal. I couldn't find any recently, I asked both on mailing lists and on Meta. https://meta.wikimedia.org/**wiki/Talk:Wikimedia_budget#** Stabilizing_the_infrastructurehttps://meta.wikimedia.org/wiki/Talk:Wikimedia_budget#Stabilizing_the_infrastructure ** Nemo __**_ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.**org Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/**mailman/listinfo/wikimedia-lhttps://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@**lists.wikimedia.orgwikimedia-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
a WordPress installation would be well within the WMF's capabilities. Neil __**_ Wikimedia-l mailing list Wikimedia-l@lists.wikimedia.**org Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/**mailman/listinfo/wikimedia-l https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@**lists.wikimedia.org 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 ___ 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 -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ 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] Dells are backdored
On Sun, Dec 29, 2013 at 5:17 AM, geni geni...@gmail.com wrote: On 29 December 2013 12:55, James Salsman jsals...@gmail.com wrote: Can we please stop paying the Microsoft and NSA taxes The WMF doesn't. and start buying datacenter equipment which costs a lot less? Cubieboard/Cubietrucks for instance? Ref.: http://www.spiegel.de/international/world/catalog-reveals-nsa-has-back-doors-for-numerous-devices-a-940994.html Best regards, James Using non standard data center equipment is a great way to add costs. Naw, it's a great idea. Let's switch to building our own ARM-based servers (by the way, which have already been a flop commercially), using only unproven, low-volume available motherboards and having to buy and assemble all of the rest of the components. And then of course, we need to design our own cases... and since these have such a low performance, we'll need to have a lot more rack and datacenter space, of course which comes with a cost... and we'll have to figure out how to run our caching layers which require large amounts of memory... and our storage layers which require large amounts of disk space. At that point we'll probably need to redesign those boards which are incapable of doing these things, so we'll need a team of hardware engineers, plus a deal with a manufacturing plant. So... I think with about a 100 million dollar per year research budget we can do this. Who's ponying up? ;) As for security given the limited resources the WMF has whenever GCHQ, FSB and MSS have wanted to get in they have and there is nothing we can do about this. ___ 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 -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ 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] Dells are backdored
Oh man --- The trolling here is amazing!!! First off, you can't just plug a fiber cable into an ethernet socket. You need at least SFP+'s for 10G fiber connections, plus the cost of fiber itself -- it's way more expensive than a 100mbit connection. That said, we do use SFP+ based 10G for our varnish layer -- the amount of traffic pushed by those boxes compared to the amount it would cost to buy a bunch of additional machines makes the extra cost of the interfaces (and don't forget the switch ports! 10G switches cost more than 100mbit switches) make perfect financial sense. Leslie PS - someone technical may point out that DAC (which is copper! gasp!) is cheaper than two SFP+'s and a fiber cable. That's true! However we have had major issues with DAC compatibility on the switch side, and some issues on the hardware side. SFP+'s rarely (albeit occasionally) have that issue. Plus we can keep a spare inventory that is usable in multiple places, making our sparing easier and life easier on the DC techs when we need to scramble for an unexpected 10G need. On Sun, Dec 29, 2013 at 10:10 PM, James Salsman jsals...@gmail.com wrote: Maximum 100 Mbps ethernet connection We should be using fiber, which also costs less power and is orders of magnitude faster. If the words enterprise-class actually mean something more than much larger markup than purchasing components then go with something like http://www.marvell.com/company/news/pressDetail.do?releaseID=3576 For example, maybe the http://www.mitac.com/business/gfx_servers.html people have benchmarks representative of our DB/cache usage patterns. It's not like we have anything special (or x86-specific, Jasper!) other than very high bandwidth. At least put out an RFP, please. ___ 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 -- Leslie Carr Wikimedia Foundation AS 14907, 43821 http://as14907.peeringdb.com/ ___ 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
