51–60 of 325 posts
Earlier quoted context omitted.
It something I would expect security hardware to have automatically stopped. Even an employee shouldn't be able to download 125GB of stuff without flipping a safety switch somewhere.
If the bulk of it is a git repo, it's probably expected that every engineer will download it regularly.
Earlier quoted context omitted.
Trying to protect against leaking developers/employees is like trying to protect against lone gunman terrorists: useless. And, if you try anyway, it is likely to cause more annoyance to everyone involved than actual protection (think TSA).
I disagree. Locking down and logging access to raw data like password hashes or payout information to only those who absolutely need it doesn't cause much annoyance and is very useful. It protects the company against rogue employees (not even strictly malicious, but also curious employees who want to see more than they should). It limits exposure if an employee's account gets hacked (my pet theory for this Twitch hac…
And you can try to prevent them from accessing live/real customer data, but the cost is that they will never be able to debug issues in production. Most companies, even very large ones, are just not able to pay that cost. Not to mention that once you have access to the codebase there are a million ways to leak customer data anyway -- it is a lost battle.
Earlier quoted context omitted.
>(which is more secure than the standard mobile app TOTP most of us use everywhere online). Is it though? The "wrench theory" applies here. It's not unthinkable that an employee was stalked on social media and had their key stolen.
Its still more secure. Rubber hose cryptanalysis applies to both equally, but that doesn't mean there aren't other attacks that apply to totp which don't to yubikeys. More secure != perfectly secure.
Someone actually started streaming going through the code ... on twitch. https://www.twitch.tv/deepfrieddev
Someone actually started streaming going through the code ... on twitch. https://www.twitch.tv/deepfrieddev
Too bad, it would be nice to see someone go through and document how Twitch works. I've never worked at "web scale" so I'd probably learn a lot.
Someone actually started streaming going through the code ... on twitch. https://www.twitch.tv/deepfrieddev
Someone actually started streaming going through the code ... on twitch. https://www.twitch.tv/deepfrieddev
Does it take a genius to figure out how to build twitch? It’s a modern crud app with video streaming.
Earlier quoted context omitted.
Everything is easy to build until a small nation state’s worth of people want to use it at once.
I work in a small nation state. That doesn't stop CV-hungry engineers from finding ways to overcomplicate it. (I do agree with you on this topic in general)