You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 23, 2021. It is now read-only.
On datBase, I viewed a dat of mine that I didn't share with anyone. A day later, with datBase window has been long closed, I still see a peer-count of 1 in Beaker Browser. This annoys me since I didn't mean to share it with datBase; I only wanted to test the connectivity and my expectation is that datBase would forget my dat after closing its window.
I'm aware that the privacy model of a dat is technically the knowledge of its public key, but still, if datBase is to remember my dat forever, I think it should've asked for my consent or displayed a warning. I feel betrayed by the current default.
This all assumes I'm correct in that datBase remembers my dat forever :-)
The text was updated successfully, but these errors were encountered:
This is an important UX concern, thanks for bringing it up! I think dats periodically get removed but I agree, perhaps this should happen when you close the tab.
On datBase, I viewed a dat of mine that I didn't share with anyone. A day later, with datBase window has been long closed, I still see a peer-count of 1 in Beaker Browser. This annoys me since I didn't mean to share it with datBase; I only wanted to test the connectivity and my expectation is that datBase would forget my dat after closing its window.
I'm aware that the privacy model of a dat is technically the knowledge of its public key, but still, if datBase is to remember my dat forever, I think it should've asked for my consent or displayed a warning. I feel betrayed by the current default.
This all assumes I'm correct in that datBase remembers my dat forever :-)
The text was updated successfully, but these errors were encountered: