[tor-dev] compass: new group by options: by-contact, by-OS, by-version

Nusenu nusenu at openmailbox.org
Thu Mar 19 14:12:38 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Karsten,

I added a few new grouping options to compass:

- -T --by-contact (#6675)
	(Maybe we should truncate contacts and remove the undefined)
- -O --by-os
- -V --by-version (#6855)

+expose -N options in html (was implemented but not exposed in gui)

https://github.com/nusenu/tor-compass


For all output I (mis)used the nick column as a quick solution since
it is not used otherwise when grouping.

Advertised bw is broken for some time. There is no
'advertised_bandwidth_fraction'  (This field was removed from onionoo
in November 2014.). Is it ok to change this to observed_bandwidth?
(which would be a non fraction item)* ?

(The MyFamily lookup is also broken)


short commit log:
- - add new group by ContactInfo option: by_contact (-T, --by-contact)
   (quick 'n dirty)

- - added new grouping -O, --by-os     (all BSDs are merged into one group)

- - added new grouping by tor version (-V, --by-version)

- - tell app.py about new options (by_version, by_os, by_contact)

- - expose -N option in html and fix a missing label tag

- - include network data in html output when using -N (uses nick column)

- - expose by_version, by_os and by_contact options in HTML

- - if it is just one item, display the actual value for AS and CC
instead of saying (1)

What do you think about it?

thanks,
Nusenu


*) while playing with that I found 3 relays from JP that have a
suspiciosly high adv bw:
https://atlas.torproject.org/#details/F528DED21EACD2E4E9301EC0AABD370EDCAD2C47
https://atlas.torproject.org/#details/8901B1D2D4C0D3398C3F8363247B5AABF31369E4
https://atlas.torproject.org/#details/4EA0464A1B8D4231F176BA2FA1BCBF0A26F128D5

reminded me of SKKU43:
https://lists.torproject.org/pipermail/tor-talk/2014-February/032094.html
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVCtlTAAoJEFv7XvVCELh0bY0P/1aJyZncqdy47WZM9I7Y1E4a
Sg1luXTqi9VlFZhbUJeFrhidLVPSqQYbMw79sKufU2uw/Jcqr0Ro2O48q9Gj7sL8
lDcM4AgFzm1yTedoXqyNAA5+bBeQTAjEgQU1ADYUZvDx2ULmGG4aD6qCuaFoP+3/
kjJ6r92jLOSYpOVdt8FyNc8IZYpbEwQNMKc4A0uZhQV/WVv6vFiOaXHliPdR6m2+
SU+KTqldWppfeezWIalGl3t7HEnz87JOaWrdnQ8fjLKSsqkex2T5E1MClguM4u2o
5ABPxg6uF/izjPv2VEy/hl42RQbLM5SDazM4CLMFN3mQu6Xa4iZ5R8A6iLDgZBj6
zK2wExcxScc58r4Briv5EKUpC9LTgE52DkPkX+TM3i9ktniYQbb/k/cy85nn+ENa
WrZ2WDmaMyQXy6kXDCS4U/3gbv1+Dwq82hg372N2fga6hOXsZPFrxV1TwWlMTzp9
MvpaF6/GZsivrjNklteHxvxgcxTyywaKW5QUdFJdeCZnOrDy29iGKIql10xQ7TXa
gTC7OTsDCAPiJn8P5xKhEAlVeJmz0zZN7QhbY/ybIc5KWkOoKyYwkT9ysmpS8rOK
mapKbuMXvuA3Sg1F1sK9PEUy+D8ZAe+sBjOEHzqILARA6VXsly0rSJkcnhNKNpmL
yxSwWe4uWOVXDmVEl7hQ
=jGQe
-----END PGP SIGNATURE-----


More information about the tor-dev mailing list