This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Multiple users to "own" the same dat. #115
Comments
FWIW the blue link labs team forked hypercloud to https://github.com/beakerbrowser/hashbase and that's the one we actively maintain. IIRC the only reason for that rule is to reduce complexity. |
Oh thanks, I actually came to this repo because of the link on the hashbase homepage :) |
Whoops!
…On Wed, Dec 13, 2017 at 10:00 AM, Martin Heidegger ***@***.*** > wrote:
Oh thanks, I actually came to this repo because of the link on the
hashbase homepage :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABNhU0d0fz7OwtR86znsNmorUhLXaZy_ks5s__SAgaJpZM4RANDZ>
.
|
Closing this issue in favor of beakerbrowser/hashbase#60 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hypercloud has upload limits & a "remove button" (which are awesome) but this means that someone could publish dat and then at a later point remove it. If another person wants to make sure that a certain dat stays alive even if another person decides to remove it then she might want to "upload" the same dat under her account in order to make sure that it stays available (and for the url to be correct). The current
'This archive is already being hosted by someone else'
is counter-productive in that case. Would it be okay to change this to "allowed"?The text was updated successfully, but these errors were encountered: