the claims in some media that Telegram is some sort of anarchic paradise are absolutely untrue. We take down millions of harmful posts and channels every day,

Gotcha. Millions of harmful posts every day. That really does sound like a great place.

Following along with the style of your own post: YAML doesn’t suck, because I feel so.

Thanks for asking.

I get that, I really do, and I honestly believe you have exactly the right idea.

But on the other hand, you have to realize that not all of the money purely goes to enabling knowledge sharing with Wikimedia. This is not an election, it’s a company, non-profit or for-profit doesn’t really matter. There are still people paying off business expenses from your donations.

I fully understand the necessity of this, but you might just feel better if your $5 literally bought someone a meal or if it paid for a fraction of a business flight to promote Wikimedia.

I do give in small streams and I do large annual contributions. I’m entirely not opposed to sharing.

I prefer to keep the small donations to individuals who also prefer a reliable stream of goodwill. Larger organizations also prefer reliable streams, but they also receive millions in donations overall, usually with significant large donors.

If you look long enough, you’ll find enough material to not want to contribute to Wikimedia. If your contribution was only a drop in the pool to begin with, maybe this is one of the expenses that is not for you to carry.

https://wikimediafoundation.org/support/where-your-money-goes/ might be a good starting point.

https://www.wikimedia.de/2022/en/finances/ has some clear numbers up front, but I’m not sure if these only relate to Germany. I haven’t been following the sources recently.

Makes sense. If you’re contributing less than $1000 monthly to anything, you’re not making a difference. If you want dedicated people to be on the receiving end, who also do a great job, every single person will cost thousands each month. Wikimedia is literally spending millions each year.

Honestly, don’t try to hunt for the “best” spot to contribute your exact amount of spare money to, with the hope of having the largest possible impact. It won’t happen. Treat a good friend to some food instead.

If you really feel like you already got some value out of a service in the past, give what you can, without limiting yourself financially in the process. If you feel like you don’t have the $1 to spend for Wikipedia, don’t spend it. Don’t guilt trip yourself into donations ever. Your donation today will not prevent a service from turning into shit tomorrow. Pay for what you got

I’ve been a funding member of the Wikimedia Foundation for over a decade. I have looked at their finances several times before and during financing them.

As with a lot of similar non-profits, a considerable amount of donations does not go into “running the servers”. You have to judge this by yourself, but they don’t embezzle any money and there is a reasonable bottom line. Wikipedia continuously helps tons of people, and the people who run the operation enable that.

You can download a full dump of Wikipedia any day. Compared to other lying companies, they have been true on their promises for some time.

Of all the $1 I could spend in a year, the one I give to Wikipedia is probably the least wrong invested, and that $1 actually already makes a difference

I’d be more worried about media than the ability to pirate it.

Music has adapted to generate plays. Platforms are already being polluted with genAI music.

TV was replaced by streaming services. Series come and go and are very specifically tailored to get people to subscribe. Exclusives are the standard. Single season productions are not uncommon. People are also already investigating ways to pollute this pool with genAI as well.

Movies are a stream of Marvel and Disney garbage that was already more CGI than acting. Now genAI and upscaled classics are on the menu.

Piracy will not go away. People used to record movies with camcorders in the cinema, now they pull raw files from CDN nodes. There is always the scene. The platforms that try to profit from the scene come and go.

I wasn’t actively aware of this for most of my life until I recently visited a clients office. Buying someone a cup of coffee is an entire thing. There’s no free coffee. You have to purchase every single cup. And you first have to walk several minutes to the place where they sell the coffee. It blew my mind. I’m used to drinking one cup after the other without even giving it any thought. Coffee machine right next to me or around the corner. There, coffee incurs friction and cost.

So when you invite someone for a cup of free coffee, this can open doors for you. I’m not kidding. People get all excited when you offer them a coffee break on your dime. And there’s levels to it too. There’s the regular coffee, and there’s the premium one. For the premium you have to walk longer and wait in line until the barista serves you.

It’s a key component in office politics when coffee access is regulated.

Why anyone would restrict access to legal stimulants in the office is unclear to me though. Put espresso machines on every desk!

Depends on the product. It’s just something to think about when signaling errors. There is information for the API client developer, there is information for the client code, and there’s information for the user of the client. Remembering these distinct concerns, and providing distinct solutions, helps. I don’t think there is a single approach that is always correct.

I don’t necessarily disagree, but I have spent considerable time on this subject and can see merit in decoupling your own error signaling from the HTTP layer.

No matter how you design your API, if you’re passing through additional layers, like load balancers and CDNs, you no longer have full control over all responses your clients receive. At this point it may be viable to always signal a successful backend connection with a 200, even if the process resulted in a failure.

Going further, your API may include partial success scenarios, think batch processing, then the result could be a mix of success and failure that doesn’t translate to HTTP status.

You could even argue that there is really no reason to couple your API so tightly with a concept of the transport layer it uses.

Respect the Accept header from the client. If they need JSON, send JSON, otherwise don’t.

Repeating an HTTP status code in the body is redundant and error prone. Never do it.

Error codes are great. Ensure to prefix yours and keep them unique.

Error messages can be helpful, but often lead developers to just display them in the frontend, breaking i18n. Some people supply error messages in multiple languages, depending on the Accept-Language header.

I feel like the time to hide information behind YouTube links is over. Feels like a link to a paywall article at this point.

5 nines imply a downtime of 6 minutes a year, or every 100,000th operation failing. That’s not great for a file system. I assume you picked the number arbitrarily, but still think about it.

And has been for so long, they already went through it once

Numbers give the wrong impression that one version follows another. Debian release channels exit alongside each other individually. Giving the release channels names helps to make that distinction. It also makes for an easy layout of packages in APT repositories.

Sid is and always has been Sid. If you were to assign numbers, what number should replace that name? There are perfectly working labels for release channels and there is no reasonable replacement.

That is some next-level Minecraft you are playing over there

Now that is ancient js style

Okay, maybe I read you wrong. I agree that nobody will try to acquire details through mullvad to prosecute this.

I read the comment like downloading music is so irrelevant, you could skip the VPN, which I would disagree with.

I once downloaded an album I had already pre-ordered, but didn’t want to wait, no VPN. Got a letter from a media lawyer within the month. Felt pretty stupid.

Now this is some horrible advice. Bravo