I stopped donating because of this - definitely want to contribute to keeping Wikipedia online, I don’t necessarily want to give my money to a larger foundation running all kinds of other projects and wielding that cash as a political tool.

[0] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_salarie...

Chief Community Officer

Chief Talent and Culture Officer

Chargée d'affaires

Chief Global Development Officer

Chief Creative Officer

Chief Communications Officer

Chief Revenue Officer

VP of Strategic Partnerships

55 million USD in annual salary expenses seems a bit high, even more so for a non-profit. I have seen startup unicorns spend less on salaries. I think there really needs to be some scrutiny into how funding is being spent.

Looking at the list of execs there I really have to question what role they play and how their compensation is justified. It's not just their individual salary either. At their level they have entire organizational hierarchies working under them and the collective salaries can add up. What precisely are they contributing to the movement?

I can't imagine the kind of things Wikipedia needs to do that needs such roles. These guys should be focusing on product and tech primarily. They have a solid product which hasn't changed in years and a strong brand. They have a singularly unique and special thing in this world and need to protect it as sacred. They need to focus on maintaining and scaling this system for eternity instead of experimenting and branching offshoots into community engagement, strategic partnerships, ambassadoring and all that crap.

Sure, some of these positions sound a bit surprising. But, having checked just the last one, it existed only for a part of 2016. So, eh, what's your point again?

Obviously there’s a debate to be had about what and how much Wikipedia should engage in other ventures but even for their core work a lot of these roles seem pretty reasonable...

The ones that made it through were specifically the ones that embraced and prepared for change, by running parallel long-shot projects and branched out from doing whatever they were doing before.

