Re: [tor-dev] Notes from 12 April 2018 Simple Bandwidth Scanner Meeting

2018-04-13 Thread Damian Johnson
> Good question! > > While I didn't necessarily work on sbws while at my place of work, I > couldn't rationalize that it is unrelated to my day job. Thus I need to > get permission from my employer in order to release sbws. > > I've already submitted that paperwork and expect to get it back in abou

Re: [tor-dev] Notes from 12 April 2018 Simple Bandwidth Scanner Meeting

2018-04-13 Thread Matt Traudt
On 4/13/18 12:26, Damian Johnson wrote: >> https://github.com/pastly/simple-bw-scanner/blob/master/docs/source/specification.rst >> (ask Pastly for access) > > Hi Matt, why is this repo read restricted? I was idly curious to see > the code of sbws and was surprised it's effectively closed source.

Re: [tor-dev] Notes from 12 April 2018 Simple Bandwidth Scanner Meeting

2018-04-13 Thread Damian Johnson
> https://github.com/pastly/simple-bw-scanner/blob/master/docs/source/specification.rst > (ask Pastly for access) Hi Matt, why is this repo read restricted? I was idly curious to see the code of sbws and was surprised it's effectively closed source. ___

Re: [tor-dev] Notes from 12 April 2018 Simple Bandwidth Scanner Meeting

2018-04-13 Thread Matt Traudt
Thanks Tom! There's a few more things that I think we need to figure out before we take you up on this offer. I'll keep you in mind though, because I think having sbws and torflow running side by side is something that should happen very soon. Stay tuned! And thanks for your help obtaining torfl

Re: [tor-dev] Notes from 12 April 2018 Simple Bandwidth Scanner Meeting

2018-04-12 Thread Tom Ritter
I'm happy to run a sbws alongside my torflow. It will let us compare bw numbers apples to apples too. My only difficulty is being unable to spend significant time to diagnose why it doesn't work, if it doesn't work. If it's at the point I should give it a shot, point me at some instructions :) -