Surely they weren't keeping everything only on GitHub, and had locally stored copies, right? Right?
GitHub removes 5 years of One Hour One Life designer's work
131–140 of 141 posts
Re: GitHub removes 5 years of One Hour One Life designer's work
#132Earlier quoted context omitted.
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…
I don't care what my neighbors do, however cutting long grass helps prevent tick and flea infestations in my area so it does have a purpose. The ticks especially enjoy the long grass. I do however work towards planting more permaculture in my yard so that there's less grass to cut. The grass provides an excellent ground cover and builds up the soil in the meantime.
> cutting long grass helps prevent tick and flea infestations in my area so it does have a purpose
Not to mention helping to reduce the risk of rodent problems. Pest control and fire risk are the reasons why, in my city, your are legally required to keep your jungle down to a certain level.
Re: GitHub removes 5 years of One Hour One Life designer's work
#133From 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.
The irony is that Jason is the "big company screws the little guy for no reason" with his own work.
He licensed his work at "Do whatever you want with it, absolutely no restrictions, and no permission necessary.".
Then when someone started making money off his work, he turned around and started litigation.
Re: GitHub removes 5 years of One Hour One Life designer's work
#134removes without notice or consultation. 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.
Boycott is often the only solution. That's why those articles are important.
Boycott is not a solution. It's the first and very tiny step towards doing something. People need to federate, mutualise, fight as part of communities. Personal actions have as only upside making you feel good (which is still a big win, but it's pretty superficial and doesn't scale).
Re: GitHub removes 5 years of One Hour One Life designer's work
#135Setting 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.
The electricity company/ISP can still deny service.
That's not only far less likely, but far easier to fix -- if my ISP and/or utility company shut me down, it would be relatively easy to physically move my servers to a friends house until I can get the situation taken care of.
Re: GitHub removes 5 years of One Hour One Life designer's work
#136removes without notice or consultation. 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.
We are all Ford Pintos. https://en.wikipedia.org/wiki/Ford_Pinto#Cost-benefit_analys...
What an interesting story, especially when you delve into the links on tort reform
Re: GitHub removes 5 years of One Hour One Life designer's work
#137removes without notice or consultation. 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.
So what should we do? What price do we need to pay to exceed the "jack shit" threshold? Specific recommendations please.
Self host in multiple locations - either datacenters or cloud providers. Its the only way to be sure.
Re: GitHub removes 5 years of One Hour One Life designer's work
#138removes without notice or consultation. 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.
So what should we do? What price do we need to pay to exceed the "jack shit" threshold? Specific recommendations please.
Use GitHub and similar hosting only as a public gathering place for projects, not as the sole development repository. Which is to say, develop locally and ensure you have backups, only using GitHub to share the work with others.
This is the way development using git is supposed to work anyway.
Re: GitHub removes 5 years of One Hour One Life designer's work
#139Re: GitHub removes 5 years of One Hour One Life designer's work
#140Earlier quoted context omitted.
It’s probably a mistake done after refactoring. The guy is only human you know.
Magic strings and numbers all over the place are less likely to be refactoring artifacts. Of course he's only human, but it wasn't me who picked this little (80 LOC) file, of all the codebase, as an example of code being like "out of a book or tutorial" :) And what about stuff such as 20 KLOC in a single file? This is spaghetti, no matter how you spin it. I wouldn't want to work with such codebase.
It isn't really clear that splitting up your code into a bunch of files is always a good thing. Sometimes it becomes harder to search, for some people switching files incurs a sort of mental cost (like walking through a doorway), it can make compilation slower, and depending on your editor you might have to do some extra configuration to work well with your directory structure.