So instead of making their system less-privacy-invasive (which I have seen no indication should be impossible wrt the APIs mentioned here), they just shut down services where this is regulated. Not surprised, but there's no way to spin this in a way that doesn't make Facebook look shady and bad. So much for "working with regulators".
To honest, I think this is probably the begining of the end for Facebook. I foresee that they'll be forced to reduce services in Europe repeatedly. It'll be interesting to see what takes its place.
Messenger API Updates for Europe
21–30 of 80 posts
Re: Messenger API Updates for Europe
#22Earlier quoted context omitted.
epd
Sorry but epd (ePrivacy Directive)[0] is from 2002 with last amendments in 2009 and has nothing to do with this. There's a draft for "ePrivacy Regulation"[1][2] introduced in 2017 that looks to replace ePrivacy Directive, but it's still in a draft and discussions stage. There's no guarantee it'll become a law. [0] - https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32... [1] - https://www.mckinsey.com/busines…
Source - worked on ePD compliance.
Re: Messenger API Updates for Europe
#23This is desperately short on explanation? The very high granularity suggests that some features are more privacy-invasive than others, but not why that is. (Also, listing the UK under EEA is .. complicated and subject to change in the next few weeks. https://en.wikipedia.org/wiki/Membership_of_the_United_Kingd... )
Re: Messenger API Updates for Europe
#24Earlier quoted context omitted.
That doesn't really say very much. What new rules? Why the API?
Just speculating, but it could be to do with the recent ruling that the EU-US Privacy Shield data sharing agreement was invalid https://easygdpr.eu/2020/08/privacy-shield-invalidated-what-... This means that data sharing between the US and EU is a lot more complicated, as the EU ruling basically says that US data protection regulations are not sufficient to comply with the requirements set out in the GDPR.
Re: Messenger API Updates for Europe
#25This is desperately short on explanation? The very high granularity suggests that some features are more privacy-invasive than others, but not why that is. (Also, listing the UK under EEA is .. complicated and subject to change in the next few weeks. https://en.wikipedia.org/wiki/Membership_of_the_United_Kingd... )
Re: Messenger API Updates for Europe
#26So instead of making their system less-privacy-invasive (which I have seen no indication should be impossible wrt the APIs mentioned here), they just shut down services where this is regulated. Not surprised, but there's no way to spin this in a way that doesn't make Facebook look shady and bad. So much for "working with regulators".
To honest, I think this is probably the begining of the end for Facebook. I foresee that they'll be forced to reduce services in Europe repeatedly. It'll be interesting to see what takes its place.
Re: Messenger API Updates for Europe
#27Earlier quoted context omitted.
Sorry but epd (ePrivacy Directive)[0] is from 2002 with last amendments in 2009 and has nothing to do with this. There's a draft for "ePrivacy Regulation"[1][2] introduced in 2017 that looks to replace ePrivacy Directive, but it's still in a draft and discussions stage. There's no guarantee it'll become a law. [0] - https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32... [1] - https://www.mckinsey.com/busines…
Sorry but you’re mistaken. The original ePD applied to messaging services, ie, SMS providers. What changed this year is that a few months ago the EU decided that providers like Messenger should be covered by the regulation too. Source - worked on ePD compliance.
Re: Messenger API Updates for Europe
#28Earlier quoted context omitted.
Sorry but epd (ePrivacy Directive)[0] is from 2002 with last amendments in 2009 and has nothing to do with this. There's a draft for "ePrivacy Regulation"[1][2] introduced in 2017 that looks to replace ePrivacy Directive, but it's still in a draft and discussions stage. There's no guarantee it'll become a law. [0] - https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32... [1] - https://www.mckinsey.com/busines…
Sorry but you’re mistaken. The original ePD applied to messaging services, ie, SMS providers. What changed this year is that a few months ago the EU decided that providers like Messenger should be covered by the regulation too. Source - worked on ePD compliance.
But I don't understand how ePD with no changes from 2009 can suddenly include Facebook and others? Unless there have been other regulations passed?
I can't find anything about ePD changes that forces Facebook to do this, all I can find is the upcoming ePR (ePrivacy Regulation) that will affect Facebook and others, but it hasn't been passed yet.
I haven't heard of any privacy/GDPR/ePD changes recently other than the EU-US Privacy Shield invalidation.
Is there anything I can read on the changes you're talking about?
Re: Messenger API Updates for Europe
#29So instead of making their system less-privacy-invasive (which I have seen no indication should be impossible wrt the APIs mentioned here), they just shut down services where this is regulated. Not surprised, but there's no way to spin this in a way that doesn't make Facebook look shady and bad. So much for "working with regulators".
It does say: "We are currently working to restore these features and will continue to update this document and the changelog section with the details as they are available." Doesn't this suggest that they aren't being shut-down?
> Unfortunately, our website is currently unavailable in most European countries. We are engaged on the issue and committed to looking at options that support our full range of digital offerings to the EU market.
and have done so for years.
Facebook's "currently" may be worth as much as the "engaged" and "committed" of those sites.
Re: Messenger API Updates for Europe
#30Earlier quoted context omitted.
What makes you think the APIs could be changed to comply? Maybe there’s no way to implement what they used to do legally.
You can see what API calls do not work on the listed page. Most of those should not require any privacy breaking features so it should absolutely be possible to implement them legally. They just don't like to do so.