However, this seems like excessive marketing for an organization that does not produce a physical product (unlike Funk & Wagnal's).

I have seen less online criticism of WikiPedia accuracy of late; perhaps this is the result of the marketing dollars. If true, it is good, but it could likely be done with marketing efforts a fraction of the size.

I understand that it isn't much for an executive, but then that stuns me even more.

Edit: median US salary is around $70k. This executive's pay is over 5x median income. Those who say it's not a lot are disconnected from the way that most people in the country and the world live.

I don't understand anything about US IT salaries anymore.

In reality, the number of developers making $500K is relatively small. Even in California, the median developer compensation is a fraction of that. FAANG companies can have admission rates that are more selective than Ivy League universities, and they don’t even hire in most cities in the US.

This causes a lot of compensation confusion and anxiety for young people who grow up reading HN comments and snarky Reddit posts when their first job offers don’t come anywhere near the $300K to $500K range that they read about online. It also causes a lot of grief for developers who think they’re overworked and underpaid because it seems like everyone on HN casually acts like $500K is the going rate for being able to spin up a React project.

Are they really that talented, or are they just good at whiteboarding algorithm questions that they almost never actually use on the job?

These companies that spend $300K or more on their developers aren’t keen on keeping under-performers around, either.

The idea that you can bluff your way into a FAANG job by memorizing enough LeetCode problems yet by somehow remaining an under qualified programmer is a myth.

I've heard this comparison before, but I'm not sure how meaningful it is because the Ivies charge an application fee. There isn't much cost to applying to FAANG and hoping for the best.

They're too high, though not high enough.

We've become the new priesthood. People who complain that sacrificing one calf to us each year would do well to be reminded that we're not demanding one child per year.

I am from Brazil, mentioned in the article. I see wages of 60k USD year as a dream job (by the way, if you need a C or Lua dev, and don't want me to relocate to an expensive place to live, I am for hire, for that price tag, I really need it. I currently make around 11k USD year)

I do think that the sky high salaries are ridiculous compared to societal contributions of, say, a nurse or a teacher. But I also like very much that I get them for doing a job that I still do with a small on my face.

I got into this line of work because it's fun. It's still fun. If I didn't get paid I'd do it for free, although "it" would be lime green hobby projects rather than the productive and tasteful work people employ me to do.

Personally I recently quit my high paying industry job and moved to an engineering heavy PhD position (HPC), because I enjoy solving complex problems.

Huh, this is interesting, maybe in some areas of America? But broadly speaking... Outside of America, no. Take a look at even senior dev salaries in Canada.

They're equivalent to master's of social work positions, oftentimes less. Having had education and work experience in both social work and computer science, I can tell you that if you want a stable, low-stress job that requires an "easy" degree, that MSW degree will serve you far better.

Not to mention that remote work is still rare. So that 90k senior AI research job, requiring a Phd at the Autodesk office in Toronto is... not great. Most computer scientists I know are happy with being middle class and just really enjoy the subject matter. Maybe this is rare in your area of the world?

Of course, this only makes your point even stronger.

[1] https://www.bls.gov/news.release/pdf/wkyeng.pdf

I am a software engineer who used to live in the Bay Area but now live in Europe. In my country, my family is living off of a salary of 30000 (Euros, or about 36k USD). (This is my wife's salary, I'm not currently working). Our income officially puts us below the poverty line, so we pay 0% in income taxes.

With this 30k, about 50% goes to housing, about 1/6 goes to special needs schooling for one of my two children (they both need it, but the younger one's school is currently free), and the remaining 1/3 is for food and bills and misc. expenses.

We own a small, fuel efficient car that my wife drives while I bike or take public transportation. Our entire apartment runs on an average of 250W (servers, laptops, cell phones, electric stove) because everything is energy efficient. (LED lighting, double-pane windows, good applicances) We pay 10 euros a month for gigabit internet, 200+ channels, and unlimited calling to 150+ countries.

We live comfortably in a large (100 m^2) four bedroom apartment in a safe neighborhood (working class, but nice). We eat well, we can afford to go to restaurants occasionally, and even take the occasional vacation.

While we're not currently saving any money, because we have money saved up, we're not living hand to mouth, even though "technically" we are.

If we wanted to return to San Francisco, the budget would look something like this:

    * 60k Schooling for both kids
    * 60k Four bedroom apartment or split home
    * 30k Food, car, bills

I live in Canada. I earn much less than USD $375K/yr. But can we agree that I am very connected with how people live in other parts of the world?

Good. Now let me tell you that were my employer to ask me to move my family to the US, ANYWHERE in the US, I would want way more than $375,000/yr to duplicate the lifestyle we have now.

That’s just how it works when you move from a place with a safety net to one where losing your job could mean certain death.

And in my family’s case, I am not exaggerating: My partner is a cancer survivor. What would we have done if we were living in the US? Hire lawyers to fight with insurance companies for her treatment? What if I was laid off and lost my benefits right when she was diagnosed?

SHUDDER.

Were I to live in the US, I would want to be stinking, immorally rich. It’s the only way to insure yourself against disaster.

She'd go on Medicaid. Anyway, quit watching so much TV. It's just propaganda.

But I don’t watch TV. I do things like read HN. Where I recall an essay on the front page a few years back where a wealthy tech founder cashed out and then tried to buy health insurance for their family.

Despite being wealthy, they reported that basically, it was impossible to get insurance that met their needs. They did not say “no problem, the whole family got medicaid.”

Now tell me: How many people in the US had medical bankruptcies last year? How about the year before? Or the year before that?

I’ll let you tell me, since you believe that I only watch propaganda on television, and you believe you have all the answers. What are these medical bankruptcies, if medicaid solves all problems?

Is all this propaganda spread by smug Canadians to boost immigration? I think not, but if you’re prepared to cite some numbers showing that nobody ever loses their home because of cancer or some other major health problem, I’ll gladly read what you share.

Even if they were paid ten times less (or a hundred times less, for execs making millions per year), there'd be lines of people a mile long willing to take their place, and probably do their job just as well if not even better.

Corporate boards and investors are deluding themselves that they need to pay astronomical rates to get people who can do these jobs.

It won't seem so sky-high once your universe also has $4k per month one-bedroom apartments and $2M single-family homes.

Why do they deserve that much compensation exactly?

The people who to my mind deserve high compensation are people who are risking their lives to help people, such as firefighters (who are often sadly volunteers and don't get paid anything), front line nurses and doctors, teachers in inner city schools or third world countries, Peace Corps volunteers, etc.

People whose job it is to hobnob with other high-paid execs over expensive lunches and give orders should be at the bottom of the pay ladder, not at the top.

Edit: I think that Salaries are for Top Executive only. There are 450 [1] in Wikimedia. In the case 55M isn't that much.

[1] https://wikimediafoundation.org/role/staff-contractors/

A sense of purpose alone won't let you lodge in cities with high cost of living.

If anything, I dare say running a non-profit usually requires a lot more skills, especially people skills and passion than a tech job.

I'm not sure how it is in the US but in Europe there is this sense of entitlement when you talk to people that because you work at a non-profit you should work for free. If I give my valuable time to contribute to the world at large, I expect to be able to have decent living conditions.

Oh come on! What talent do they need that a million much lower paid people don't have?

Same line used in defense of corporate board hiring practices, and as in that case, stated without evidence to support the claim.

100k was maybe "sky high" 20 years ago. 100k in most large cities is not. When your modest house costs $800k USD, a car costs 30k, auto insurance is $1600 a year, groceries are 10k a year (looking at you, Toronto), just how in the hell is 100k "sky high"?

$80k was a decent salary in a mid-size city 15 years ago.

Just because six figures seems like a lot of money to you doesn't mean it's a lot of money.

Upper class income only seem lackluster compared to the perverse 0.1% incomes and the housing bubble.

You know how many people live in Iowa?

I'm also a Principal SWE and my salary is well below $200k, though there are years with bonuses, etc.. that I reach $200k

Wikimedia is a global foundation, so they don't have to live in the US even.

They could have easily hired someone from a country with a much lower cost of living.

/s

If Wikipedia(1) is semi-accurate, no (ZERO) major European county surpasses this. Not even Switzerland which clocks in at 70k EUR. And that's average, the mean is even lower due to skew by those making top money.

(1) https://en.wikipedia.org/wiki/List_of_European_countries_by_...

And slap 20-25% VAT on top.

That money is really not that much, a generalist MD would make that for eg.

To be considered sky high in my book you need to be actually rich - able to afford luxuries such as own a luxury home, driving a premium car, be able to rent a yacht for a vacation - you need to be making >150k for your income to be noteworthy, otherwise you're just doing well off - higher middle class.

Sorry but there's nothing sky high about earning 80k EUR per year and living in London, Zurich, Oslo, Amsterdam, Munich, etc. you barely stand out, especially if you socialise with other college educated workers, you're probably the norm or below it for career people.

[1]: https://www.iwkoeln.de/fileadmin/user_upload/HTML/2019/einko...

PS: Data is for Germany.

> Also from the diagram, 75% of the population are earning less than 10,400 EUR while 25% are earning more than 10,400 EUR.

If 25% of the city is making more money than you you are not rich by any definition.

I have friends living in Munich, friend is a SW engineer, makes 75k, his wife has her own business so I'm not sure how much she makes, they are very much middle class lifestyle and can't afford to live in the wealthy areas.

Sorry to burst your bubble but you're not rich if you make 80k/year, you're just (maybe upper) middle class, even in EU.

[1] http://www.salaryexplorer.com/salary-survey.php?loc=982&loct....

Edit: Also it's completely unclear to me how this point relates to your initial gross misrepresentation of compensation in western Europe.

OP suggested that 100k$/year not being noteworthy is a uniquely SV/US thing - it is not. Any place worth living in Europe will take that much to live comfortably (note. 100k USD = 80k EUR)

Upper middle class maybe. People in the upper class don't need to work.

[0] https://www.iwkoeln.de/en.html

Sky high is at least top 1%. Maybe top 5% in high income areas.

In Eastern Europe you begin to approach this at 80k.

But rent is getting crazy here, a 60 sqm apartment will cost you 1300+ utility.

For example here [1] you can see some reliable statistics for France, see page 2 (it's in French but the plots are easy to understand). The median salary (annual before taxes) when starting is 35k€, and roughly increases by 1800€/year. So it only reaches 40k€ after 3 years. It reaches 50k€ after 8 years only.

Also all engineers have Masters in continental Europe. You can't be an engineer without one. It's nothing special.

[1] https://www.iesf.fr/offres/doc_inline_src/752/IESF_Synthese_...

But Italy and Spain aren't really what I would consider Western Europe, they are the less developed parts and I admit I have no experience with France and know nobody who works there.

Yeah, well, you're American, right?

You really are living up to it in many ways.

That is the figure for "programmers and software development professionals", anyway.

How did you get these costs? You can get a French Chateau with that much money. https://www.prestigeproperty.co.uk/french-chateau-for-sale-2...

I paid $340k for this house 13 years ago. I thought that was far too expensive but I didn't have a choice.

I would guess that they co-evolved in a vicious cycle of inflation. But I know very little of economics.

At entry level you typically manage a two-pizzas sized team in one fairly limited domain. "Have this desk and a bunch of people, figure out how to run a worldwide wiki" would be a typical senior manager/director assignment (a.k.a. middle management).

If we set aside an argument about IT salaries fairness, I think people at Wikimedia deserve some thanks for taking a salary cut to undeniably make a difference on the world.

I guess there's a chance that executive compensation went up significantly after 2018, but nothing I saw looks out of place for an organization as large as Wikipedia. ~300k for a San Fransisco-based CEO and an average salary of ~120k for all employees employees seems fairly reasonable to me.

The annual real median personal income in the US in 2019 was $35,977[0], how can anyone think that $120k isn't a lot? Why should people around the world donate their hard earned money so that some employees in America can have Silicon Valley salaries?

[0] https://en.wikipedia.org/wiki/Personal_income_in_the_United_...

wikipedia SHOULD be paying competitve salaries so that their best and brightest don't leave to join tire-fire companies like Facebook. I don't know why you think someone working at Wikipedia shouldn't be paid a competitive salary if they work there; if not they will go work for Facebook and the world slowly loses out on an incredible resource while companies like FB get stronger because of misaligned thinking.

You are disparaging a CEO for making 350k/year for one of the highest trafficked sites in the world. For perspective, Zuckerberg's net worth places him at an effective salary of 3B/year (his current net worth divided by his age), nearly 10,000x of the guy you are saying is getting paid too much and potentially driving employees away from.

If your problem is the median personal income you don't solve that by trying to reduce the CEO of wikipedia's salary. Focus on that - it's your kind of attitude (why should a burger flipper get paid $15/hr) that is actually suppressing wages in this country.

This is a good question. Why shouldn't Wikipedia hire developers from 3rd world countries? It sure shows donation banners there. And there isn't anything magical about US developers and anything special about building sites for millions of people. Expertise is there, often used by US companies, salaries are not.

> You are disparaging a CEO for making 350k/year for one of the highest trafficked sites in the world

The root of the question is: what determines compensation at companies? FAANG and SV startups are able to offer huge salaries not because they are "the highest trafficked sites in the world". It's because they rake in billions of dollars in revenue, by monetizing their users, and/or because they are VC-funded. If that wasn't the case, their employees' -- and certainly their executives' -- salaries would not be this high.

When your company makes billions of dollars a year, and you can make the case to your board that you can increase or maintain that number, that's when your salary becomes high -- when the tradeoff to shareholder value between paying you a lot of money and the company making a lot of money tips your way. You don't just automatically get a high salary for running (or working in) a large company, if that company does not make this much money.

The WMF is a nonprofit. It does not make any money aside from donations. When running its donation campaigns, it does so from the perspective of keeping internet knowledge alive, rather than saying "we think it's important to keep ourselves in the top 10% worldwide salary bracket". It's absoluetly fair to say that they need to raise a certain amount of money in order to keep the foundation going, and in order to maintain and develop it. But saying that it's "insane" to argue that a nonprofit should not be able to compete against a multi-billion dollar organization salary-wise is... strange?

Most of the world's companies, startups or otherwise, in fact can't afford SV salaries, and so they look elsewhere -- there are many, many great developers, executives, and other folks around the world (and in the US, outside of SV) who work for less than FAANG salaries. This doesn't meant they aren't well-compensated, it just means that maybe they don't live in SV, and that yes, it's possible that FAANG will poach some of them. That's just something you have to live with when you don't make infinite amounts of money, like 99% of the world's companies.

> For perspective, Zuckerberg's net worth places him at an effective salary of 3B/year ...

For perspective, Facebook's revenue was about $85B last year. Using the world's fifth-richest person, who heads a fortune 150 company that is the F in the only five-lettered FAANG acronym that's frequently used as the barometer for high salaries, "for perspective", is also strange. The only perspective that Zuckerberg's salary offers is "what does the top 0.1% of the top 0.1% make?"

> it's your kind of attitude (why should a burger flipper get paid $15/hr) that is actually suppressing wages in this country

It's disingenuous at best to connect a nonprofit's executive staff making large salaries with raising the minimum wage. In fact, that's precisely the discrepancy that is making folks talk about the salaries at WMF: the foundation is soliciting donations from the folks making $15/h in order to pay its CEO $300k+ a year.

So let's say I start a company selling cars. I decide to sell my cars for $1. It's a terrible business model, and I don't make much money. So according to you, because my company makes no money, I should be allowed to pay my staff way under market. This doesn't make sense to me, despite being obviously illegal.

The amount of money you paid for labor is decided by a market. Just because I have a horrible business model of giving away cars for free does not entitle to me to underpay for labor. And conversely, if I am a good engineer working for Wikipedia, and FB offers me a much better paying job, I will probably jump ship to FB. Employee retention is a problem for any company.

Now I'm not saying Wikipedia is completely justified in paying the exact same pay grade as FAANG, but it's ridiculous to me that there are so many tears about an executive member of Wikipedia making the same amount of money as a middle manager at Facebook. We are not even comparing directors, we are comparing rank & file to the CEO of another company and people still have a problem with it.

>It's disingenuous at best to connect a nonprofit's executive staff making large salaries with raising the minimum wage

I don't see how the argument is different. I don't think engineers working at Wikipedia should make 300k because they work at Wikipedia. I don't think cashiers working at McDonalds should make $15/hr because they work at McDonalds. You are removing the value of their work simply based on where you think their social status should be,

The better analogy here is GoldBurger, which is a very successful burger chain that sells gold-plated $200 burgers and pays its employees $100/hr. Would it then be reasonable for my local mom-and-pop burger joint, where the most expensive burger costs $5, to compete with GoldBurger on salary? Would the cashiers making only $20/hr at my local joint be paid "way under market" just because GoldBurger exists?

The fact that GoldBurger exists and can create very well-paying jobs for its cashiers doesn't mean that suddenly the entire base of the market rises up to match it. It just means that, all else being equal, it's entirely possible that potential employees will go with GoldBurger rather than my local joint, if given the choice, and the local joint will have to hire other folks. If every burger joint was like GoldBurger, my local joint would be in trouble. But that doesn't tend to be the case, and it isn't the case in the tech world, either.

The average programmer salary in Sweden is $50 000. Why should I donate to people who earn more than twice my salary?

Good programmers in Germany do not work for €50.000. I'm based in Iceland and do contract work for German companies, and I assure you none of the people I work with are even close to €50.000. Perhaps because they're not average but good.

Here in Iceland €50.000 might possibly get you a recent graduate. Myself, I wouldn't hire a programmer at that low pay though, graduate or not. A couple of my friends (good programmers, not "average") who have moved to Sweden and Denmark get similar salaries to what they got up here in Iceland.

Higher salary gets you talented people.

If one look for reasons not to donate, they can always be found by thousands.

I find it beautiful that there is such a site as Wikipedia, that is free and open, and I am happy to contribute a tiny bit to it.

It’s the fact that they are begging for donations while hoarding $300M in cash, and only 5% of your donation goes towards Wikipedia itself. The rest is on the hands of a foundation for them to use at will.

We are feeling tricked because it’s about 5% efficient right now.

They're paying two to three times as much as they would have to pay anywhere else. That's not a "small" inefficiency, it's a pretty huge one.

Your attitude creates a race to the bottom.

It's not about a race to the bottom, it's the vast differences in pay in the same society. If the median real salary is $35 000, why should a 25 year old web developer make 3X that? Some software engineers act like what they do is so much more important and difficult than what everyone else do, it's a bit disturbing. Of course, people in finance are even worse.

Another one is that the companies that we work for make insane profits despite the sky high compensation.

In isolation, without major legislation that depresses those profits too, it at least makes more sense to share the spoils with the shareholders and the employees than with the shareholders alone.

I didn’t think it would happen at the time, but compensation saw a significant jump in the years after the compensation cartel (Apple, Google, Intuit etc.) was broken up.

I guess that's at the core of the discussion. Wikipedia isn't seen by many as yet another tech company there to make insane profits.

Software and finance are high-leverage jobs where improvements are instantaneously rolled out to large sections of humanity all at once and the potential change isn't incremental, it's epoch-defining.

I don't see how you could afford all the things you mentioned on an average SWE salary in Europe. I have a very much above average SWE salary, and don't seem to be in any danger of getting a house and two cars anytime soon. I rent and don't have any cars, actually.

Healthcare is free, for the bare essentials. I pay a crazy amount per year for (private) healthcare, because the standard, mandatory insurance covers just about nothing of what I actually need. Consider that every month, I pay into the government healthcare system a lump sum which is approximately equivalent to the median salary in my country. This doesn't buy me any benefits - I get the same minimal coverage as everyone else. Socialism at its finest.

I'd be OK with it if the money actually went towards worthy causes. That is not the case, however - I am pretty sure most of the healthcare budget goes towards funding an antiquated, insanely oversized bureaucratic system. There's a whole social class of bureaucrats on the government payroll, who do pretty much nothing at all - you won't find them in the office after 3PM - who collect a meager but secure salary for their utter lack of effort and general uselessness.

More and more, I am jaded by the illusion of a "fairer" society in the EU, which often ends up being just a case of "everyone is guaranteed to get the same low-quality treatment".

The reason Wikipedia is amazing is the user generated content and community moderation/admin.

It's also worth noting that many of Wikimedia's staff are remote. I think more of the engineers are based in Europe than in the US and salaries are scaled somewhat based on the cost of living in each employees city/region. Wikimedia salary is almost certainly lower than the big tech companies but still pretty good for a non-profit and the benefits provided are very good if not quite up to the google level of luxury.

Disclosure: I work for the Wikimedia Foundation as a software engineer, however, I don't really know much about the financial details.

Disclaimer: This is just my personal opinion / observation and not representative of my employer.

It’s like you walked into this discussion without reading any of it. That is precisely the issue - less than 10% of the budget goes towards operating Wikipedia, and they’re still begging for money.

Paying for legal staff who defend lawsuits and advocate for legal reforms that matter is part of "operating Wikipedia."

Paying SREs to be on-call for incident response, plus routine upgrades of servers and racking new hardware is all part of "operating Wikipedia."

Absolutely essential parts of operating Wikipedia certainly account for a lot more than 10% of the budget. Sure there is a lot of overhead and I'm sure some expenditures are non-essential. I just can't agree with your assessment. The overhead and excesses are quite certainly nowhere near 90%.

Well, managing a company with over a hundred million a year in revenue, for one.

What is CEO of Twitter doing that CEO of Wikipedia isn't? Why dont we have a discussion of their salaries?

Both are working a job. Enployees are not donating, donors are

The CEO of Wikimedia needs to hire and manage maybe 50 people, of whom about 5 need executive pay. I have no idea why Wikimedia needs 500 staff, if they could build the site with a team of 20 or so.

It looks like a gravy train, and it quacks like a gravy train.

You cannot possibly be serious, assigning twitter CEO some super demanding nebulous task of 'looking for new opportunities' but somehow downgrading Wikipedia one to that of a middle-manager.

Both websites have a massive audience, both have new intiatives and the ones by wikipedia are actually productive. Both have to deal with attempts at censorship, inappropriate content, and both have to find a place in the rapidly shifting techbology landscape.

This judgement 'if it's charity work then it's easy' comes across as dishonest and presumptios.

The Wikimedia execs are obviously not being paid to boost the bottom line; it's fat enough already. Wikipedia has never failed to cover it's costs. It doesn't need whizz-kids; it needs a few competent managers to make sure things don't completely fall apart.

All the pointless side-projects just mean there's too much money washing around. Those side-projects could end up torpedoeing the main deal. Wikimedia makes enough in a year to set-up an endowment that would guarantee Wikipedia forever. Provided they prune the management tree - not so much because of salary costs, but because all those execs need projects, to prove they're not overpaid.

It's nothing to do with "charity work". It's about maintaining mature code, taking care of the editor community (they're not much cop at that), and buying server racks. You don't need scores of leet execs for that - you just need a handful of competent and responsible administrators.

It is your personal judgement, and I violently disagree: if they stagnate, they will either wither and die. FAANGs of this world will eat them, for example by taking snippets from wikipedia and giving nothing back.

It is charity work to spread knowledge, and it has never been as important as it is in the knowledge economy of the 21st century. Do you seriously think that there is nothing to improve, the pinnacle of creation is text format with links? You cannot imagine a more interactive alternative to learn?

Now it's possible that both of us are wrong, and the truth of the matter is something else entirely.

However they are not a public service, and they run their charity in accordance with their vision. If they want to document every dead language and give each poor kid a laptop, people like myself support them, and you don't have to.

Your cost-cutting/management bloat critique comes across as a standardised copy paste of critique you might encounter on "department of highways" or similar public service. It appears to be based off prejudice and assumptions. Not only don't you have that level on knowledge, no-one without a crystal ball could know for sure.

Wikimedia doesn't need to recruit top engineering talent; it's now a maintenance project, and it's open-source. Wikipedia content is created by volunteers, and significant editorial decisions are made by admins, who are usually volunteers. These volunteers mainly manage themselves. Most editors have never communicated with a staffer.

This "Tides Trust" is not a proper destination for donor's money. No donor thinks their money will be spent on some random project dreamed up by Tides Trust.

And it seems pretty irregular to me to treat a donation to the Tides Trust as "expenditure". The correct name for that money is "profit".

Like, this claim of "if everyone donated $2..." (or whatever this year's amount is) means they need more than a hundred thousand donations to pay this guy. And then the site is still at zero, getting nothing, that only pays one person at a "non profit".

I'm all for fair compensation but if you dedicate yourself to running a non-profit, getting rich on people's donations (98% of whose money you took earning less than you) is a weird kind of definition of fair.

If people want to get rich, maybe they should go and fix Jenkins pipelines for some adtech company where everyone's clear on what the goal is.

After looking, I realized that I made more than them at my previous job just being an engineer.

90%+ of the cash goes to fund the other foundations’ programmes, that’s the core of the issue.

I trust the founders. I don't trust new leadership. That's not specific to Wikimedia.

If people feel that they were somehow tricked into their donation, they have instructions on how to request a refund.

It's an interesting thought experiment to consider if Wikipedia didn't exist what would change in the way we learn about and discuss things, especially in these days of fake news etc. Britannica is 75$ per year.

(Some of) the execs are manipulating people to donate, many of the donors wouldn't have donated, had they known that there was enough money already for Wikipedia.

> If people feel that they were somehow tricked into their donation

Problem is, they are unaware about having been tricked.

They generally don't know about this discussion at HN.

They're not raising money on their vision for the future though. Their fundraising ads imply that if you don't donate then Wikipedia.org will go offline

Instead of complaining when a top shelf global organization get paid a reasonable wage in California for the scope of their work maybe focus on how we can redistribute incomes more appropriately.

Also - I am obviously against wasted resources or overly bloated organization or corruption but nothing in this report seems to point anything of that nature. /end mini-rant

Not at all would have my vote. I would donate for that.

I don't think I agree with you at all here, given that I grew up wanting the Hitchiker's Guide to the Galaxy and Wikipedia refuses to offer it... seemingly in no small part because the founder of it makes money off of Wikia.

But, I believe regardless: if someone goes to an encyclopedia and is told "this encyclopedia needs your help: it is going to run out of money unless you donate to it", and you take that money to do something that isn't to improve that encyclopedia, that is absolutely unethical, no matter how useful it might be on its own.

> Wiktionary indirectly supports translation work that benefits Wikipedia

This alone might be somewhat fair (though I find it hard to believe, honestly); but, I still challenge whether someone who comes to the website and is shown the current banner would believe their money isn't being flitted away on things that don't benefit the resource they were using, even if it might be "more ethical" to provide better translations.

At some point in the last 10 years Wikipedia managed to purge as much content as it could about fiction because this was Wikia's turf. There was just an order from above and overzealous mods willing to do the work, even when the content wasn't readily available.

Now the content is in a website that's closed, slow as hell, littered with ads, tracking and autoplaying video.

Maybe Wikia should be the one footing the whole bill for Wikipedia, instead of Wikipedia spending 12% of donation money on fundraisers.

> Please don't comment on whether someone read an article. "Did you even read the article? It mentions that" can be shortened to "The article mentions that."

https://news.ycombinator.com/newsguidelines.html

What exactly are you basing this on?

https://meta.m.wikimedia.org/wiki/Wikimedia_Foundation_Mediu...

They budgeted $5M for "data centre expenses". We cannot know for sure how much it would really cost if WMF only focused on running their website. But $10M doesn't sound implausible to me.

Wikimedia has one project I’m slightly interested in, and spends most of their money on other projects that I’m completely uninterested in, and would personally consider to be largely a useless waste of time. They aggressively fundraise with a message that implies their single product that everybody cares about is financially imperilled. In reality, if they’d been run responsibly, the one valuable thing they produce could have already been financially secured for decades into the future.

I really just don’t care about what they spend most of their money on, I think they’re deceitful in the way that they fundraise, and all I hope is when all of their side projects eventually fail, that their core product survives in some form.

https://meta.m.wikimedia.org/wiki/Complete_list_of_Wikimedia...

You don’t have to put it in air quotes like you’re making some sort of point. Calling everything they fund a “project” is the language Wikimedia use in their budgets and governance documentation.

If you were actually having trouble thinking of a single project they operate other than Wikipedia, then perhaps you might also have some questions about what they do with 90% of their revenue.

Thank you for the link. I was unaware.

https://en.m.wikipedia.org/wiki/Scare_quotes

But don’t worry. I’m sure you really were just “quoting [me]”.

PS: I work for cloud computing company and have insight on how much costs increase with scale.

edit: fixed typos.

It does not significantly use cloud services, and as you can see by the picture of their racks, they use standard 1 RU pizzaboxes. Their workload is highly scalable horizontally, and doesn't even need much in the way of expensive "enterprise" hardware such a SAN arrays: https://upload.wikimedia.org/wikipedia/commons/thumb/c/ca/Wi...

If you buy beige box rackmount hardware with basic compute and CPU, it's pretty easy to spend less than $250K per rack, and the hardware can be kept for 5+ years. That's about 50K per rack per year. Double that for opex, and assume twenty racks distributed across a a handful of sites for capacity and availability. That's just $2M per annum.

Keep in mind they're a high-profile charity, so they get discounts and tax breaks.

(I'm not saying that's all there is to Wikipedia! There's software development, management, finance, etc... I'm just saying that the infrastructure alone is probably less than you think.)

PS: English Wikipedia gets about 250M page views per day, which is only about 3,000 per second. If they used an efficient language instead of PHP, that's well within the capability of a single modern server! There have been comments along these lines made in other forums, and the response was that it would cost more to rewrite the software than the maintain the hardware required for PHP. I don't remember the numbers, but I vaguely remember tens of millions for a rewrite, a high risk of breaking issues, and a significantly lower hardware cost.

They do host their own private "cloud", mostly used for research and project development.

> English Wikipedia gets about 250M page views per day, which is only about 3,000 per second. If they used an efficient language instead of PHP, that's well within the capability of a single modern server!

Nitpicking, page views from outside users are not supposed to hit PHP at all - those requests should be served by their caching layer. But yes, you're correct that they're relying on quite a bit of legacy tech from their early days, not just PHP but MariaDB as well even though many enterprises would now rely on Postgres wrt. these use cases. I suppose that they could rewrite the stuff piecemeal, and recent developments in PHP itself would make it easier. (Some things have been rewritten already, notably the wikitext parser. That's clearly one thing where you would want to avoid breakage at all costs, but they did get it done.)

Postgres is great and all, but there’s really nothing wrong with relying on MariaDB or MySQL for what Wikipedia is doing.

The new parser is being rewritten in php in order to be integrated with the rest of the php code.

This type of comment betrays a complete lack of knowledge about how large scale internet systems operate (which is something I've worked on for the last 10+ years) and comes across as incredibly naive. I can immediately point out huge flaws in your thinking:

* You're assuming that traffic is constant through the day (that you can divide daily traffic rate to get a sense of daily peak; or, in other words, you provision for mean usage, not peak)

* You're ignoring the problems of unpredictable hotspots (single articles suddenly becoming orders of magnitude more popular than the median in relatively unpredictable and spikey ways; think World Cup final or major earthquake)

* You're not reserving any safety margins for unexpected traffic growth, so you'd likely run into cascading failures

* You're assuming that the entirety of Wikipedia can be held in ram. Including all the history and such. Or, if not, that a single server has enough drives that spindle capacity won't be a problem.

* You're not even considering networking/bandwidth costs. How many network cards would your server need?

* You're ignoring any problems with replication/redundancy (e.g., no backups?) so your site would be a nightmare in reliability terms. Of course, once you do that, you'll need to reason about consistency problems.

I think your logical fallacy is that you're thinking that because your can't understand something (that running Wikipedia could cost so much), it must mean that the thing you can't understand isn't true. Instead, I'd suggest that you'd get further by focusing on discovering the limits of your understanding and genuinely asking yourself: "How could it be that it costs so much? What may I be missing?"

Also, don't assume I'm speaking from a position of ignorance here, I know more than a little about how Wikipedia works. I've perused the source, played with the database dumps, etc...

I find comments like yours amusing, because I hear similar things in the industry all the time! People like you are not wrong, it's just that correct knowledge is very rapidly outdated in this industry. It's shocking what exponential growth really means! As a random example, I once had an engineer going on and on about their "powerful" email server that cost them six figures. I pointed out that it was slower than the Blackberry phone it was synchronising the email to. (No, really!)

You really underestimate the spec of a modern, 2021 era server!

You really are.

You can buy, right now, for "normal" money, a server with two 64-core AMD EPYC CPUs. That's 128 cores that are the fastest individually of pretty much any server CPU. This platform provides 256 hardware threads. Right there, you're looking at something like 12 requests per second per thread. As long as you can serve them in under 85 milliseconds each on average, that's plenty!

I've written a Wikipedia clone for an in-house CMS. The content generation was so fast that for laughs I compiled it to javascript and had it run per keystroke for a live preview in the browser. This worked fine for content up to about 64 KB. This was in 2008, by the way. Things have moved on in terms of performance. Try this with Rust and some judicious use of high-performance AVX-enhanced parsers, and you could generate a typical Wikipedia page in under 10 ms, no sweat. Then there's output caching to get it even lower...

That server can have something like 4 TB of memory in it. The entire Wikipedia database is just 5.6 TB uncompressed.

Yes, you really can fit most of Wikipedia in memory!

Bandwidth? Mellanox makes 200 Gbps Ethernet cards. They're dual port, so that's 400 Gbps. That's enough to handle the bandwidth of a decent sized regional telecommunications company through a single box. I should know, I've seen the network diagram of mine, and they have only 100 Gbps inter-city links!

Spindles!? Are you kidding me? There are gaming PCs being built right now with 2 TB NVMe drives in them that can individually put out 7 GB/s and 1M IOPS! Who the hell puts servers on spinning rust in this day and age? That lone, single NVMe drive is putting out 56 Gbps by itself. Throw in a smidge of caching, and it could saturate those aforementioned 2x200 Gbps ports.

So no, I would not put the entirety of Wikipedia on just one server, that would be silly.

I would put it on two.

Okay, maybe three, for redundancy. Just in case.

This is incorrect. Many of the numbers you throw out ignore that in order to serve its content a server must do some work, which requires both CPU time and memory. Assuming you were able to eliminate hard drives and fit everything into RAM, you still have the problem that to serve requests and do that work you need RAM.

>That server can have something like 4 TB of memory in it. The entire Wikipedia database is just 5.6 TB uncompressed. >Yes, you really can fit most of Wikipedia in memory!

This is incorrect. According to Wikimedia[2], the entire uncompressed size of Wikipedia is 19TB as of 2019, and the site has grown since.

Talking specifically about hard drives:

> Spindles!? Are you kidding me? There are gaming PCs being built right now with 2 TB NVMe drives in them that can individually put out 7 GB/s and 1M IOPS! Who the hell puts servers on spinning rust in this day and age? That lone, single NVMe drive is putting out 56 Gbps by itself. Throw in a smidge of caching, and it could saturate those aforementioned 2x200 Gbps ports.

Firstly, gaming PCs are almost always ahead of the curve when it comes to performance on everything.

Secondly, to your question about who puts servers on spinning rust -- Pretty much everyone. Backblaze even releases HDD reliability ratings[1] based on what they observe in terms of the spinning platter drives.

Also, your 2TB NVMe drive is going to cap out at around a quarter of what the large-spindle raid controller can, and you can have a few of those in each system if you want. Sure, a PCIe 4.0 NVMe drive is going to get you 7.88GB/s in your motherboard slot but a PCIe 4.0 raid controller can have four times that bandwidth available to it.

But for argument's sake let's say you decided to swap out your raid controller for a PCIe 4.0 card that does NVMe and has onboard raid (these don't exist for purchase yet that I can find at my usual suppliers but I imagine they're coming). Now you have a size problem. The largest current best available SSDs are Sabrent's 8TB PCIe 3.0 drives. This will cut the performance considerably but is probably the sweet spot for size & speed. You need 4 of them just to host current Wikipedia, limiting any growth, and certainly without factoring in any other parts of the system that may take away from the operation.

For comparison's sake to the 2TB NVMe drive in your example, my old homelab can hit 5 GB/s on five spindles that I bought in ~ 2011-12 and they're all old and cheap, not enterprise-grade gear.

> So no, I would not put the entirety of Wikipedia on just one server, that would be silly.

> I would put it on two.

> Okay, maybe three, for redundancy. Just in case.

Then you have issues of bandwidth by having so few connections, as well as the poor user experience of trying to visit a site that exists and is served in only three places (hopefully around the globe). It's also bad for reliability because if any one site loses its connection suddenly your 200GB/s traffic is pushed onto the other servers. If you want a sense for how reliability engineering works you should look at how Netflix does testing and why they've managed to withstand regional AWS outages despite being hosted on AWS[3].

Wikimedia lays out their system set up pretty well on their own page[4].

Could you technically host wikipedia on your own systems? Sure, lots of people do, go visit Reddit's r/datahoarders and I'm sure you can find more than a few who have their own local copies. Could you actually replace production wikipedia on the Internet with the setup you describe? No, you cannot.

I also suspect you haven't costed out the server setup you describe, as it seems incongruous to say that they spend too much while advocating replacing their entire server stack with cutting edge hardware (and will they need to do so annually in order to keep up?).

[1]: https://www.backblaze.com/blog/backblaze-hard-drive-stats-fo...

[2]: https://meta.wikimedia.org/wiki/Data_dumps/Dumps_sizes_and_g...

[3]: https://netflixtechblog.com/lessons-netflix-learned-from-the...

[4]: https://meta.wikimedia.org/wiki/Wikimedia_servers

Who cares if Blackblaze -- a backup company -- uses hard drives? Of course they do! They're not hosting Wikipedia though. My point was by using current-generation COTS hardware, it is entirely possible to host a huge website on a single box. It is. It really is. This is not about what other people generally do. This is about what is possible!

You keep getting bogged down by the practicalities of real-world site management. For the sake of argument, if I were to engineer a serious solution for this problem, I would be looking at hardware more like what Cloudflare uses for their edge cache boxes. They did the legwork to find the sweet spot for price/performance. This is typically a single-socket server with a 48-core AMD EPYC processor and 100 Gbps Ethernet. This CPU model is much cheaper than the 64-core flagship, but has the same amount of cache. (They're made from the same 8-core chiplets, but with 2 cores fused of due to defects.)

In these servers I would use PCI-e quad port NVMe adapters, as you said. The capacity requirements aren't as high as you think either, because the content can be sharded. The 5.6 TB number is for english Wikipedia, not all of Wikipedia + Wikimedia as a whole! So those 4x 8 TB cards are more than sufficient. Heck, even 4x 2 TB is enough for a while. The trick here is to apply some sort of lightweight compression on the text. That 5.6 TB compresses down to just 100 GB! In practice, you could easily get better than 3:1 ratios even with a very fast compressor set to "light" compression.

Then I would distribute these servers around the globe, with about 3 per location. One for english, with the other two for all the other languages. Each server would have a local, read-only replica of the language-specific databases with asynchronous streaming from the master copy.

I'd distribute this to about 5 regional locations, and nominate one server per language as the "write master" where updates occur. So for each language you'd have 1x read/write and 4x read-only. These would be at different locations, so for example German wikipedia would have the read/write replica in Germany. English would be at some US east-coast location. Etc...

Then you'd need some boxes for nonproduction test, dev, etc...

All of the remote edge servers would be load balanced using a DNS-based method, with no local load balancers. The servers' 100 Gbps ports would be directly connected to the peering routers, the same way Cloudflare and the like does it. This would add up to 1.5 TBps of traffic that you really could physically serve (5 x 3 x 100 Gbps).

Overall, the entire platform could be handled by something like 20-25 servers. That's it.

Now, I tell a small lie: Wikipedia hosts only the text! WikiMedia has the pictures, which don't compress well and requie much more disk space. This is best served with technology similar to AWS S3, which can be replicated with open source software and some boxes packed with hard drives. But again, you're probably overestimating the capacity required, and underestimating how much you can pack into a server these days.

Just to reiterate: the above is predicated upon having an efficient codebase, and Wikipedia isn't currently efficient enough to make this possible. It would take a rewrite of the code to achieve this, and that would cost more than their current hardware, so it doesn't make financial sense. Most web sites are in a similar situation, which is perhaps why your perspective is skewed: Your expectations of software performance capability might be off by a few orders of magnitude!

MediaWiki repository size is about 1.4 GB and according to phploc it has closer to a million lines of PHP code. Sounds like fools errand to rewrite it.

The wiki staff themselves admitted that the current parser is inefficient, partly because of PHP, partly because the underlying grammar was not designed to be efficient, and partly because the parser itself was built up over time and wasn't easy to optimise.

My approach was to write the parser and a matching "markdown inspired" format at the same time, optimised for speed. Just a handful of small tweaks to the syntax were all that was required to largely eliminate backtracking and achieve a nearly linear parsing time in most cases. If I remember correctly, I had it down to about 1-5ms for a typical 64 KB page, and then HTML generation was another 5-10ms depending on various factors.

What a lot of people are missing here is that Wikis are not at all like typical "ERP" applications. The latter sometimes requires dozens of API calls and thousands of database queries to generate just one kilobyte of output HTML. Wiki is very linear, with a single 1-100KB blob of text as input, a matching 1-100KB blob of HTML as output. It all boils down to the parsing and HTML generation efficiency, nothing else matters!

You can parse grammar on save and make an optimized compiled format where static content is already resolved. Next step is to substitute semi-static content (like author name) to a runtime format, this last format can handle dynamic data substitution like current date & time, but probably going to be rare that any substitution is needed for the runtime format (how much truly dynamic data does a wiki have?), most of the time just print it with readfile or similar. Only difficult part here is cache invalidation for the runtime format (I know, it is one of the three difficult things you can do in programming).

3000 request/second in PHP is not hard, especially if you plan for it.

This is why it amuses me that people seem to think that Wikipedia "requires" tens of millions of dollars of infrastructure to host. It doesn't require it. It's just that some things are better/easier with more kit, such as maintenance.

Hm, since Wikipedia dumps are public, has anybody tried? Moving wikipedia itself might be a large endeavor, but seeing some submissions on HN I think a very dedicated dev or two could possibly manage a rewrite to have a proof of concept.

For any attempt at porting over MW, you will need to re-implement the whole parse/include stuff... and that is a lot of work, even for a proper team.

Otoh https://en.m.wikipedia.org/wiki/Internet_Archive#Ceramic%20a...

Even for a well-informed person who understands that's not how Wikipedia works, your comment does no favors for the people who are already walking around with the idea in their head that it does, nor does it help the people who have to correct this (too frequently) mistaken belief. And after ruling out that that's what you meant, it's not clear what your comments did mean.

Whether or not its 10x better service, I don't know, but they are definitely doing more now then back then. There's been lots of software development since 2011 (Some good, some not so much). Even just site speed and stability has improved significantly since 2011.

And it's probably questionable if all side ventures are needed or if they could/should have sticked to the core project and developt it with little money.

As mentioned further down: Do you really need 40 fundraiser positions?

It seems they currently (2019-2020) are responsible for 12% of the expenses [1], but I can't find any information as to which percentage of the donations they're responsible for. I wonder if there's a more transparent report for that.

Looking at their donor numbers [2], it suggests that most of the fundraising is still coming from the long tail, from regular people donating online. They only seem to have 17 "major benefactors" and even if we multiply the smallest amount for that tier (50k) by 10x, that still only accounts for 7% of the donations.

According to their 2019 data, the average donation seems to be $15, which suggests Jimbo banner is way more important than the fundraisers.

Of course my assumption might be completely incorrect.

[1] https://wikimediafoundation.org/about/annualreport/2020-annu...

[2] https://wikimediafoundation.org/about/annualreport/2020-annu...

EN Wikipedia has always been where the lion share of attention was focused on (With wikidata and commons coming in second. The other projects get very little love).

Well, side ventures which burn money would explain factor 10, but yeah...

[0] https://en.m.wikipedia.org/wiki/Wikipedia:Size_comparisons

On big thing that changes as a site grows, and as it reaches more places internationally, is that it attracts more attacks. Stopping that costs lot.

Money is a funny thing, in Denmark about $320 million is spent on Covid testing a month. So from January to July that would be the equivalent of Wikipedia funding for 20 years.

I'd definitely want an analysis on the server costs. Compared to ten years ago you can get vastly better servers per dollar and about ten times the bandwidth per dollar.

Here's the OG version by Jimmy Wales: "The sum of all human knowledge available to every person in the world."

Here's what it currently looks like: "Empower and engage people around the world to collect and develop educational content under a free license or in the public domain, and to disseminate it effectively and globally." https://wikimediafoundation.org/about/mission/

Which one is more inspiring on all counts?

The management probably don't see themselves as caretakers of incredibly valuable resource that needs to be preserved. Which is probably what 90% of the rest of humanity want them to be.

The first version is about centralizing all informations so it can be consumed. It's the traditional view of knowledge dissemination, scaled to the whole world instantaneously. The second version is about giving people the tool to produce knowledge so it can be shared with the whole world. Just like the printing press spread authoring power from a select few people who bothered to write everything, to anyone with enough money to buy a machine, Wikipedia is giving the power to share knowledge from those who had the right curriculum to anyone with a bit of motivation.

This is the revolution that Internet and the Web promised (not just allow everyone to watch and listen, but give everyone a voice), and I'm glad Wikipedia is doing it. If it takes more money to fulfill that mission then it's totally worth it.

The 2nd is mature, focused, grounded in reality and is actually what wikimedia does. So yeah #2 100%. But then again I'm not 12.

https://upload.wikimedia.org/wikipedia/commons/9/9f/AR_web_a...

I guess now we have to fight over what 10 years ago means.

Please do not bring disingenuous arguments in 'exposing' suspected disingenuity, it is counterproductive.

1/ Ŕunnign a website requires constant change just to stay still. Technologies change, usage changes and user needs change. There is need for experimenting, dealing with drama, and getting funded.

2/ WMF cost per user is very reasonable for the amount of usage. If WMF would run as a subscriber based service, it would cost just $0.5 per month/per user (rough estimate). Total expenses:$112M, 330,000 active users editing site. >800 million monthly unique devices (en-wiki alone).

> But keeping Wikipedia online is a task that the WMF could comfortably manage on $10 million a year This part is disingenuous and bordering on malicious. The linked email (https://lists.wikimedia.org/pipermail/wikimedia-l/2013-March...)

He has editorialized the word "comfortably" and he should have discussed how the estimate might have changed since 2013, but overall I don't see why you think it's a disingenuous relating of the original email. I don't see any relevant nuance in the email that would significantly change my view of the estimate. However, I haven't gone through the preceding emails at all

> 43% Direct support to communities

> The Wikimedia projects exist thanks to volunteer communities around the world that create and maintain them. We strengthen these communities through grants, programs, events, trainings, partnerships, tools to augment contributor capacity, and support for the legal defense of editors.

My wife's friend just came to stay with us. He worked for the Wikimedia foundation for a long time and we were just talking about this. From what he said, after engineering expenses, legal expenses are the highest category. What he said happens is, say, the government of India finds editors with IP addresses in India, contributing to a page with a map not showing Kashmir as a part of India, and either arrests or sues those people, and Wikimedia Foundation tries to do all they can to provide legal defense for these people.

Ironically, this guy's biggest complaint and the reason he left Wikimedia is they don't pay enough for engineering. They're still fighting a propaganda war with all of the world's governments to provide accurate information, and that is a labor-intensive war being waged by true believers and volunteers. For instance, they block all IP blocks allocated to US legislative offices from editing any pages because of how consistently Congressional staffers were vandalizing pages and posting misinformation, but surely these people have learned of the existence of VPNs and working remotely. They clearly need better automated detection and moderation system, but to develop and deploy such systems, now they're competing with Facebook and Google for labor, but paying 1/3 of what Facebook and Google pay.

Apparently, people think the answer is they should just move to Vietnam or wherever labor rates are lowest.

Look, I don't doubt overseas developers are just as talented as anyone else, but history has inertia. There's a reason Silicon Valley firms are located in a place with university professors and professional mentors who invented much of the modern OS and Internet. I also don't doubt athletic talent is evenly spread around the world, but nonetheless South America and Europe dominate football, the US dominates baseball and basketball, Kenya dominates distance running. If you want to put together the best basketball team you possibly can, you go to Los Angeles, New York, or Chicago. You don't look around the world for the cheapest labor rates and go there.

This kind of nonsense is exactly why I left the nonprofit world so long ago. The public all believe labor should subsist at the bare minimum living wage of the cheapest possible place to live, and no money whatsoever should be spent on fundraising.

Just understand when you take this position, if the nonprofit is involved in anything that governments and for-profits might also be interested, say, influencing how and what information gets disseminated to the entire world and for what purpose, the non-profit trying to minimize cost at all cost is going to lose to the governments and for-profits every single time.

This is disingenuous, moving to pretty much any European city would be enough. Asking people to donate to an organization that pays people 10x of what you make while pretending that they are in dire need of money is just gross.

There are thousands of editors who deal with vandalism. WM doesn't need to develop new vandalism-detection software.