bingo-bongo

That may be true for billing, but Hetzner killed all access to my dedicated server on a weekday afternoon and when I reached out to them within 30 min, the response was “it was done by the networking department, I can’t do anything about it, but they’ll look into it tomorrow..” .. :| wtf?! not okay Hetzner! (My “mistake” was a interface mis-configuration, nothing abusive or otherwise problematic)

I don’t think the end user is the target audience for the article.

> But doesn't this just mean that instead of writing your code and logic in Ruby you're writing it in RDL?

..and write a test for it..? :|

> ..and that when we fixate on the people who build systems and forget those who maintain, moderate, and use — or, in this case, exploit — those systems, we’re missing the messy realities of how technology actually evolves.

(Somewhat out of the original context, but this really stuck with me)

Depends on type of attack/level of security vs convenience. Having both username, password and TOTP in you password manager protects against password leaks from cloud services, but not from someone stealing/getting access to the content of your password manager. Having TOTP on separate device protects against both, but is also a bit more inconvenient in daily use.

Being able to schedule with a timezone is also great! Regards, someone living in a country with summer/winter-time

What makes it a terrible user experience?

I think `docker-compose down <service> && docker-compose up -d --force-recreate <service>` should do it.

Crystal is great!

After ~10 years with Ruby, I decided to try out Crystal for my latest weird hobby project (a modern style bbs) and I have enjoyed it so much!

Considering the relatively short lifespan of Crystal, I was positively surpriced how good the documentation was and how fast, easy and stable the language it already is :)

Also, why would you put your public key in your own authorized_keys on the same host? (that has the private key) Is that something people do..? Edit: typo

Even though a hot standby is technically the exact same thing as a read only replica, it solves 2 very different problems (uptime vs scaling). Personally, I never want read only queries going to my hot standby, otherwise I risk the secondary can’t handle the load in case of failover. Probably a reason like that with AWS as well, as they are selling a “hot standby” product to ensure the uptime for your RDS.

I would argue that poorly configured docker images as far bigger issue than insecure http servers: https://www.infoq.com/news/2020/12/dockerhub-image-vulnerabi... Security wasn’t the motivation imho, but being able to package your app with all it’s dependencies, including OS libs and deliver it extremely easy, sure was.

If your data changes a lot, try REINDEX and VACUUM ANALYZE on the tables involved and then test and check if the query planner still wants to do seq scan.

We have a couple of rather large tables with a lot of changes, where is’s needed regularly to ensure the query planner makes the best possible plans.

To be fair, your ns secondaries usually does pull the zone (axfr) or zone changes (ixfr) from the primary - the zone reload just sends a notify to trigger it.

The executive director of the .NET Foundation force merged a PR on a project, instead of following project guidelines.

The incident snowballed into other projects discovering they have been moved to the .NET Foundations Github Enterprise account without their knowledge.

And even more projects joining the snowball with “we were told the Foundation were just there to help us, not take over project ownership”

And now there is a huge snowball with a lot of projects and people stuck inside.

The forced PR was reverted shortly after by another maintainer.

And I agree, a “sorry my bad” type of comment would have looked nice in the PR, but the attitude and actions in it vs the official apology, sounds like completely different people.

..and attack surface - physical presence vs entire Internet is quite the difference.