Agree. Single point of failure. One developer, one account. Crazy.

ptx 8 hours ago | parent | next [-]

Having multiple accounts wouldn't help, as Microsoft could easily suspend all the accounts of everyone associated with the project if any account looks suspicious. The single point of failure is Microsoft.

▲

pjc50 7 hours ago | parent | prev | next [-]

You're not actually allowed to avoid this by having multiple accounts, that falls under "ban evasion".

But yes, there's a lot of critical single maintainer projects.

▲

raxxorraxor 8 hours ago | parent | prev | next [-]

No, that is not the issue here. The source of the problem is something different. This is a wrong root cause analysis.

▲

jamesnorden 8 hours ago | parent | prev [-]

How would more than one account help in this scenario, exactly?

	▲	hirako2000 3 hours ago \| parent [-]
		Any account can sign any (same) piece of software. Of course Microsoft could detect the it's signing a software related to a banned signed and ban the new account. So veracrypt (and wireguard) is stuck. It's outrageous. MS is simply enforcing some Government crackdown on encryption software that would interfere with backdoors.