3 ms·
For a paid account this is utterly unacceptable. For a free account I can kinda understand it, although it'd still be nice to get some automated explanation. An
by mcv 6y ago
For a paid account this is utterly unacceptable. For a free account I can kinda understand it, although it'd still be nice to get some automated explanation. An automated system that can't provide a good reason to disable an account, shouldn't be disabling accounts at all.
If this is a thing that happens at Github, I guess that's another reason to check out Gitlab instead.
- vorpalhex 6y agoAge and activity matters here too. There are plenty of developers who have never paid github but do endlessly important work through it. At the very least flag these accounts for human review.
- joepie91_ 6y agoAnd this sort of thing is why some of us have been endlessly warning that it's probably a bad idea to centralize all of the open-source ecosystem onto a single centralized, proprietary, commercial platform. Not that those warnings were heeded, of course, as usual.
- villgax 6y agoThis
- codegeek 6y agoTechnically git is free and you can self host. The issue is that the power of money cannot be ignored. Github has become the defacto centralized OSS ecosystem because it is free and can afford to be free due to the money they have. I would argue that we should encourage more platforms (paid) that can host git and not just depend on github or gitlab. But those 2 are successful because they were some of the early ones and then got a lot of money/funding. There may be other alternatives but no one wants to put their code with a small risky company that may not exist tomorrow. IF we can solve that problem, I think we will be ok.