Hi Hideo,
i am not at all an expert with tahoe but maybe i can share some of my
understandings:
1) there is software to use tahoe-lafs with (other) cloud storage, check out
this:
https://github.com/mk-fg/tahoe-lafs-public-clouds
but there are other usage scenarios. in a "friendnet" type of environment, you
and other people (i.e. your friends) would set up storage nodes on their NAS',
raspberry pi's, HTPC (to name a few options) and build your own cloud-storage.
Data fed into the grid is encrypted & redunantly distributed to the available
storage nodes. Or you can buy the storage space, i.e. here
https://leastauthority.com/
2) The terms client and gateway are sometimes used in a confusing manner in the
Tahoe docs. Basically a client IS a gateway. So you could compile tahoe on your
smartphone and access your storage grid. the problem is, that there is some
more or less CPU intensive encryption to be done, so it depends a bit on how
your device performs this task. OR you access your data by a "real" gateway,
which does the de/encryption, but that entirely depends on what you want to do.
3) i have no idea
cheers,
t.
________________________________
From: Hideo Kuze <another.ghost.in.the.sh...@gmail.com>
To: tahoe-dev@tahoe-lafs.org
Sent: Thursday, July 18, 2013 3:27 AM
Subject: [tahoe-dev] some questions about tahoe-lafs
Hi,
I checked the FAQ but couldn't find answers to these, so I'm asking here.
1) which clouds are supported to act as nodes? (mega.co.nz? skydrive? gdrive?
dropbox?)
2) what was the motivation for requiring a gateway for accessing the files?
Couldn't it be done only with a client?
I ask this question because if you only required a client for accessing the
data, you could access the data from your mobile (as in having only a single
device). But it seems that as it is, you will always need a trusted computer
running tahoe-lafs 24/7 --- which will be a problem if you're traveling.
3) tahoe-lafs has a small visibility (only recently I've heard about it), as
opposed to more well known projects like Truecrypt, which has more users and a
higher chance of any issues being identified. Has any 3rd party code review
been done?
Thank you for your time.
Cheers
_______________________________________________
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
_______________________________________________
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
