I am astounded that the maintainer and inventor of Wireguard is in this position.
Microsoft even supports Wireguard in Azure Kubernetes Service.
Maybe time for a custom license that would require M$ to sign up for special T&Cs if they want to use this software?
Who cares if it's OSI-approved or not, a line saying "M$, Google, and the like need written permission for every use case" would help to make those leeches honest. Just learn from the JSLint example.
It's got a lot of analogy to restaurants banning Uber delivery for not handling their food to their standards.
Agree. Single point of failure. One developer, one account. Crazy.
Is this another example of their old modus operandi:
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
?