@LouisIngenthron I mean, that’s what someone from QOTO would say.
But marketers, especially of big companies, tend to be very paranoid of blowback and exercise caution.
I’m not saying that Microsoft owns dotnet.social.
But non-affiliation? I don’t buy that.
And clearly whoever owns dotnet.social works in lockstep with Microsoft’s marketing department—otherwise they wouldn’t put the account on that server.
@atomicpoet Or their marketing department tried to create an instance, saw how difficult it is to run on Windows, gave up, found a community instance already dedicated to their product run by an employee, reached out to him, and he was happy to have them, because of course he was if he was such a big fan that he started an instance dedicated to their product in the first place.
That's not only Occam's Razor here, but it's consistent with the story they've given.
And the unnecessary dig against my server isn't strengthening your argument; to the contrary.
@atomicpoet Or their marketing department tried to create an instance, saw how difficult it is to run on Windows, gave up, found a community instance already dedicated to their product run by an employee, reached out to him, and he was happy to have them, because of course he was if he was such a big fan that he started an instance dedicated to their product in the first place.