Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm not sure what exactly Scuttlebutt covers or does not cover, but an example real problematic situation that I have seen is like this:

1. The system among other things stores user-entered content;

2. User A has published sensitive personal data about person B (perhaps in a doxxing-like post, perhaps by making a fake profile with their name and data, perhaps including interesting images), and to make things interesting also regarding other laws in other countries, let's assume that person B is underage (which is also realistic and common, school kids do things like that to each another).

3. Person B requests that user A removes that content, and A refuses.

4. Person B escalates (the specific process does not matter much) finally resulting in you getting a legally binding request to remove that information about person B from your system/product.

So the key tech requirements include both breaking immutability and full centralised control; you can do decentralised systems for e.g. performance and bandwidth reasons, but fully decentralised, user-controlled censorship-resistant technologies can't be used because then you can't implement censorship, and you need that ability.



There doesn't even have to be a person B. Under the terms of the GDPR you have the right to an erasure request, which means the party holding your data must erase your data, whatever that may be, and it must be erased from backup systems too.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: