Says the man always dragging his feet when time comes to support Ukraine’s self-defense

Does this attack scale linearly with key size?

Using the D-Wave Advantage, we successfully factored a 22-bit RSA integer, demonstrating the potential for quantum machines to tackle cryptographic problems

That attack is a threat only if it scale better than existing attacks.

Don’t forget the 15% minimum corporate tax. This now have to be turned into law.

Taxing individuals by itself cannot solve shortcomings in the tax system. The super rich have corporations and shell companies in tax heavens to avoid taxes.

This is a common issue in software, not limited to scripting. Software are getting more and more layers of wrappers/adapter code, like a Russian doll. It contributes to dependency hell, as each layer brings new dependencies.

Developers often find it easier to wrap existing apps and software, and add another layer on top, rather than improving or replacing what exists.

Okay, I misinterpreted your comment.

Having a backup at a cloud provider is fine, as long as there is at least one other backup that isn’t with this provider.

Cloud provider seems to do a good job protecting against hardware failure, but can do poorly with arbitrary account bans, and sometimes have mishaps due to configuration problems.

Whereas a DIY backup solution is often more subject to hardware problems (disk failure, fire, flooding, theft, …), but there’s no risk of account problem.

A mix is fine to protect against different kind of issues.

That would indeed be a good backup strategy, but better be specific. “Offsite” may be interpreted in different ways.

They had backups at multiple locations, and lost data at multiple (Google Cloud) locations because of the account deletion.

They restored from backups stored at another provider. It may have been more devastating if they relied exclusively on google for backups. So having an “offsite backup” isn’t enough in some cases, that offsite location need to be at a different provider.