5 ms·
> Think of it: my Facebook friends lists has EU and US people in it. This list can't reside in EU or US. I think you're misunderstanding the ownership of the d
by simonh 11y ago
> Think of it: my Facebook friends lists has EU and US people in it. This list can't reside in EU or US.
I think you're misunderstanding the ownership of the data, hence the down votes. If I as an EU citizen create a private friends list like this, that list belongs to me. If I live in the EU but create the list using a US service with servers in the US, there is no problem. US privacy laws apply. If I create the list using an EU service on EU hosted servers there is no problem, EU privacy laws apply. However in this second case if the internet service company wants to transfer the list from their EU servers to their US servers without my explicit permission, that's a problem.
- estefan 11y agoI think the parent is getting at if you're in the EU and your data cannot be transferred to the US, and a friend in the US has data that cannot be transferred to the EU (if they were to follow suit) you wouldn't be able to create a list of friends in both localities because of the restriction to send data around, without incurring intercontinental latencies. Obviously the list itself could reside in either location, but the service provider would need to perform an intercontinental join each time you wanted to view the names of friends in your list.
- weddpros 11y agoThank you! You got my point.
- estefan 11y agoWhere it gets really tricky is caching. Say you do your intercontinental join but then want to cache HTML fragments for performance, well, is that classed as "transferring data" because technically it is...
- buro9 11y agoI think it will be reasonably argued that data in this context is the master record. The source of truth to which queries are sent. A cache is not that, and you need only look at something like the EU e-commerce directive to find exceptions for caches and networks on the basis of being a "mere conduit" for the communication. It is not as if the data is now toxic and cannot be cached or communicated outside of the EU, only that the data must be stored in the EU and should not be replicated to any database or storage outside of the EU that would prevent EU privacy law taking effect. That's important as EU privacy law already has enough exceptions to allow reasonable scenarios like caching to function. And if you are going to say "well I could just query my cache", then I'd suggest that if your cache is able to do much more than a single key|value lookup to retrieve the cached item then it is in fact a database you'd lose the protections of being a cache and you're back in the world of not storing EU data outside of the EU.
- weddpros 11y agoThat still means changing the whole architecture of Facebook, Tweeter and the likes... from a replicated system to a cached geo-centralized system. Also, it doesn't bar the NSA from consulting the information from the USA... which is supposed to be the goal of the whole thing. Actually the only way to surely block the NSA is probably to disconnect Europe from the Internet. LOL
- simonh 11y agoBut user names in e.g. Facebook aren't private information, they are explicitly public. As are messages you publish to people. That's just not an issue. The issue concerns private information associated with your account that you have not chosen to share such as your personal phone number, physical address, date of birth, etc. Of course if you send that information around in public messages that's your problem, but if you keep it in your account, then the company, such as Facebook, transferring that account information to the US it is a problem.
- DanBC 11y agoMy name is private data and should be treated as such. Companies need to have my permission to gather my name, and they need to tell me what they use it for and how long they store it, they should not gather it if they don't need it, they should store it securely, they should not share it with other people without getting my explicit opt-in. That doesn't make it impossible for Facebook to do business. It just means Facebook needs to be more careful with what they gather and store.
- Tyr42 11y agoI don't think that's how it works, as whenever you post anything your name shows up with it, with a link to your profile. I don't think you have any expectation of privacy with respect to your name, not anymore than a profile picture.
- Aloisius 11y agoI don't know. The EU's own website[1] on data protection refers to your name and photographs as private information that is subject to privacy protection laws. Relevant quote: > Individuals regularly disclose personal information such as their names, photographs, telephone numbers, birth date and address while engaged in a whole range of everyday activities.This personal data may be collected and processed for a wide variety of legitimate purposes such as business transactions, joining clubs, applying for a job, and so on. > Nonetheless, the privacy rights of individuals supplying their personal data must be respected by anyone collecting and processing that data. [1] http://ec.europa.eu/justice/data-protection/data-collection/index_en.htm http://ec.europa.eu/justice/data-protection/data-collection/...
- weddpros 11y agoImagine I'm in the EU, and Facebook wants to store my data in the EU. But I'm friend with US people. So I'm in their own friend list too, which is stored in the USA. So my data is needed in the USA too. When I publish something in Europe, my friends needs to see it too in the USA. And you can't build a Facebook wall with intercontinental latencies. You need replication. It's a social graph, and you can't split it between US and EU: data has to be replicated across borders (or face massive latency and bandwidth).
- jarek 11y ago> And you can't build a Facebook wall with intercontinental latencies. I have yet to see a Facebook wall in under 0.133 seconds, I'm not sure intercontinental latencies are the biggest problem in web performance these days...
- weddpros 11y agoAre you suggesting hosting a web app in the USA and its database in Europe makes no difference? There's also the problem of bandwidth (if you can't cache data locally).
- jarek 11y agoNo, but I would suggest that it's not a dealbreaker. Again, bandwidth pales in comparison to megabytes of Javascript and images getting pushed all over the place. On my nearly-blank test account loading Facebook.com fetches ~4 MB, including ~3 MB of Javascript with instructive names like https://static.xx.fbcdn.net/rsrc.php/v2/y0/r/64jGxSfxJ36.js https://static.xx.fbcdn.net/rsrc.php/v2/y0/r/64jGxSfxJ36.js and https://static.xx.fbcdn.net/rsrc.php/v2/yp/r/K6ojr4ngQRr.js https://static.xx.fbcdn.net/rsrc.php/v2/yp/r/K6ojr4ngQRr.js In face of that, suggesting having to store some data 0.05 s away is problematic is a bit of a waffle
- lucian1900 11y agoThe latency would be incurred several times when loading a single wall. As an experiment, take a moderately complex web app and deploy it in a different continent from the database it connects to.
- forrestthewoods 11y ago"that list belongs to me." Those words don't actually mean anything.