[tahoe-dev] Tahoe use cases: Storage vs UI
nejucomo at gmail.com
Mon Oct 8 17:31:40 UTC 2007
Hello Tahoe Developers,
I'd like to use Tahoe in a private network amongst friends, but
there's a use case conflict:
In order to have reliable storage, the grid members should have a good
uptime. Storage reliability depends, to a large deal on storage
redundancy as well as average grid member uptime. Zooko convinced me
I want the average storage grid reliability to be larger than the
storage redundancy multiplicative inverse (which we called "r").
However, I do most of my day-to-day computer usage on transient
connections, such as a laptop which hops from wifi to wifi, often
being shutdown for arbitrary lengths of time.
So, I want to run a Tahoe UI on my laptop, which will store my keys,
linking the confidentiality of my grid storage to my laptop. Yet, I
don't want it to be a member of the storage grid, or the overall grid
reliability will decrease.
Is there a simple way to achieve this use case?
Unless Tahoe has specific support for this, one option is to connect
to a trustworthy node running on a high-uptime, static ip server, and
connect to the web ui via HTTPS.
ps: This use case seems similar to the AMD commercial service, where
there are customer (UI, no storage) nodes and server (storage, no UI)
More information about the tahoe-dev