That has also been implemented recently. With staged publishing the author must verify a new release with 2FA so automated attacks dont work anymore. Some human in the loop must verify a release.
I am wondering about the last part of glibc malloc. Isnt that exactly the problem reported for the last 10+ years with glibc? And the common solution is to use tcmalloc or jemalloc which hasnt these problems?
I would love to have a mode that I must use my long password to unlock my mac for security purposes. But when unlocked, use touchid as an alternative to my password for convenience.
So just the normal TouchID mode but not for unlocking the mac.
Oh there will be a lot of issues in the future because Germany says thst your company is in Germany because you work from there. So you have to do taxes in Estonia and in Germany. And prepare for a lot of tax issues if you dont have a good tax advisor.
I do understand why all these steps are required. And they are good. But how should zero-trust architecture solve that? You‘re still authenticated what the core problem is.
When you have a custom domain you can list @mydomain.com as sending domain allowing you every string before the at character. So that means you could use 50 different domains with infinite adresses on these domains.
The doomsday saying the past months that everyone will now vibecode a solution instead of paying for SaaS as a big logic error… These people could have switched to self-hosting an open source clone of any popular SaaS but they didn‘t! Why? Because they dont want to be the person maintaining this, so we should those people not self-hosting a free software now go one step further and also build those products?
The reverse. Argo gives better peering than any paid plan. Its the reason for the product‘s existence. They can use more costly peering that they couldn‘t use with their free egress model.
Even a 100% test coversge is far away from verifying all behaviour.