1. 10
  1.  

  2. 7

    Today’s edition of shared computers are shared.

    Since the MS acquisition, a lot of people have moaned about how MS is going to go into your private repo and steal your code. I think this is kinda unlikely for a few reasons, not least of which is the enormous liability that would be for them. MS may not be a good actor, but in this case I don’t think they are a “bad” actor.

    But there are bad actors, even less constrained by ethics, laws, etc. than MS. Nobody seems to consider how github’s model deals with them. Throw all the bits into a giant pile, then hope you can sort out who’s stuff belongs to who later? Perilous. Even if the github admins are saints, that won’t save you.

    1. 5

      Since the MS acquisition, a lot of people have moaned about how MS is going to go into your private repo and steal your code

      TBH, that’s the first time I’ve heard this. And it seems like a ridiculous argument to make, for the reasons you stated.

    2. 4

      Note to the reader: for new private repositories, forking is turned off by default. You have to explicitly allow people to make forks.