> Sometimes users will still get errors from PowerDNS directly, but I added some logging of all the errors that users see, so hopefully I can review them and add extra translations if there are other common errors that come up.
I noticed that you are using our Go module to access the API. It is wonderful to see our work helping others build great software, especially for education. Thank you for that.
Please note that the upstream API sometimes changes slightly between minor releases. For example, prior to v4.9, the error response for a non-existent server was "Not Found". Starting with v4.9, it changed to "Method Not Allowed".
Unfortunately, error responses aren't always part of the API specification. I'm thinking about adding the most common cases to the module anyway.
> At the moment there is still a one-time order fee for dedicated servers
For (some) dedicated servers, I think. Last time I checked the lowest tiered dedicated servers didn't have any setup fees. If it's not mentioned, assumed it'll remain.
As diggan said, there's usually at least one of their dedicated server offerings for which setup fees are waived, so I figure my tests would use the API to find out which one and use it :)
I think it helps to speak the same „language“ as the manager. Add price tags to the infrastructure development or technical debt. This may add an important perspective to the discussion for both sides.
As developers you should be doing this anyway to understand why you want to do something. Gut feeling for "it's just better" doesn't get you far - no wonder you can't get anyone else on board.
Similar issues happen for justifying security. But if you've got a price tag, then just do expected utility. What's the odds that you'll need a backup? 1%? 0.1%? Per year? And what's the value of that backup price tag during that time? $10m? 0.1% per year * 10m = 10k per year.
Give the price tag when missing. The argument is we need to fix this in order to insure against this catastrophic event.
Or take the price tag when missing multiply by the probability of needing it over the course of one year. This is a more accurate estimate for the annual cost of not creating the backup.
Slightly related: If you're self-hosting your email, you can use autoconfiguration[1] and autodiscover[2] to help your users set up Thunderbird and Outlook correctly.
I am so glad that the congress is back. It's been an important event for me for more than a decade, and has been a huge gap between Christmas and New Year since it was cancelled during Covid.
I've been a very happy Roundcube user for a decade without a single problem. Also worth mentioning, their CLI update script just works without a hitch.
I'd like to see Nextcloud adopt Roundcube's commitment to reliable software. I've tried migrating my calendars, reminders and contacts several times, but it's never worked reliably. There were often subtle problems such as missing calendar entries that simply disappeared without a trace.
This reminds me of a problem I had a few years ago. Whenever I sat down on my office chair, my monitor turned black for a few seconds.
One day I started to understand what’s happening when I touched the aluminum Apple keyboard while being electrically charged. I was wondering how it was possible to get an electric shock since my Mac Mini had no connection to ground via its IEC-60320 C7/C8 connector. I learned that the Mac Mini grounds itself via DVI.
Turned out the pressure cylinder of the chair caused some kind of electromagnetic pulse, which interfered with the DVI signal and forced the monitor to resync every time I sat down.
I noticed that you are using our Go module to access the API. It is wonderful to see our work helping others build great software, especially for education. Thank you for that.
Please note that the upstream API sometimes changes slightly between minor releases. For example, prior to v4.9, the error response for a non-existent server was "Not Found". Starting with v4.9, it changed to "Method Not Allowed".
Unfortunately, error responses aren't always part of the API specification. I'm thinking about adding the most common cases to the module anyway.