Do they? I haven’t seen any comments from them about it.

I mean, if they’re entering the front door, not a hidden entry somewhere at the back, it’s pretty open. Like an open secret

Mike is “more or less” openly a Nazi if he frequents the nazi bar. Don’t need them to outright say heil Hitler to see what crowd they promote and attract.

Have you read the same article?
The founder hosted a debate with an open fascist then gave him a platform on the FUTO YouTube channel.

You mean the security team that got pwned here?

Not if you run a wildcard CNAME for your sub domains right ?
Like I have *.mydomain.com point to my server, and there I have a different reverse proxy depending on the domain.

Indeed it is technically possible to donate, but like you said, they are really not making it easy nor do they depend on it for survival.
Money corrupts and makes aligning user needs and profitability quite difficult, as we see with Plex now

Jellyfin refuses donations so even if I (not the one you’re responding to) wanted to, I would not be able to.
Pretty funny one has to keep reducing features and increase prices, while the other is actively refusing funds because they have enough already.

The source engine does not handle case sensitivity when loading assets from disk. On windows it’s not an issue but on Linux it will silently fail to load assets if the case doesn’t match. I lost so many hours trying to fix some weapon animation that had 0 seconds run time when porting a mod dedicated server to Linux.

Go had the same behavior until recently. Closures captures the variable from the for loop and it was a reference to the value.
They changed it because it’s “common” in Go to loop over something and run a goroutine that uses the variable defined in the loop. Workaround was to either shadow the variable with itself before the loop, or to pass the value as an argument.
It’s been a long time since I wrote c# so idk if the same is expected from the avg dev, but in Go it’s really not explicit that the variable will be a reference instead of a plain value

Holy moly, the comments on the article are full of reactionaries shitting on Linux for having a CoC and enforcing it. Did not expect so much hate for such mundane things

I get what you mean. GitHub and friends have pushed that back to a more centralized approach. However I think that it’s not too bad actually. Most projects tend to be centralized too

I mean, it’s decentralized alright, but it doesn’t mean it’s HA or automatically replicated. You can just use a different origin server and push/pull from it instead.

It’s even funnier since “chat” is pronounced with a hard T at the end, and in French chatte is pussy.
So it’s more like, pussy I farted

I did not yet upgrade to the latest version, but to migrate to compose I only had to copy the volume paths and the environment variables from Synology.
I can share my compose yaml by the end of the day if you need.

Before I upgrade I will try putting the cache on a SSD instead, seems it can improve performance quite a bit

The latest version of Synology with the container manager allows you to update images from the registry and will restart the container for you.
But I still migrated to docker compose to enable hw transcoding with quicksync

Care to explain why ?
I didn’t feel a change on my side, but I’m in Europe so maybe it’s different elsewhere?

My assembly code only goes brt :(

I would Guess the air cannot sustain the performance as well as the pro. The battery is way bigger afaik Doing 16+h on a single battery charge is insane

The biggest difference for me was the noise. Intel mbp fans spinning as soon as you open more than one application, going turbo if you compile anything and slowing down in the summer because of the heat.

The only time I heard my M1 Mac fans is when I left the poor thing in direct sunlight outside