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

Delete Hastes #354

Open
ACH1980 opened this issue Nov 12, 2020 · 4 comments
Open

Delete Hastes #354

ACH1980 opened this issue Nov 12, 2020 · 4 comments
Labels

Comments

@ACH1980
Copy link

ACH1980 commented Nov 12, 2020

Is there a way we could delete hastes on our own haste-Instance? I think they must be stored somewhere, could we delete them on the filesystem and they would disappear online too? If yes, where to find them?

To be precise: I've actually the problem that I uploaded a haste and accidentally didn't removed all sensitive data, so I asked the admin of the instance to remove it but they can't find it.

Dear
Matthias H.

@ririko5834
Copy link

This is good feature

@jagoe
Copy link

jagoe commented Dec 18, 2020

Currently, that depends on the storage method.
For file, you can navigate to the specified directory (./data by default) and search the files for the content to identify the one you want to delete. You could also generate the md5 sum of the document key in the URL to get the file name (but I expect that to depend on the exact algorithm).
For any of the other storage methods you can basically do the same thing for the respective store.

@jagoe
Copy link

jagoe commented Dec 18, 2020

That being said, I would welcome a feature to delete or edit documents from the UI. Is anything like that planned?
I'm thinking a key to prove ownership that would be generated and displayed after creation. That way there'd be no need for authentication while still enabling authorization.
Integrating the client would require some more thought, since I wouldn't want to copy the "admin access" URL by default but also not "lose" it.

I wouldn't mind working on that or a similar solution, but I didn't want to start without first checking if that's even part of the vision.

@github-actions
Copy link

github-actions bot commented Mar 8, 2022

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Mar 8, 2022
@filipechagas filipechagas added triage and removed stale labels Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants