Re:Major Facebook security hole lets you view your friends’ ...
by nostrademons on Wednesday May 05, 2010 @01:09PM
(#1321773)
Well, a lot of this is the flip side of FaceBook's "changes are pushed to the live site as soon as they're checked in" policy. That lets them innovate quickly, but also means that whenever anyone screws up, it's immediately visible in a very public way. Other companies have release processes and QA procedures to stop this.
Re:Major Facebook security hole lets you view your friends’ ...
by u238 on Wednesday May 05, 2010 @02:38PM
(#1322083)
Every single line of code is peer reviewed by at least 2 people before it can be pushed.
Re:Major Facebook security hole lets you view your friends’ ...
by studer on Thursday May 06, 2010 @06:36AM
(#1324081)
But tested by nobody?
What happens to the reviewers that let this thing slip through, btw?
Re:Major Facebook security hole lets you view your friends’ ...
by MartinCron on Wednesday May 05, 2010 @02:31PM
(#1322058)
On the whole, I think the rapid innovation model tends to make things safer overall. Tiny changes can be rolled back more easily, or patched more easily.
Release processes and rigorous QA procedures seem more appropriate for client-deployed software like operating systems than for centralized web applications.
Re:Major Facebook security hole lets you view your friends’ ...
by derwiki on Wednesday May 05, 2010 @03:31PM
(#1322255)
From chatting with a few Facebook engineers, I'm pretty sure it's not quick to get checked in code -> production (unless it's super urgent)
Re:Major Facebook security hole lets you view your friends’ ...
by noodle on Wednesday May 05, 2010 @03:27PM
(#1322241)
so you're proposing that if someone doesn't like software bugs that they should stop using software?
that would be mighty difficult, as software and their potential bugs are present in most every facet of modern life.
Facebook, like all other software, is bound to have bugs. If you don't want your personal information/conversations to be exposed by a potential bug I'd suggest not using the service.