@prologic@twtxt.net If you feel that strong about it I think this is enough of an abuse from M$ and Github. But despite of that, today we have great alternatives for self-hosting such as Gitea. But I also think Github gives a great exposure to projects that helps discoverability and bringing new collaborators.
@prologic@twtxt.net I can’t believe there isn’t a single question related to licensing in their FAQ; stinks of a list of planted questions, to me.
@ocdtrekkie@twtxt.net @prologic@twtxt.net Perhaps treating the Github project page as a Twitter™ account that some OSS project have where you can link to the real project source and have a Readme there on Github with a FAQ. I don’t know. But it is a bit of the story repeating itself, right? Some website comes around, looks inoffensive, everybody start using it, becomes relevant to what we do, and then, some company comes around and start to change rules and abusing it. I think the lesson is only one here: Take ownership of your identity and don’t rely in a centralized service.
@ocdtrekkie@twtxt.net @prologic@twtxt.net The only convenience that I see on Github (apart from the discoverability) it is that with one account I can create issues in any project. If we start hosting our code on our own Github like instances we will need to have an account for each instance. Which is a bit inconvenient (just a bit because we are likely to use a password manager and it would be set once and forget)