[tahoe-dev] How to ignore own node?

[slush]

Hello Shawn,

thank you for your view. I considered almost everything you wrote. My
primary usage of Tahoe is as disaster backup and I don't care about
instant recovery too much. But first impulse of patching Tahoe by
myself is usage of helper, so every uploaded file was downloaded back
from helper to my machine which killed my Internet connection. Now Im
satisfied, my disc isn't storing unwanted shares, connection is used
just for uploading and my computer have more free capacity for anyone
else's shares.

Marek

On Thu, Jun 24, 2010 at 11:10 PM, Shawn Willden <shawn at willden.org> wrote:
> On Fri, Jun 18, 2010 at 3:14 AM, slush <slush at centrum.cz> wrote:
>>
>> Partially yes, because happiness give me a guarantee to recover my
>> files. But I still think blocking own node would be a nice feature,
>> because uploading file to the same node is useless in most cases.
>
> I thought the same thing for a while, but changed my mind.
>
> Keep in mind that backups serve to help recovery from two different kinds of
> situations:  disasters and errors.
>
> If all you're thinking about is disasters, then you're right that putting
> shares on the local machine is useless, because full copied of the data are
> on the local machine.  But if you consider errors, cases where you
> erroneously remove files that you need, then having local shares both
> improves recovery performance and also survivability, in case some of the
> remote servers are off-line or gone.
>
> All in all, I decided that the benefits of having local shares outweigh the
> small cost in disk space.  You may not come to the same conclusion, but it's
> worth thinking about.
>
> --
> Shawn
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>