Re: [tor-dev] Latest state of the guard algorithm proposal (prop259) (April 2016)

2016-04-29 Thread Fan Jiang
Hi, Just some update, We fixed this chosen_by_version SIGSEGV error, And Tania is working on removing XXX comments. Will keep u updated when we close more issues. Cheers, Fan On Fri, Apr 22, 2016 at 9:14 AM, George Kadianakis wrote: > Fan Jiang writes: > > > [ text/plain ] >

Re: [tor-dev] Latest state of the guard algorithm proposal (prop259) (April 2016)

2016-04-22 Thread Fan Jiang
2016年4月22日 上午4:54,"George Kadianakis" 写道: > > Fan Jiang writes: > > > [ text/plain ] > > On Thu, Apr 21, 2016 at 4:32 AM, George Kadianakis > > wrote: > > > >> Fan Jiang writes: > >> > >> > [ text/plain ] > >> >

Re: [tor-dev] Latest state of the guard algorithm proposal (prop259) (April 2016)

2016-04-21 Thread Fan Jiang
On Thu, Apr 21, 2016 at 4:32 AM, George Kadianakis wrote: > Fan Jiang writes: > > > [ text/plain ] > > Hi, > > > >> Hello Fan and team, > >> > >> I think I'm not a big fan of the pending_guard and pending_dir_guard > >>

Re: [tor-dev] Latest state of the guard algorithm proposal (prop259) (April 2016)

2016-04-20 Thread Fan Jiang
come 100% > with #12538) > > #12538 got merged in 0.2.8, so if prop259 gets merged in 0.2.9, by the > time prop259 becomes active, almost all guards will be dirguards. > > So I think it's fine to only consider guards that are dirguards && > fast && > stable now, since by the time prop259 gets deployed that will be the > case > for almost 100% of guards. > -- Fan Jiang 蒋帆 Amateur Code Chef Thoughtworks, Inc. mobile +86-150-9189-3714 skype f...@torchz.net ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Latest state of the guard algorithm proposal (prop259) (April 2016)

2016-04-18 Thread Fan Jiang
Hi, the last mail got rejected by tor-dev, to keep track of this thread, sending again, sorry for disturbing, > On Fri, Apr 15, 2016 at 5:37 AM, George Kadianakis > wrote: > >> Fan Jiang writes: >> >> > [ text/plain ] >> > Thanks for the insights. >