| |||||||||||||
Github compromisedGithub compromisedPosted Mar 5, 2012 18:33 UTC (Mon) by mpr22 (subscriber, #60784)In reply to: Github compromised by wahern Parent article: Github compromised I value the presence of a public git respository for the (small) project I host on github more than I value USD7 a month, but less than I value not having the burdens associated with running my own server.
(Log in to post comments)
Github compromised Posted Mar 5, 2012 20:19 UTC (Mon) by wahern (subscriber, #37304) [Link]
People who understand that managing a server is a burden are precisely the people who should be managing their own servers, if only to help ensure the right and ability of people to continue doing so.
The more people flock to web services, the less demand and necessity for interoperability and standards, _especially_ for non-HTTP services. It's a civic duty to run your own services for those who are capable. Those who are incapable, but do so anyhow, will continue doing so regardless.
Also, I hate to sound like a fanboy but running OpenBSD is significantly less stressful than Linux. For many reasons (simplicity being the biggest, IMO), and particularly for basic HTTP, SMTP, and SSH services. Upgrading is more difficult than a simple `apt-get dist-upgrade', but I've done remote upgrades bi-annually for the past 12 years without a single problem.
The best system administrators are software developers, because the developers understand how crummy most software really is. But for this reason software developers hate doing system administration. It doesn't bode well for the security of any web service, where system administration and software engineering become highly specialized positions.
Github compromised Posted Mar 5, 2012 22:53 UTC (Mon) by kleptog (subscriber, #1183) [Link]
While I could theoretically run stuff I want to share off my own server, I'm also realistic in that I know I won't be able to dedicate the time required to make it work. It's never just a server, to do things properly you need fail overs, backups, alternate sites, etc.
And then it's just way too much work required just to share a single Git repository. You're right, I don't like system administration much.
I do run my own server, but I run it for myself. I know the backups are irregular, that there's no alternative site. But if it breaks no-one else is affected.
The Github's of the world fulfill a need, that's why they're there.
All or nothing or something in-between Posted Mar 7, 2012 14:34 UTC (Wed) by pboddie (subscriber, #50784) [Link]
I don't know why people keep portraying this as a contest between hosting stuff on someone's service with all the weird terms and conditions and running your own server with you being responsible for absolutely everything from the (virtual) motherboard upwards. There are other options.
I remember looking into VPS hosting after deciding to move away from fairly simple static hosting, and after realising that I didn't want the hassle of having to deal with SSH port-scanning and the accompanying attacks and the like (it was a surprise that they left such issues to the average user), I ended up going with a shared hosting provider who gives SSH access, provides a reasonable OS distribution, and lets you install your own software. From that point, you can host repositories fairly easily if you can follow the instructions for your DVCS project of choice.
What hosting (and service) providers are missing, not just in this case but in the area of social networks and other services with a tendency to cultivate dominant providers, is the opportunity to offer convenient but interoperable services to a wider audience. Everyone wants to own the whole cake, no matter how small, instead of having a larger slice of a larger cake, which means that everyone has to watch as the behemoths take all the cake.
|
|||||||||||||