Re: [tor-dev] tor 0.2.7.5 make error

2015-12-07 Thread grarpamp
On Tue, Dec 8, 2015 at 1:10 AM, Tim Wilson-Brown - teor wrote: > What's the version of autoconf / automake? > https://trac.torproject.org/projects/tor/ticket/17732 added ___ tor-dev mailing list tor-dev@lists.torproject.org

Re: [tor-dev] tor 0.2.7.5 make error

2015-12-07 Thread Tim Wilson-Brown - teor
> On 8 Dec 2015, at 16:47, grarpamp wrote: > > "Makefile", line : Need an operator > make: fatal errors encountered -- cannot continue > > 6772:export TESTING_TOR_BINARY=$(top_builddir)/src/or/tor > 6794:export PYTHON= > 6795:export SHELL=/bin/sh > 6796:export

Re: [tor-dev] Shared random value calculation edge cases (proposal 250)

2015-12-07 Thread Michael Rogers
On 21/11/15 12:05, George Kadianakis wrote: >> If there's no consensus on a fresh SRV, why not just use the disaster >> recovery procedure? >> >> That is: >> >># Consensus >>if majority agrees on SR value(s): >>put in consensus >>else: >>put disaster recovery SR value

Re: [tor-dev] Scaling Tor Metrics, Round 2

2015-12-07 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/12/15 01:07, Spencer wrote: > Hi, >> teor: Do David's visualizations already use JavaScript? We could >> make (another) part of the metrics site use JavaScript. >> > > Can the data be processed on the host server and sent to the > client

Re: [tor-dev] Scaling Tor Metrics, Round 2

2015-12-07 Thread Tim Wilson-Brown - teor
> On 7 Dec 2015, at 19:14, Karsten Loesing wrote: > > On 07/12/15 01:07, Spencer wrote: > > Hi, > >> teor: Do David's visualizations already use JavaScript? We could > >> make (another) part of the metrics site use JavaScript. > >> > > > > Can the data be processed on

Re: [tor-dev] Graphs - Estimated Traffic Capacity

2015-12-07 Thread Tim Wilson-Brown - teor
> On 22 Nov 2015, at 02:55, David Goulet wrote: > > On 21 Nov (16:26:31), Tim Wilson-Brown - teor wrote: > ... >> It would be great to have some stats for typical path lengths, is there an >> open ticket for this, or should I create one? > > That would help us have a better

Re: [tor-dev] Better relay uptime visualisation

2015-12-07 Thread Tim Wilson-Brown - teor
> On 8 Dec 2015, at 10:43, Tom Ritter wrote: > > On 7 December 2015 at 13:51, Philipp Winter > wrote: >> I spent some time improving the existing relay uptime visualisation [0]. >> Inspired by a research paper [1], the new algorithm uses

Re: [tor-dev] Scaling Tor Metrics, Round 2

2015-12-07 Thread Karsten Loesing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/12/15 12:10, Tim Wilson-Brown - teor wrote: > >> On 7 Dec 2015, at 19:14, Karsten Loesing >> wrote: >> >> On 07/12/15 01:07, Spencer wrote: >>> Hi, teor: Do David's visualizations already use JavaScript? We

[tor-dev] Better relay uptime visualisation

2015-12-07 Thread Philipp Winter
I spent some time improving the existing relay uptime visualisation [0]. Inspired by a research paper [1], the new algorithm uses single-linkage clustering with Pearson's correlation coefficient as distance function. The idea is that relays are grouped next to each other if their uptime (basically

Re: [tor-dev] Better relay uptime visualisation

2015-12-07 Thread David Fifield
On Mon, Dec 07, 2015 at 02:51:23PM -0500, Philipp Winter wrote: > I spent some time improving the existing relay uptime visualisation [0]. > Inspired by a research paper [1], the new algorithm uses single-linkage > clustering with Pearson's correlation coefficient as distance function. > The idea

Re: [tor-dev] Better relay uptime visualisation

2015-12-07 Thread nusenu
Philipp Winter: > Red pixels are used to highlight suspiciously similar clusters. Last year [1] there were a few huge groups, 3 of them are not flagged (black lines, not red) even though they look like a perfectly matching group? [1]

Re: [tor-dev] Better relay uptime visualisation

2015-12-07 Thread David Fifield
On Tue, Dec 08, 2015 at 10:47:08AM +1100, Tim Wilson-Brown - teor wrote: > > On 8 Dec 2015, at 10:43, Tom Ritter <[1]t...@ritter.vg> wrote: > > On 7 December 2015 at 13:51, Philipp Winter <[2]p...@nymity.ch> wrote: > > I spent some time improving the existing relay uptime

Re: [tor-dev] Better relay uptime visualisation

2015-12-07 Thread grarpamp
Can a one be generated covering each year and maybe a five year one. And three other check sets but sorted left to right by first online date FP AS As to the actual FP's, all I can think of is including a second text file with pixel number to FP mappings. Or some "maps" style online zooming.

Re: [tor-dev] Better relay uptime visualisation

2015-12-07 Thread Philipp Winter
On Mon, Dec 07, 2015 at 05:43:01PM -0600, Tom Ritter wrote: > On 7 December 2015 at 13:51, Philipp Winter wrote: > > I spent some time improving the existing relay uptime visualisation [0]. > > Inspired by a research paper [1], the new algorithm uses single-linkage > > clustering

[tor-dev] Tor Messenger 0.1.0b4 is released

2015-12-07 Thread Sukhbir Singh
We are pleased to announce another public beta release of Tor Messenger. This release addresses a number of stability and usability issues, and includes the default bridge configurations for pluggable transports. The initial public release [0] was a success in that it garnered a lot of useful

[tor-dev] tor 0.2.7.5 make error

2015-12-07 Thread grarpamp
"Makefile", line : Need an operator make: fatal errors encountered -- cannot continue 6772:export TESTING_TOR_BINARY=$(top_builddir)/src/or/tor 6794:export PYTHON= 6795:export SHELL=/bin/sh 6796:export abs_top_srcdir=/tmp/tor-0.2.7.5 6797:export builddir=. This is on a FreeBSD 8.x from early