We had to roll back to an earlier version of Sentry for this exact reason. It went from a few gb to using 18gb+ of RAM and a factor more number of containers. The older version had every feature we wanted, so there was no need to move forward.
Extremely poor response. You can't blame him for contacting others affected when you marked it as out of scope. And yet you fail to mention that in your blog post..
I feel if I open Uber ahead of a planned travel and type in a destination to get an idea on the price, the price is $X. I then open the app back later when I'm ready to travel (say 15 minutes later after packing and leaving the hotel) and the price has gone up (sometimes by quite a bit).
Now maybe I'm just unlucky and the dynamic market prices have gone up every time, but I've never seen the same price or less.
Which makes me wonder if Uber records your interest in using them to get to a destination and then increases the price when you come back after committing to using them for your trip.
I now only open the app and search when I'm ready for the trip.
How will this affect those running MicroG? Is it as simple as implementing that API and returning "trustworthy", or is there some kind of signing going on that will make it harder?
Docker can run on macOS (albeit in a VM), but its still running on a Mac "that is already running the Apple Software". So its a perfectly valid option for Mac owners, even if its a VM + container + VM deep.
K-9 Mail is great. Coming from iOS to a google-less android, I'd be lost without it.
The decision to keep both names is strange though. If its just a name and colour theme, what is the point? Thunderbird already has far more brand recognition, so it makes sense to just switch.
Love caddy. Only minor downside is having to build your own container to get route53 DNS support.
Would be awesome if they provided a pre-built container for each module, but understand it'd create a very large number of builds for them, and then people would want module+module which would create an exponentional number of possibilities.
Maybe an all modules build and the ability to toggle them via ENV?
We've used it in a single-user (a docker user) and multi-user (user for each dev) environment.
Most, if not all, containers work fine, there are some, like mailcow which don't work well with it.
If you have multiple IPs on the one machine, there is a longstanding bug that means you can't bind the same port on different IPs. Eg IP1:80 and IP2:80. The workaround for this is separate rootless docker users + runtime for each container that shares ports, nasty.
In a multi-user environment we simply setup rootless docker under each devs user, so they have their own runtime and their own containers isolated from other devs. This works really well.
If you're looking for an open-source self-hosted alternative to Dropbox, I've found Seafile to be flawless. Seadrive is also nice if you want to access your data as if it were a network drive.
* Not affiliated with seafile, just really like their software.