Philipp Winter

Add module to verify a relay's exit policy

1

Relays can lie about their exit policy, e.g., they claim that they exit to port 80 and 443, but won't actually do it when they receive data from clients. We...

...to make it easier for folks to see when a new paper is added.

Show paper's abstract when hovering over it with mouse

1

When you move your mouse over a paper, I'd like the paper's abstract to pop up, to make it easy to get an idea of what the paper is about...

Having access to the base class can be useful for third-party code that needs to juggle a variety of measurements.

We want to be able to extract all consensuses and descriptors that contain a relay identified by its IP address or by its fingerprint. Ideally, we also want to specify...

Currently, sybilhunter uses strict parsing to pass objects to modules. Some modules, however, only need relay fingerprints, which means that lazy parsing is sufficient. Modules should be able to express...

Thanks to Karsten for suggesting this: https://lists.torproject.org/pipermail/metrics-team/2016-February/000069.html

Instead of analysing every single consensus, we might want to analyse only one per week or per month. Thanks to Karsten for suggesting this: https://lists.torproject.org/pipermail/metrics-team/2016-February/000069.html

Sybilhunter's churn module should also be able to determine the fraction of consensus weight joining or leaving the network, like NewCW and GoneCW. Thanks to Karsten for suggesting this: https://lists.torproject.org/pipermail/metrics-team/2016-February/000069.html