[tahoe-dev] Remove node?
Zooko O'Whielacronx
zookog at gmail.com
Fri Jun 7 10:54:31 UTC 2013
On Fri, Jun 7, 2013 at 5:49 AM, Anders Genell <anders.genell at gmail.com> wrote:
> Hehe, yes, worry is a very human trait :-)
>
> But I can also imagine some slight practical use in having an up to date list. We plan to invite friends who are not so very computer savvy, and it would be good to see if their nodes are suddenly disconnected for some reason. If the list starts getting cluttered by legacy nodes I imagine it could be slightly less obvious which ones are a real problem.
Good point.
> But if there is no real reason for doing anything about it then I'll survive without a nifty mind soothing clean-up.
Well, what you wrote above is a real reason. However, I don't know
when I, for one, would get around to working on this instead of
working on other Tahoe-LAFS improvements. If someone else does the
work, I would approve of committing the fix to Tahoe-LAFS trunk, in
principle, although I'm not sure precisely what solution I would want
to see. Oh, in fact now that I think about it, if the problem is the
human interface element, described above, then the solution should
probably be to hide long-disconnected servers from the *display*
instead of to delete information about them entirely from the client!
Maybe the UI should have a folded-away list of servers that have not
been seen in more than 7 days, or something like that.
Here's a ticket (thanks, PRabahy!): #1997.
Regards,
Zooko
https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1997# Remove node feature
More information about the tahoe-dev
mailing list