Re: [tor-dev] onionoo: new field: measured flag (#16020)

2015-07-06 Thread l.m
Hi nusenu, Since you posted to tor-dev I guess you're asking for community input too. About your use cases, Onionoo is for obtaining data about running relays, not tor network health, or BWAuth activity. You can answer this question by looking at the latest consensus data from CollecTor, counting

Re: [tor-dev] Roster introduction

2015-07-06 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > The main difference between Roster and Globe/Atlas is that Roster > provides information at the level of *operators*, not individual > relays. > Agreed, this was just a placeholder. Will put contact info instead > for now. Thanks, alot better

[tor-dev] onionoo: new field: measured flag (#16020)

2015-07-06 Thread nusenu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Karsten, could you give me a short opinion about #16020 https://trac.torproject.org/projects/tor/ticket/16020 Something like: - - no, never going to add measurement data to onionoo ever or - - yes, it makes sense and has a chance to be implement

[tor-dev] Chutney (was Re: Performance testing using chutney)

2015-07-06 Thread Cory Pruce
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Well, you could test my latest branches for #14175: > > https://trac.torproject.org/projects/tor/ticket/14175#comment:8 > > There's a branch which modifies src/test/test-network.sh in tor, > and another with the performance measurement code in chut

Re: [tor-dev] Roster introduction (Philipp Winter) (Sean Saito)

2015-07-06 Thread Philipp Winter
On Sun, Jul 05, 2015 at 09:21:38AM +, saitos...@ymail.com wrote: > > - I searched for my relay family by fingerprint and the resulting page's > > URL didn't contain my family, so I couldn't send the URL to somebody > > else. > > Could you give me some more details about this? Currently the s

Re: [tor-dev] Performance testing using chutney

2015-07-06 Thread teor
> On 6 Jul 2015, at 11:16 , Cory Pruce wrote: > > > > > > > And running everything on the same box / VM should still give you some > idea, as long as CPU usage on all CPUs isn't ~100%. > > > > Haha I guess this is a "we'll wait and see" situation. Let me know if > there is anything I can do for