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.

I hate the concept because it’s just really wasteful of energy. If I recall correctly, only 30% of the power output of the charger goes into the device, versus 95+% for wired.

Dust?

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?

But you can have a DAC to plug them in then, which probably will sound better than your phone’s

It takes 5 minutes at most to get another hour of playback from my headset. You do not need a headphone jack in this day an age, and I say this as an avid music listener. Also ANC won’t work if your battery is dead most of the time, so having a wired option is not that useful for your flight