For context, I operate a product that Microsoft doesn't like (I have received cease and desists in the past and Microsoft even had LinkedIn shut down our LinkedIn pages).<p>As a precaution, I left Github when the rumors of Microsoft's acquisition began floating around.<p>My question for everyone is-- do you think Microsoft poses a risk for Github users? I can certainly imagine Microsoft leveraging their legal team to C&D my code if it were on Github or worse, or am I being too paranoid?
I would venture a guess that the division of MS that issues C&D letters is probably 5 steps away from leadership at Github that could implement something like suspending your github account and removing access to repositories. THe ol' one hand doesn't talk to the other type of thing.<p>That being said, if you are doing something that is attracting the attention of a legal department of a Fortune 15 company, my guess is your customers would flee to competitors if they knew that.<p>Host your code elsewhere (gitlab?) and retain legal counsel that can help you navigate this. Asking internet strangers for advice isn't likely to be beneficial.
In general, no, MS and Github exist to sell services. They are not a danger to people who use their services. But it sounds like you are doing something that they consider to be sketchy, so for your specific scenario we cannot answer your question unless you tell us exactly what you are doing.
Under Microsoft's leadership the various cease & desist orders and shutdowns went certainly worse than under the developers friendly Nat Friedman.<p>Now they hit hard first, similar to Google or other non-developer friendly services.
Corporate takeovers always come with uncertainty, and Microsoft has shown it is not shy about enforcing its interests. Treat GitHub as a public distribution channel rather than your primary repository. Use self-hosted Git instances or platforms like GitLab for your core work. Automate your deployments to push code to multiple places so that no single platform has full control over your code.
I think the more important question is "Does Microsoft pose a risk to me as a GitHub user?" and to that, I'd answer yes.<p>GitLab is another option. You could use GitHub as a primary and have GitLab prepped as a fallback, and mention it on your GitHub project.
is it worse than <a href="https://github.com/massgravel/Microsoft-Activation-Scripts">https://github.com/massgravel/Microsoft-Activation-Scripts</a> ?
I don't think they gonna go the C&D route. It's much smarter to have some random "anonymous" person file a DMCA complaint, which has the same effect with zero legal exposure or risk.<p>But yeah, never have the lifeblood of your company's assets on GitHub. From an international perspective they're basically legally untouchable unless you have billions in cash laying around to go up the courts unless SCOTUS eventually decides in favor of them anyways.
There's the general risk of enshittification that is almost guaranteed to occur.<p>There's specific risks based on your software or you. If your somehow prone to tripping their alarms then you will always be a hot target for bans especially automated and AI-driven bans. If someone is taking action to prevent your software spreading then the platforms will probably side with them unless you win some legal action or settlement.
You have had cease and desists notices in the past in regards to the product. It is hardly a deep conspiracy to think they will send the same notices to other platforms; irrespective of if they own them or not.<p>The real "danger" when it comes to GitHub is their success and the mainstream nature of the product - they are very unlikely to tollerate any questionable content.<p>As has to be pointed out far too often, when it comes to court orders - CEOs (especially those who are billionaires) will NOT select the option of "go to jail" over complying with court orders.