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

Lock down or delete document #92

Open
cben opened this issue May 21, 2015 · 0 comments
Open

Lock down or delete document #92

cben opened this issue May 21, 2015 · 0 comments

Comments

@cben
Copy link
Owner

cben commented May 21, 2015

The current Firebase security rules make document history append-only. This means that once a document's URL gets out, it's full history is forever accessible to the the world.

  • What's worse, deleting text in the editor seems to do the job. There is no hint yet in the UI that older versions are there — but recovering older text is not really hard.

This is not defensible. Users universally expect the ability to delete forever content they created (and sometimes sue for this).

But there is a tradeoff with vandalism. Allowing anyone who saw your work to delete it entirely is also bad. I'm not sure I want to support this until I have logged-in users who "own" a document.

A related alternative (closely related to #91) is retaining the document but locking down access — even read access — to require a longer secret URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant