Hacker News Reader

Comment by dx034 | Hacker News Reader

The data belongs to the user. There's nothing Facebook can do to prevent exporting if it's via the data backup. They can just design it in a way that is easy to read by humans but very challenging for parsers.

View on HN

>They can just design it in a way that is easy to read by humans but very challenging for parsers.

This is explicitly forbidden in article 20.1

Machine readable only means no images. You can still structure it in a way that it's a pain to import. Or use changing structures. Definitely violates the spirit of the law but don't think Facebook cares about that.

I'd argue that the GDPR is entirely about spirit.

well they can make a big, very readable screenshot of your data, handwritten by an adversarial DNN

What's with generated images (some crap like facebook frames or generated slideshows etc) doesn't have facebook the copyright on those - at least the designs? Should those be included in the export?

Yeah, I understand it belongs to the user and they can export it. But does any third party service then have a right to allow the users to import their data from Facebook?

Yes, the user owns the data and can give consent.

I don't understand how a facebook post made by me 'belongs' to me. It was addressed to specific audience that facebook made available to me, it wouldn't have existed in the first place if facebook didn't exist. How does it completely belong to me.

If you make a song on a Gibson guitar, should the song belong to Gibson?

I think your analogy holds true for the documents you write on MS word that you bought. Posting on facebook is equivalent to recoding on a song in Gibson's studio, in which case it doesn't completely belong to you.

Reply on news.ycombinator.com