31–40 of 77 posts
Earlier quoted context omitted.
I've never written a web app that actually deletes data. Sure, but that's just a business decision, right?
It's often a performance, scalability, and safety decision as well. The optimal way for a web app to truly delete data is during an asynchronous garbage collection process. It's a lot easier to just mark the object as deleted.
Earlier quoted context omitted.
Any 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.
>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.
Earlier quoted context omitted.
Not how cookies work. Visit any page with loads the facebook like widget iframe/img/script -> make a request to facebook with your cookie.
I 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 sen…
The company says the data is sent because of the way the “Like” button system is set up; any cookies that are associated with Facebook.com will automatically get sent when you view a “Like” button. They have a point. This is going to be the same for any site that has static content served elsewhere with cookies attached to the domain. Hot link to an image on my blog you commented on? OFFLINE DATA GATHERING ZOMG.
Hotlink an image? That's now how the Like button works. It's more like linking to an IFRAME with its own javascript . Slight diff.
This is a great example of the inherent conflict of interest when your users are not your customers, in fact they're your product. http://johnstanderfer.com/2011/09/26/facebooks-most-importan...
How about if browsers implemented this cookie system: Each time a cookie is set, you could have the ability to mandate when that cookie is sent out. For example with a Facebook cookie you could tell the browser to only send that cookie when your address bar reads facebook.com. Problem solved?
Earlier quoted context omitted.
Why do the cookies need to exist? If I log out from your service, why do you need to keep a cookie on my computer?
Hell, HackerNews leaves a cookie on your computer after you log out with some opaque blob holding who-knows-what. Users like to complain about cookies when you bring them up, but generally can't seem to bother. Including the two of us.
Their defence doesn't hold much water. But then, I can't imagine any excuse that would satisfy me. They say “The onus is on us is to take all the data and scrub it,” said Arturo Bejar, a Facebook director of engineering. “What really matters is what we say as a company and back it up.”, except their track record on that matter isn't exactly stellar. We know they don't actually delete messages or things you delete on…
What if you delete your account entirely? Do they delete your data then?
How about if browsers implemented this cookie system: Each time a cookie is set, you could have the ability to mandate when that cookie is sent out. For example with a Facebook cookie you could tell the browser to only send that cookie when your address bar reads facebook.com. Problem solved?
They do.. it's called disable third party cookies.
What I'm talking about is the ability to limit when cookies as sent out with requests. Privacy wary users could perhaps have their browser set so that for example Facebook cookies are not sent to Facebook just because you're visiting a website that has code from Facebook on it, but only when you're actually browsing Facebook.