4 ms·

I assume all private stuff on Github would be leaked at some stage and change my behavior accordingly. You have to code as if someone you don't want will be rea

I assume all private stuff on Github would be leaked at some stage and change my behavior accordingly. You have to code as if someone you don't want will be reading it. Same goes for any service advertising their service as 'privacy aware'. How do you audit those claims? I mean Whatsapp is closed source for example and could be intercepted without you knowing, despite all their claims of 'privacy by design using E2E encryption'. Whatsapp also leaks metadata which can be even more detrimental to privacy instead of mere content leaking out. You have to assume all secrets will be leaked (by whatever means) and change your behavior.

itslennysfault 5y ago
Honestly, any illusion of WhatsApp being secure went out the window when the original founders left, leaving billions on the table, and then donated millions to Signal. I think that was a pretty clear indicator that privacy/security of WhatsApp was over.
FastEatSlow 5y ago
> You have to code as if someone you don't want will be reading it. This reminded me of "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live."
- gumby 5y ago
  Sorry, have we worked together?
  - FastEatSlow 5y ago
    On the off chance that's not sarcastic, I doubt we have.
    - gumby 5y ago
      don't worry, it was merely a lighthearted comment about some of the people I have worked with in the past.
zeven7 5y ago
> You have to code as if someone you don't want will be reading it. That should be standard practice no matter where your code is, Github or not.
coldpie 5y ago
> I assume all private stuff on Github would be leaked at some stage and change my behavior accordingly. This is good, but should be expanded to all online information. If you have something on the Internet, you should assume it can become public at any time. There is no such thing as computer security, and we need to stop pretending that there is.
ravenstine 5y ago
The only reason I have private stuff on GitHub is because, last I remember, they don't have an "unlisted" option. If I needed a repo for anything seriously proprietary, I wouldn't use GitHub for that.

itslennysfault 5y ago

Honestly, any illusion of WhatsApp being secure went out the window when the original founders left, leaving billions on the table, and then donated millions to Signal. I think that was a pretty clear indicator that privacy/security of WhatsApp was over.

FastEatSlow 5y ago

> You have to code as if someone you don't want will be reading it. This reminded me of "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live."

gumby 5y ago
Sorry, have we worked together?
- FastEatSlow 5y ago
  On the off chance that's not sarcastic, I doubt we have.
  - gumby 5y ago
    don't worry, it was merely a lighthearted comment about some of the people I have worked with in the past.

zeven7 5y ago

> You have to code as if someone you don't want will be reading it. That should be standard practice no matter where your code is, Github or not.

coldpie 5y ago

> I assume all private stuff on Github would be leaked at some stage and change my behavior accordingly. This is good, but should be expanded to all online information. If you have something on the Internet, you should assume it can become public at any time. There is no such thing as computer security, and we need to stop pretending that there is.

ravenstine 5y ago

The only reason I have private stuff on GitHub is because, last I remember, they don't have an "unlisted" option. If I needed a repo for anything seriously proprietary, I wouldn't use GitHub for that.