How often do we have these articles? Averaging once a month? Maybe more?
How often does it need to happen before people realise that your $10/mo means jack shit to a multi-million dollar company, and "accidents" like this are just a cost of business to them. Solving the problem properly would cost a lot more than just letting people fall through the cracks of automation.
well the beauty of git is that the entire repository is more than likely cloned in a few different places and is easily reproduced. Also makes it nice and easy to move elsewhere.
According to an earlier tweet [1], the reports are from users who are mad they were banned from his discord server. > Actually, it seems like this "report" to discord came on the heels of us banning a member for posting offensive content. That member then, to seek revenge, reported the entire server to Discord, and told us about it. Nice. I've experienced similar immature behaviour in the Minecraft community back whe…
I've helped run a forum in the past, and holy shit is it scarily easy to make stupidly-determined enemies. Even people who joined just to spam offensive content would act like they were the one victimized when banned and would do all sorts of things to "even the score". I think these people would emotionally forget that they joined looking for a fight and earned their ban in the first place, and would then ride the high of righteous indignation.
Don't put all your projects in one cloud And... Use Gitlab
Gitlab too had incidents, remember db backup fiasco ? I know few devs that lost issues and wikis that day. Just backup your repos once a year, lets not be paranoid.
Yeah sure. But since Gitlab is possible to run self-hosted, you can back up the entire instance from the public cloud to the self-hosted version. That's pretty great.
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.
> none of the features are truly needed I think ease of contribution and discovery shouldn't be underestimated. I find it hard to believe that our little project [1] would have had 90+ contributors, of whom ~8 made very substantial contributions, if we'd self-hosted it. The project would have been far lesser without those contributions, and I probably would have abandoned it out of lack of interest. That said, most o…
I've nothing to add to the conversation, but I would like the opportunity to thank you for Tridactyl. It makes the web usable.
That is terrible and a good reminder that using the "cloud" means that you don't really control your destiny. A quick googling around reveal a couple of options for backing up everything from github (but I'm not sure what you'd do with a backup if you got kicked out like the OP).
I think the reminder is just that backups are necessary, and cloud isn't a required condition. I had a bare-metal host turn off my server because they were concerned I was violating the trademark of a big company with what I was serving. That big company was my client and I had permission, but the host shot first and asked questions later (actually, I had to call them when I saw the site went down).
In such situations I tend to go onto the meta level and ask them that they realize what they are doing at that moment: looking perfect is more important to them than acting like a perfect neighbour. So something like: “I always thought of you as a good neighbour, because of your beautiful garden, but is complaining about your neighbours garden something a good neighbour would do?” Usually they never bother you again…
That particular phrasing comes across a mite hypocritical - if you admit that having a well-kept garden makes one a good neighbor, then you are admitting that your unkempt garden makes you a bad neighbor.
> if you admit that having a well-kept garden makes one a good neighbor, then you are admitting that your unkempt garden makes you a bad neighbor.
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?
The remaining 20% are usually incompetence or malice on the part of the big company...
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…
It would seem that he has some idiosyncratic neighbors, then. But they are not alone, a certain amount of people are strangely obsessed by the grass of their neighbors. My kids loved the dandelions of my grass and I let them grow, but then I received regular bullying by the old lady next to our place, who had a "perfect" french style garden, and looked at us as if we were some kind of savages. I actually found this b…
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.
and so you don't send an email?
Maybe they did, but the mail's stuck in a spam filter or sent to an old email address...
Maybe they tried to call him but he rejected the call?
Only the stories that sound unreasonable get viral attention.