3 ms·
I might argue that Slack has no interest in anyone's inner workings. I've been at companies building relatively uninteresting products that treated Github like
by briandear 10y ago
I might argue that Slack has no interest in anyone's inner workings. I've been at companies building relatively uninteresting products that treated Github like it was the same as emailing source code and server logins to the competition. I could be wrong, but I have never heard of a single instance of a company on Github having code stolen because it was on Github. I have heard of many companies who have had their internal systems hacked.
I might trust Github more simply because their entire product and value proposition is built around the use case of storing code while some company that builds a restaurant app -- their primary business isn't building code storage infrastructure. So why add operational overhead because of unfounded paranoia?
Unless you're running your own metal in your own data center, there's always 'risk.' Even then, if your system is connected to the internet there's still risk.
Proper risk management isn't "paranoia all the time," but an evaluation of the degree of harm posed by a particular hazard along with the likelihood of that hazard occurring. Then mitigating that risk in a way that is commensurate with those variables.
- shanemhansen 10y agoGitHub delivered the wrong source code to people for a while. https://github.com/blog/2273-incident-report-inadvertent-private-repository-disclosure https://github.com/blog/2273-incident-report-inadvertent-pri... I'm not bashing GitHub, but some people find more value and less risk in using git in its "native" distributed mode.
- taylorfausak 10y agoI think it's a little misleading to call that "a while". The post says "156 private repositories" were affected during a "ten-minute window" representing "0.0013% of the total operations at the time".
- eeZah7Ux 10y ago> Proper risk management isn't "paranoia all the time," but an evaluation of the degree of harm posed by a particular hazard along with the likelihood of that hazard occurring. Risk analysis: using online DVCS/bugtracker/chat service you are one compromised password away from letting an attacker read the whole contents and potentially alter them. Many of those passwords will be stored in browser. Browsers are known for being softer targets compared to servers, generally speaking. Contrast this with an on-premise services: You still have login credentials but also require people to badge-in to access the building and login on the desktops or start a VPN (often requiring creds and 2fa).