Removing an archive and private sharing
hossameldeen opened this issue · 4 comments
The following happened with me that made me rethink several assumptions of beaker & hashbase:
- I added an archive to hashbase by mistake.
- I removed it hastily from hashbase.
- I also deleted the archive in beaker (but didn't remove it from trash).
- Surprisingly, I found in my hashbase's profile the public key of the removed archive in Recent Activity.
- When I tried the key in a dat url, it worked!
Several user assumptions that have been broken by beaker & hashbase, in my opinion:
- Beaker: Deleting an archive stops seeding it even if not removed from trash yet.
- Hashbase: Removing an archive removes everything hashbase knows about the archive.
- Hashbase: Actually, I don't remember consenting to making my pinned websites' urls public in the first place (probably did :D), but Recent Activity is dangerous, in my opinion, or even showing the websites that a user has in their profile, and perhaps an explicit option or disclaimer "Show the website on your profile" would be good.
With all due respect! :-)
Thanks for the feedback, I'll talk with @taravancil about 2 and 3.
About 1, Beaker only permadeletes an archive once it's cleared from the trash (happens automatically after 2 weeks). If you visit the archive it'll be swarmed for the rest of the session atm.
Great, thank you!
And in case I didn't make it clear enough in the OP: Especially problematic is removing an unnamed archive because its public key remains exposed in Recent Activity.
That does make sense, yeah. We'll give this some careful thought.
Can a checkbox be added: "Publish as Unlisted" before publishing an archive to Hashbase? Then any unlisted archives should never be displayed in "Recent Activity".