Autor: Alan Data: A: tails-dev Assumptes vells: Re: [Tails-dev] Testing Tor Monitor Assumpte: [Tails-dev] Tor Monitor: don't show duplicate streams with the same
destination in the same circuit
Hi,
sajolida <sajolida@???> wrote: > Alan:
> > intrigeri <intrigeri@???> wrote:
> >> sajolida wrote (27 Aug 2015 16:48:14 GMT) :
> >>> C. Duplicate information
> >>
> >>> In the list of circuits I sometimes see duplicated lines.
> >>
> >> Technical nitpicking: these are streams, not circuits :)
> >>
> >>> For example when connecting to heavy websites like YouTube.
> >>> See duplicates.png in attachment. Why not deduplicate these lines?
> >>
> >> I'm not sure what's the value of the "there are multiple streams to
> >> this IP:PORT going on that circuit" information. At first glance,
> >> I would say let's deduplicate, but perhaps I'm missing a use case
> >> or three?
> >>
> > If I display duplicates, either I have a bug or there are multiple
> > streams to this IP:port in that circuit... I can deduplicate them if
> > requested but I fail to see the interest to complexify the
> > code to simplify the reality.
>
> The interest is to have a more compact view displayed to the user and
> reduce noise. Did you see my screenshot? To me it looks pretty awful. I
> fail to see the interest in complexifying so much the interface to
> simplify a bit the code :)
Please file a ticket for that then. I'd suggest we don't consider it as
a blocker thought.
%20:%0A>%20>%20>>>%20C.%20Duplicate%20information%0A>%20>%20>>%0A>%20>%20>>>%20In%20the%20list%20of%20circuits%20I%20sometimes%20see%20duplicated%20lines.%0A>%20>%20>>%0A>%20>%20>>%20Technical%20nitpicking:%20these%20are%20streams,%20not%20circuits%20:)%0A>%20>%20>>%0A>%20>%20>>>%20For%20example%20when%20connecting%20to%20heavy%20websites%20like%20YouTube.%0A>%20>%20>>>%20See%20duplicates.png%20in%20attachment.%20Why%20not%20deduplicate%20these%20lines?%0A>%20>%20>>%0A>%20>%20>>%20I'm%20not%20sure%20what's%20the%20value%20of%20the%20%22there%20are%20multiple%20streams%20to%0A>%20>%20>>%20this%20IP:PORT%20going%20on%20that%20circuit%22%20information.%20At%20first%20glance,%0A>%20>%20>>%20I%20would%20say%20let's%20deduplicate,%20but%20perhaps%20I'm%20missing%20a%20use%20case%0A>%20>%20>>%20or%20three?%0A>%20>%20>>%0A>%20>%20>%20If%20I%20display%20duplicates,%20either%20I%20have%20a%20bug%20or%20there%20are%20multiple%0A>%20>%20>%20streams%20to%20this%20IP:port%20in%20that%20circuit...%20I%20can%20deduplicate%20them%20if%0A>%20>%20>%20requested%20but%20I%20fail%20to%20see%20the%20interest%20to%20complexify%20the%0A>%20>%20>%20code%20to%20simplify%20the%20reality.%0A>%20>%20%0A>%20>%20The%20interest%20is%20to%20have%20a%20more%20compact%20view%20displayed%20to%20the%20user%20and%0A>%20>%20reduce%20noise.%20Did%20you%20see%20my%20screenshot?%20To%20me%20it%20looks%20pretty%20awful.%20I%0A>%20>%20fail%20to%20see%20the%20interest%20in%20complexifying%20so%20much%20the%20interface%20to%0A>%20>%20simplify%20a%20bit%20the%20code%20:)%0A>%20%0A>%20Please%20file%20a%20ticket%20for%20that%20then.%20I'd%20suggest%20we%20don't%20consider%20it%20as%0A>%20a%20blocker%20thought.%0A>%20%0A>%20Cheers%0A>%20%0A>%20 "Reply to this message")
