Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GDPR: Removing Monal from the EU

monal.im

Post reply on HN
Print view View original

731–740 of 957 posts

Re: GDPR: Removing Monal from the EU

#731

Post by izacus »

diminoten wrote: post #397
badsectoracula wrote: post #70

Earlier quoted context omitted.

If a business blocks EU citizens what will happens is that either another one who cares about GDPR will pop up and be able to work with both EU and non-EU citizens, or the business in question wont be that important in the first place. In either case, nothing will change for most people.

Maybe, but imagine if Google, Microsoft, Facebook, Amazon, etc. had decided to pull out of the EU. Not that any of them aren't replaceable, but providing the suite of functionality that any one of them does to their customers would not be a simple feat. "Second class citizens" might not be the right term, but would "segregation" be an appropriate term?

Except that Google, Microsoft, Facebook and Amazon have been at the table when GDPR was written and will be compliant with it. So it's a completely bogus argument.

Re: GDPR: Removing Monal from the EU

#732

Post by izacus »

maufl wrote: post #60

Please be nice to the developer. I didn't post it to shame him. I'm just very sad about the post because I was hoping to establish XMPP as the group chat in my family, of which half are iPhone users.

The developer has decided to spread misleading information and FUD about legislation protecting people. We shouldn't be "nice" to people deliberately spreading lies.

Re: GDPR: Removing Monal from the EU

#733

Post by poizan42 »

aembleton wrote: post #714
Angostura wrote: post #687

Earlier quoted context omitted.

I respect his right to do whatever he would like with his own hobby, but we should be clear that the guy is stating he doesn’t have the resources, based on a series of misunderstandings. So, for example, he says he is required to appoint a DPO. The U.K. Information Commissioner has this to say: >Do we need to appoint a Data Protection Officer? A> Under the GDPR, you must appoint a DPO if: > you are a public authority…

That's the UK's interpretation of GDPR. What about France or Poland, or any of the other countries? I suppose it depends where in Europe he would like to visit

I'm not seeing any interpretation being done here, but judge for yourself. Here is what the GDPR actually says (Art. 37 Designation of the data protection officer):

> (1) The controller and the processor shall designate a data protection officer in any case where:

> a) the processing is carried out by a public authority or body, except for courts acting in their judicial capacity;

> b) the core activities of the controller or the processor consist of processing operations which, by virtue of their nature, their scope and/or their purposes, require regular and systematic monitoring of data subjects on a large scale; or

> c) the core activities of the controller or the processor consist of processing on a large scale of special categories of data pursuant to Article 9 or personal data relating to criminal convictions and offences referred to in Article 10.

Re: GDPR: Removing Monal from the EU

#734

Post by zerostar07 »

hvidgaard wrote: post #728
zerostar07 wrote: post #252

Earlier quoted context omitted.

Having an app that is non compliant out there induces anxiety. Having 10-20 old or fire-and-forget projects out there, it's anxiety multiplied. There is a non negligible chance that One disgruntled or trolling user or competitor will report you to their country's DPA . There are 28 DPAs and they are not all as good and fair as Germany's or the UK's , they may fine you even if there is no good reason. Example: in my c…

Only the DPA of your country will handle complaints against you.

But for those outside the EU, any of the 28 DPAs can fine their company.

Also, i think the DPAs can fine any company in the EU, not just the companies of the country the DPA is in.

Re: GDPR: Removing Monal from the EU

#736

Post by raverbashing »

aembleton wrote: post #714
Angostura wrote: post #687

Earlier quoted context omitted.

I respect his right to do whatever he would like with his own hobby, but we should be clear that the guy is stating he doesn’t have the resources, based on a series of misunderstandings. So, for example, he says he is required to appoint a DPO. The U.K. Information Commissioner has this to say: >Do we need to appoint a Data Protection Officer? A> Under the GDPR, you must appoint a DPO if: > you are a public authority…

That's the UK's interpretation of GDPR. What about France or Poland, or any of the other countries? I suppose it depends where in Europe he would like to visit

There's no "UK Interpretation", this is the whole point of the EU. The rules apply across the block.

Re: GDPR: Removing Monal from the EU

#737

Post by tinus_hn »

CaptainZapp wrote: post #671
fcbrooklyn wrote: post #463

Earlier quoted context omitted.

Bovril could easily comply. They would simply have to open a manufacturing facility that did not use UK beef. The French cheese makers could sort of comply, by pasteurizing their milk. Kinder, I admit, has a more difficult problem, and has, in fact attempted to comply, by creating a completely different product with the same name.

"The French cheese makers could sort of comply, by pasteurizing their milk" And why should the French cripple a delicious and traditional product, which is gladly gobbled up by millions of happy consumers to sell their product in the US?

Because otherwise they can’t sell it there. Their country, their rules. A French cheese maker doesn’t get to dictate the rules abroad. Take it or leave it.

Re: GDPR: Removing Monal from the EU

#738

Post by aembleton »

slrz wrote: post #571
zerostar07 wrote: post #132

While this developer may be overreacting (he probably doesn't need a DPO), i understand why it might just be easier to block it , at least until there are precedents about how to comply and more info on how the regulation will be enforced. GDPR can be scary for developers, because nobody actually knows how a website or app is supposed to work (I have yet to see a single example), and it requires a series of steps tha…

> The example of the cookie law (for which it's hard to argue that it has not utterly failed) should act as a bad precedent, not a good one. It is an utter failure but mostly because services try hard to turn it into a travesty and simultaneously manage to deceive their users by attributing blame for the annoying cookie warnings to regulators. "We are required by law to show you this stupid warning because our site u…

But how would you handle logins without cookies? How would you know that a customer has already agreed not to allow cookies without a cookie?

Re: GDPR: Removing Monal from the EU

#739

Post by lagadu »

linker3000 wrote: post #699
tokyodude wrote: post #679

Earlier quoted context omitted.

> Indeed, this did not drop out of the sky. It has been in the works for years. VOGON CAPTAIN: [On Speakers] People of Earth your attention please. This is Prostectic Vogon Jeltz of the Galactic Hyperspace Planet Council. As you no doubt will be aware, the plans for the development of the outlying regions of the western spiral arm of the galaxy require the building of a hyperspace express route through your star syst…

Yeah, but the analogy is not good... * We've known about the GDPR for around 2 years. * The GDPR text, national regulators' comments, industry opinion, sample docs and a plethora of free resources have been readily accessible on the Internet for about the same length of time. Having worked on the GDPR docs for a medium-sized business that builds learning management systems for corporate customers (about 100 live syst…

> * We've known about the GDPR for around 2 years.

6 years, it's a 2012 directive.

Re: GDPR: Removing Monal from the EU

#740

Post by zerostar07 »

lagadu wrote: post #715

> I do not have the resources to meet the letter of the law for compliance especially with respect to retention and processing these tokens. Harsh words but I feel they're warranted: If you don't want to treat my private data with the due diligence you should, then we're better off not using your service.

> my private data

> we're better off not using

Just pointing out that some people may want to choose how they want their data treated case-by-case, instead of having no option to use the website because its blocked

Post reply on HN