[tor-relays] Are BWauths punishing 'bad' relays? (not publishing measurements)

[nusenu]

Hi,

this is actually a question to BWauth ops.

even though the new onionoo measured flag data is not* yet completely
rolled out (since it has to be deployed for > a week to assign the flag
to all relays), I would have a question since the data says that
all relays in the previously detected AWS family [1] are unmeasured.

I'm wondering whether this is a pure coincidence or on purpose (by
BWauths) or by some other yet to be found reason?

thanks!

[1] https://lists.torproject.org/pipermail/tor-talk/2015-July/038623.html

The "spikes" in the following table brought me two that group again.


The table shows unmeasured running relays by the month they joined the
network (note this is based on preliminary onionoo data)

The "spikes" are caused by relays mentioned in [1].

+-----------+---------+
| joinmonth | #relays |
+-----------+---------+
| 2015-07   |       3 |
| 2015-06   |       4 |
| 2015-05   |       2 |
| 2015-04   |      12 | <<< AWS family part II
| 2015-03   |       4 |
| 2015-02   |      35 | <<< AWS family part I
| 2015-01   |       2 |
| 2014-12   |       2 |
| 2014-11   |       8 |
| 2014-10   |       1 |
| 2014-09   |       3 |
| 2014-08   |       3 |
| 2014-07   |       2 |
| 2014-06   |       2 |
| 2014-05   |       1 |
| 2014-04   |       4 |
| 2014-03   |       1 |
| 2014-01   |       2 |
| 2013-11   |       1 |
| 2013-02   |       1 |
| 2012-04   |       1 |
| 2012-02   |       1 |
+-----------+---------+
onionoo data from 2015-08-18 18:00:00 (thecthulhu instance)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20150818/74fc7567/attachment.sig>