UBI/UBS requires a very solidaric community. But the current situation (in Germany) is not about finding any job but taking a low paid, hard working or even dangerous job (nursing service, shifter, even soldier, public sector).
UBI makes it even harder to find people for that kind of jobs. Not paying any social benefits and increasing the pressure on the unemployed to take these jobs is much more interesting for everyone that is not unemployed. Please don't judge me for writing this. It's the feeling I have, not my view.
A lot, I'd say even most people in Germanys long term unemployment scheme which are not already working part time (Aufstocker) have severe mental and physical health problems. More pressure isn't going to help those people but it's the current Government's shtick.
I'd say UBI would make it easier to find people working in demanding jobs because you could to them part time, so they don't wear you down as much. It's much easier to work as a nurse for 20 hours a week.
I also took the route of finding a new hobby (biking, all things bike mechanics, even politics) but of course it's not paying any of my bills. That's the point. While I helped making other people very rich, I never owned shares or got a bonus after an exit.
A couple of years ago Bloomberg reported about spy chips/hw backdoors in SuperMicro mainboards but to my knowledge without a smoking gun proof. Maybe they had to settle outside of court and also had to sign papers to help protect the company from further damage in the future. Using (other) Bloomberg material may have triggered this. Of course this is a wild speculation. I have no evidence or insider knowledge.
I enabled DNSSEC a couple of years ago on my self hosted powerdns setup. I sign the zone locally, than build docker containers via SSH on the target nodes.
I made a mistake once and signed with wrong keys which then broke DANE. It‘s good to validate your DNSSEC (and DANE, CAA etc.) setup through external monitoring.
The key rollover part is what kills me about DNSSEC. I deal with key rotation in other contexts and it's already annoying, but at least if I mess up a TLS cert renewal the worst case is a browser warning. DNSSEC KSK rotation goes wrong and your whole domain stops resolving. And the old DS record is cached upstream so there's no quick fix.
> The key rollover part is what kills me about DNSSEC.
Key rollover is completely optional with DNSSEC (unlike with TLS where it's semi-mandatory). All of my domains use infinite lifetime DNSSEC keys, which probably isn't ideal from a security perspective, but it's still much better than no DNSSEC at all.
> but at least if I mess up a TLS cert renewal the worst case is a browser warning.
If you have HSTS enabled (which you probably should), then you're unable to bypass the browser warnings, so if you have a bad TLS certificate, then you'll be completely unable to connect to the website.
At least the error goes away immediately, for everyone, once you fix the cert.
.net seems to serve DS records with at least 18 hours TTL. so worst case it takes your monitoring up 18 hours to notice your record was broken, and then another 18 hours before your fixed record is server everywhere.
Aren't you supposed to keep the old and new KSK records for a while? Sorry if it's a dumb question since I don't regularly do this myself.
Worst case you can put the old records back until you figure out how to generate the new ones correctly, right? (Assuming it's not too close to the expiry time)
Maybe that could help a little, but on the other hand, there are just no more IPv4 addresses at RIPE. And European businesses seem to be very hesitant at adopting IPv6.
It's about decentralization, and IPv6 adoption is very high in Europe. Resilience means to know how to network. A large enthusiastic community of amateurs leads to skilled professionals.
I don’t want to speculate who is behind that. Clearly some SaaS shops are way overpriced but this is in no way the end of the business modell. Some contrarian will find the right timing to counter play and become more wealthy…
By using an external service, people outsource problems. Using agentic coding to „clone“ a service by naively specifying the features (not the implementation) will insource the problem. If the problem is static, separated, well understood and used internally only, it may be okay to do so. In other circumstances I highly doubt it. SaaS markt will come back stronger once people suffered enough pain in doing „the app myself“.
UBI makes it even harder to find people for that kind of jobs. Not paying any social benefits and increasing the pressure on the unemployed to take these jobs is much more interesting for everyone that is not unemployed. Please don't judge me for writing this. It's the feeling I have, not my view.
reply