31–40 of 141 posts
Seems it’s been a busy week for these reminders not to trust centralized services. I think the the “Fediverse” will become more popular over the next few years.
There are in fact people who are already trying to "federate" code collaboration https://nth.io/notice/7652
From being on the other side of this kind of "big company screws little guy for no reason"... In ~80% of cases, there is more to the story than meets the eye. For example maybe a legal complaint came in, or someone was DoS attacking that repo and it put the whole GitHub service at risk.
Jason Rohrer [1] is the author of Passage [2]. His latest game, "One Hour One Life" [3], is a massively multiplayer online game where your character has only one hour of life. You start off as a baby and are dependent on others for shelter and heat before you're able to be autonomous. Eventually you die of old age but your impact on the world/server persists. I recommend anyone interested to purchase the game [4] or…
He's also idiosyncratic in the approach to the rest of his life. When he practiced ‘simple living,’ in his front yard he had (or still has?) a small wild garden with uncut grass, where he of course walked barefoot and his children played naked (iirc). He was taken to the court by neighbors on the issue of grass, and appeared there with a tome of paper citing local laws and research that says cut grass exudes harmful…
Earlier quoted context omitted.
There's always two sides to a story. That being said, it seems like every other week now there's a story of a cloud service or provider shutting something down or removing something, without our with very little notice, and the only recourse for somebody who cannot afford an army of lawyers is calling them out on Twitter and hoping for the best. This is an alarming trend, and highlights how decentralization and, at t…
> This is an alarming trend This has always been the case, ever since BBS operators. Data on other people's machines is data on other people's machines.
The only lesson to be learned here, one that needs to be repeated time and time again: Don't put all your eggs into one basket.
And... Use Gitlab
From being on the other side of this kind of "big company screws little guy for no reason"... In ~80% of cases, there is more to the story than meets the eye. For example maybe a legal complaint came in, or someone was DoS attacking that repo and it put the whole GitHub service at risk.
so in 20% of the cases it really is a big company just screwing a little guy for no reason?
Setting up your own git remote takes minutes. Github is just a pretty interface with bells and whistles. I think more people should go self hosted. It's cheaper, and none of the features are truly needed.
Maybe none of the Github features are useful to you in how you use it, but I find Github the most productive way to work with a distributed dev team that I've ever found by a large margin. It's an amazing system for productivity of large dev teams and a dream to work with if it fits your use case.
The biggest feature for me is the whole Pull Request flow with integration between filing the original issue, the code changes to fix it with inline code reviews and tracking everything through to a release all with a few clicks. And all of it is in a format you can link to in an email or drop into a chat, even referencing the specific lines of the diff you care about. It's really an amazing system that most of us take for granted.
Different people have different needs. And for a lot of people, git itself is just the (excellent) engine but really they want a whole car.