bingo-bongo

8 ms·

61.
by bingo-bongo 5y ago
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 c
62.
by bingo-bongo 5y ago
Being able to schedule with a timezone is also great! Regards, someone living in a country with summer/winter-time
63.
by bingo-bongo 5y ago
What makes it a terrible user experience?
64.
by bingo-bongo 5y ago
I think `docker-compose down <service> && docker-compose up -d --force-recreate <service>` should do it.
65.
by bingo-bongo 5y ago
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
66.
by bingo-bongo 5y ago
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
67.
by bingo-bongo 5y ago
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 secondar
68.
by bingo-bongo 5y ago
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 bein
69.
by bingo-bongo 5y ago
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 regu
70.
by bingo-bongo 5y ago
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.
71.
by bingo-bongo 5y ago
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 ac
72.
by bingo-bongo 5y ago
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 peo
73.
by bingo-bongo 7y ago
..and attack surface - physical presence vs entire Internet is quite the difference.