5 ms·
Bejar said Facebook is looking at ways to avoid sending the data altogether but that it will “take a while.” Maybe I'm naive, but why would turning off the gat
by lpolovets 15y ago
Bejar said Facebook is looking at ways to avoid sending the data altogether but that it will “take a while.”
Maybe I'm naive, but why would turning off the gathering of information take a while? This reminds me of unsubscribing to email newsletters, where the final goodbye says something like "you should stop receiving our emails within 6-8 weeks."
- jurjenh 15y agoI wonder if that involves something like collecting the data and storing it locally on your computer, then only sending the data once you log into facebook...
- rwolf 15y agoNot how cookies work. Visit any page with loads the facebook like widget iframe/img/script -> make a request to facebook with your cookie.
- jurjenh 15y agoI was thinking more along the lines of a local store, but then you'd need a little script embedded into every page to handle the storage. Essentially, instead of FB like widget -> request to facebook I would think FB like widget -> add to local datastore. Then FB could do an optimised/aggragated query on the local database. The only thing would be that it would introduce large latency in the resulting data if its sent back only on FB login.
- pork 15y agoThat's a micro/premature optimization at facebook's scale.
- mnutt 15y agoAny code changes take a non-trivial amount of time. It sounds like the solution is to delete more of the cookies on logout, but there may be other Facebook services that use them and need to be transitioned away.
- cbs 15y ago>Any code changes take a non-trivial amount of time Thats a awfully cautions attitude and smells like a huge cop out for the well known fly-by-the-seat-of-your-pants commit to live strategy that facebook has.
- pork 15y agoWhatever you've read, Facebook likely has a non-trivial push strategy, just like everyone else. Nobody at their HQ is committing directly to the live site.
- cpeterso 15y agoFacebook's Release Engineering blog says a code change can go from commit to live in less than 60 minutes. Admittedly, they don't say how often they deploy. https://www.facebook.com/note.php?note_id=59150988919 https://www.facebook.com/note.php?note_id=59150988919
- lbrandy 15y agoCode changes are easy at facebook. Messing with domains/cookies/security/static-resources/etc is more than a code change.
- mnutt 15y agoI don't work there, but where I work we deploy 10-20 times a day and if somebody asked me to change the way we store data in cookies, it would probably take a bit of time to roll out. I'm only defending them because it annoys me when people who aren't familiar with the software internals tell me "this is a minor change, it should take you less than an hour".
- 0x12 15y agoTo be fair though, not doing something is a lot easier to implement than to add new functionality. As a minimal implementation they could err on the safe side and stop tracking everybody for a bit until they've corrected their error.
- yason 15y agoWell, he didn't say not only turning it off would take while. He said looking at ways to do it would take while. Speaking in such weaselese I'm not entirely positive they would ever get close to the actual turning off phase.