Re:Facebook’s Clear History privacy feature is still months ...
by tylerhou on Wednesday December 19, 2018 @12:57PM
(#18717685)
Or, maybe, making a product which has to deal with legacy code for billions of users is actually difficult?
Like, we know Facebook is evil, but they can’t be that evil, right?
Re:Facebook’s Clear History privacy feature is still months ...
by jandrese on Wednesday December 19, 2018 @01:48PM
(#18718158)
> Like, we know Facebook is evil, but they can’t be that evil, right?
People keep saying this and they keep being surprised.
Re:Facebook’s Clear History privacy feature is still months ...
by emilsedgh on Wednesday December 19, 2018 @04:07PM
(#18719630)
I don't know man when they wanted to generate a highlight video of new year's resolution for each user and they went from 0 to executed in a few days and blogged about it they seemed very capable people.
Re:Facebook’s Clear History privacy feature is still months ...
by CaptainZapp on Thursday December 20, 2018 @07:29AM
(#18724332)
I would call supporting genocide for years and helping to drown democracy in a number of countries (Hungary, Philippines, Cambodia, Sri Lanka among others) pretty fucking evil.
Blowing vile, antisemitic dog whistles from the very top level also doesn't do much in order to improve their image
Re:Facebook’s Clear History privacy feature is still months ...
by chillacy on Thursday December 20, 2018 @08:50AM
(#18724832)
This is event steam data, at what large tech company do you work for where you can possibly store that in a SQL database? At my current company our clickstream data is in the petabytes, Facebook has orders of magnitude more. It’s probably stored in HDFS or something, not too far from chronological flat files.
Re:Facebook’s Clear History privacy feature is still months ...
by makomk on Wednesday December 19, 2018 @01:01PM
(#18717721)
It's probably not just stored as gigantic combined flatfiles, but imagine what would happen if they launched this feature and it only actually deleted some copies of the user's browsing history.
It seems more likely to me that yes, they could do a DELETE FROM BROWSING_HISTORY WHERE USER = "%S", but that's not their business model. Instead they have to add a column to the database that flags data that will be shown to the user or not, and then go through every part of the site where the data might be visible and add a check for that flag. It's a lot more work, and worse they have to get it right the first time because people will be angry if there is a leak somewhere and their supposedly deleted data is visible.