Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is use of Blockchain at odds with Right to be forgotten ? #2

Open
nelsonic opened this issue Dec 9, 2016 · 4 comments
Open

Is use of Blockchain at odds with Right to be forgotten ? #2

nelsonic opened this issue Dec 9, 2016 · 4 comments
Labels
help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue

Comments

@nelsonic
Copy link
Member

nelsonic commented Dec 9, 2016

Does the idea of having a distributed database where records cannot be deleted without "breaking" the chain mean that people lose the "Right to be forgotten" ?
See:

@nelsonic nelsonic added help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue labels Dec 9, 2016
@jackie-scholl
Copy link

It depends on what you're using Blockchain for. If you're using it for handling money, zcash is a highly anonymous public blockchain. If you're using it to store user data, I'd be interested to know what the perceived benefit is over tried and true distributed databases that do allow for editing and deleting records.

@nelsonic
Copy link
Member Author

nelsonic commented Dec 9, 2016

@raptortech-js which distributed database do you have experience with?
(my interest in Blockchain is for storing sequential records in a system which then allows people to export their data and use it elsewhere...)

@jackie-scholl
Copy link

jackie-scholl commented Dec 9, 2016

@nelsonic personally, I've used DynamoDB and Amazon Cognito Sync. For storing purely sequential records I'd use Amazon S3 (which I also have experience with), which is more of an object store than a database, which makes it (in my mind) even better for this task. If you don't want to use AWS, I believe Azure and Google Cloud Platform both have similar offerings. If you don't want to use the cloud, I'd use MySQL with replication or possibly MongoDB. If there was a massive amount of data (50+ TB), I'd consider Hadoop. If it was important that it be very highly distributed and fault-tolerant, I'd consider OrbitDB, but be careful; it's still at a very early stage of development.

The major advantages of S3 in this case are that it allows you to drop in data in absolutely any format, that it's very easy to append data, the very attractive cost structure, and the security controls available.

@nelsonic
Copy link
Member Author

I tend to agree with Japanese courts on their ruling that certain crimes should not be "forgotten", e.g:
https://www.theguardian.com/world/2017/feb/02/right-to-be-forgotten-online-suffers-setback-after-japan-court-ruling
"supreme court said, however, that the public’s right to know outweighed the man’s right to privacy, given the serious nature of his crimes"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue
Projects
None yet
Development

No branches or pull requests

2 participants