Earlier quoted context omitted.
It would be nice not to have to rely on centralized servers at all. A P2P/torrent client built specifically for sharing code from git repositories, perhaps?
IPFS, anyone?
Yeah, I'm hyped too.
GitHub had connectivity problems
51–60 of 175 posts
Re: GitHub had connectivity problems
#52Earlier quoted context omitted.
It would be nice not to have to rely on centralized servers at all. A P2P/torrent client built specifically for sharing code from git repositories, perhaps?
But there is much less commercial incentive behind a p2p alternative. Centralized services are easier to monetize. I look forward to the day governments start to fund free software, for example through the GNU project. Then we'll all have better tools. Actually, there were already some fundings. Germany funded GnuPG to port it to Windows. What do I care what is the new world record in sprinting? But I very much do ca…
Hear, hear. I've talked about this with people and it's surprisingly hard to convince them that government-sponsored software is a good idea. While a tiny fraction of the amount we already spend on commercial software would utterly transform the free software landscape, it's not politically viable as long as commercial software vendors have lobby power.
Re: GitHub had connectivity problems
#53Earlier quoted context omitted.
If only git were a distributed version control
It would be nice not to have to rely on centralized servers at all. A P2P/torrent client built specifically for sharing code from git repositories, perhaps?
> A P2P/torrent client built specifically for sharing code from git repositories, perhaps?
Or, we could both set up HTTP servers on our respective machines and simply push to each others repos.
Re: GitHub had connectivity problems
#54Well that's me not able to work.
If only git were a distributed version control
Oh cool, I didn't realize git being distributed solved the communication problems that arise on an engineering team.
Back to work everyone, git is distributed version control so we don't need pull requests or gists or any kind of easy-to-read historical record that is also accessible for non-engineers.
Re: GitHub had connectivity problems
#55Earlier quoted context omitted.
Yeah my first reaction was it is government based and probably China. I know, we should keep building up their economy by manufacturing nearly everything there, that should stop them.
Over the long term, it will. An educated wealthy populace doesn't accept tyranny for long.
To some extent, most likely, yes. But my perspective on the PRC is that the powers that be know that they will only remain in power for as long as they can provide, or rather, the illusion of them providing, a continuous increase in wealth. This in part would be why information is key in China. Assange had a very positive view of it when he said "I often say that censorship is always cause for celebration. It is always an opportunity, because it reveals fear of reform. It means that the power position is so weak that you have got to care about what people think." [1].
[1]: https://wikileaks.org/Transcript-Meeting-Assange-Schmidt#996
Re: GitHub had connectivity problems
#56Ugh, how horrible! DDoS'ing github is like kicking a puppy in the face.
Re: GitHub had connectivity problems
#57[deleted]
Re: GitHub had connectivity problems
#58I haven't experience any connectivity issues on Github today. Just pushed some code and it worked fine and promptly.
Re: GitHub had connectivity problems
#59Ugh, how horrible! DDoS'ing github is like kicking a puppy in the face.
Github has certainly done an amazing PR job if that is a common perception.