Jacob Appelbaum <jacob@xxxxxxxxxxxxx> wrote: > Nick Mathewson: > > On Tue, Sep 11, 2012 at 4:48 PM, Jacob Appelbaum <jacob@xxxxxxxxxxxxx> wrote: > >> Nick Mathewson: > >>> On Tue, Sep 11, 2012 at 1:12 PM, Jacob Appelbaum <jacob@xxxxxxxxxxxxx> wrote: > >> Oh, I don't mean to imply not to file bugs but rather, if we have a > >> guard that fails circuits, I'd say we should discuss it openly. Is it a > >> load issue? Or something else? > > > > We should definitely discuss stuff openly, yeah. It was the possible > > ExcludeNodes bug that seemed most like an issue that would go well > > with the bugtracker to me. > > Agreed - that said - I like the idea of a client telling users that a > given guard is failing a lot of circuits - is there anyway today that we > can start to learn the distribution of those failures? Say with some > useful client side logging? It would also be great if there was an easy way to correlate messages in the Tor client log with the log of the socks client. Fabian
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays