# mrz....@gmail.com / 2014-09-09 12:27:03 -0400:
> On Sat, Sep 6, 2014 at 5:23 AM, Roman Neuhauser <neuhau...@sigpipe.cz> wrote:
> > you seem to be unaware that if you pay some money you can have "private"
> > repos in github.  those are accessible only to users authorized by you.
> 
> Lot of companies wouldn't allow their IP on servers they don't fully
> control, no matter how many guarantees that they're the only ones allowed
> to access it.

yes, and many do.  it's a matter of a kind-of SWOT analysis.  do you
distrust third parties with access to your code?  if you take it to its
logical conclusion you'll find you need to design and manifacture your
own hardware and software.  Intel may deny backdoors in their CPUs[1],
but that's no different from Github swearing they [dw]on't let others
see your code, is it?

[1] Cisco and others can't claim innocence anymore

> I'm actually surprised that companies actually do use github
> -- especially after cases like
> http://it.slashdot.org/story/14/06/18/1513252/code-spaces-hosting-shutting-down-after-attacker-deletes-all-data
> -- but I have to admit I know many that do and they seem to be happy.

well, i had never heard of codespaces.com until their shutdown was
publicized, and judging from the description of the breach they were
a fly-by-night operation.  github is in a different league.

at least with DVCSs complete version history remains with you even if
your hosting provider shuts down abruptly, so you lose established
processes but no data.  github lets you access all your data including
issues and whatnot programmatically so you can have backups away from
their infrastructure should the shit hit the fan.

-- 
roman

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to