Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T07:27:28Zhttps://gitlab.torproject.org/legacy/trac/-/issues/25240Add an interface to the Metrics CSV files2020-06-13T07:27:28ZirlAdd an interface to the Metrics CSV filesFor some statistics, it would be better to get these from the CSV files instead of from Onionoo (in the case of users, they are not available in Onionoo).For some statistics, it would be better to get these from the CSV files instead of from Onionoo (in the case of users, they are not available in Onionoo).https://gitlab.torproject.org/legacy/trac/-/issues/23937Add tweet templates about events in the Tor network2020-06-13T06:57:02ZirlAdd tweet templates about events in the Tor networkThis may include simple events such as diffs between current and previous consensus documents, but also more complex events for which there may need to be some external data source providing the event information.
This is going to be a ...This may include simple events such as diffs between current and previous consensus documents, but also more complex events for which there may need to be some external data source providing the event information.
This is going to be a larger task, and this ticket serves as a placeholder and a place to hold thoughts and discussions over what may be useful here.https://gitlab.torproject.org/legacy/trac/-/issues/23936Add tweet templates about users of Tor2020-06-13T06:57:02ZirlAdd tweet templates about users of TorData on users is already aggregated and made available on the metrics website:
https://metrics.torproject.org/userstats-relay-country.html
It should also be possible to use the graphs as generated by the website in the tweets.
This wo...Data on users is already aggregated and made available on the metrics website:
https://metrics.torproject.org/userstats-relay-country.html
It should also be possible to use the graphs as generated by the website in the tweets.
This would not just be a couple of templates but perhaps also include:
* Total directly connecting users
* Total bridge users
* Users (direct/bridge) by:
* country
* transport
* IP versionhttps://gitlab.torproject.org/legacy/trac/-/issues/23934Add tweet templates for platform diversity2020-06-13T06:57:01ZirlAdd tweet templates for platform diversityData on platform diversity is already aggregated and made available on the metrics website:
https://metrics.torproject.org/platforms.html
It should also be possible to use the graphs as generated by the website in the tweets.Data on platform diversity is already aggregated and made available on the metrics website:
https://metrics.torproject.org/platforms.html
It should also be possible to use the graphs as generated by the website in the tweets.https://gitlab.torproject.org/legacy/trac/-/issues/23935Add tweet templates for running versions2020-06-13T06:57:02ZirlAdd tweet templates for running versionsData on versions is already aggregated and made available on the metrics website:
https://metrics.torproject.org/versions.html
It should also be possible to use the graphs as generated by the website in the tweets.Data on versions is already aggregated and made available on the metrics website:
https://metrics.torproject.org/versions.html
It should also be possible to use the graphs as generated by the website in the tweets.https://gitlab.torproject.org/legacy/trac/-/issues/23939Create an XMPP interface for querying relay/bridge details2020-06-13T06:57:04ZirlCreate an XMPP interface for querying relay/bridge detailsThis interface would respond to user requests returning Atlas URLs and basic information from Onionoo on the relay, or provide basic aggregated data that may be useful.
The exact commands that may be used are still needing to be defined...This interface would respond to user requests returning Atlas URLs and basic information from Onionoo on the relay, or provide basic aggregated data that may be useful.
The exact commands that may be used are still needing to be defined.
The underlying XMPP framework may be more useful when it comes to providing direct notifications later.https://gitlab.torproject.org/legacy/trac/-/issues/24070Generate an event if more than X relays join2021-11-29T14:35:53ZirlGenerate an event if more than X relays joinWe should decide on what this threshold is.
If more than the threshold of relays join, generate an EVENT status update and send to all channels subscribed to the EVENT type.We should decide on what this threshold is.
If more than the threshold of relays join, generate an EVENT status update and send to all channels subscribed to the EVENT type.https://gitlab.torproject.org/legacy/trac/-/issues/24071Generate an event if the most used Tor version changed2021-11-29T14:35:54ZirlGenerate an event if the most used Tor version changedIf the most popular Tor version used (by relays) has changed, generate an EVENT and send to all microblog accounts subscribed to EVENT updates.If the most popular Tor version used (by relays) has changed, generate an EVENT and send to all microblog accounts subscribed to EVENT updates.https://gitlab.torproject.org/legacy/trac/-/issues/24073Generate an event if there is a major relay outage2021-11-29T14:35:54ZirlGenerate an event if there is a major relay outageGenerate an event if there is a major outage of relays. We should decide on thresholds for relay counts/consensus weight. This may actually be just a part of #24070.Generate an event if there is a major outage of relays. We should decide on thresholds for relay counts/consensus weight. This may actually be just a part of #24070.https://gitlab.torproject.org/legacy/trac/-/issues/24076Implement a MicroblogAccount interface that logs to the console2020-06-13T06:59:43ZirlImplement a MicroblogAccount interface that logs to the consoleThis should call `System.out.println` or maybe something in log4j. It definitely should not generate new status updates to say the status was updated. We may also need some protective mechanism to ensure that DEBUG messages can only be s...This should call `System.out.println` or maybe something in log4j. It definitely should not generate new status updates to say the status was updated. We may also need some protective mechanism to ensure that DEBUG messages can only be sent to this kind of MicroblogAccount.https://gitlab.torproject.org/legacy/trac/-/issues/24069Maintain a copy of the previous details document2020-06-13T06:59:40ZirlMaintain a copy of the previous details documentIn order to perform diffs between details documents to generate events, a copy of the previous details document should be retained.In order to perform diffs between details documents to generate events, a copy of the previous details document should be retained.https://gitlab.torproject.org/legacy/trac/-/issues/24079metrics-bot should listen for private messages2020-06-13T06:59:46Zpastlymetrics-bot should listen for private messagesLess spam in #tor if users can do simple queries via PM.Less spam in #tor if users can do simple queries via PM.https://gitlab.torproject.org/legacy/trac/-/issues/24101Provide percentages not just absolute numbers for country and AS information2020-06-13T07:00:03ZRoger DingledineProvide percentages not just absolute numbers for country and AS information<metrics-bot> 1304 relays in Germany are contributing 4.6GiB/s bandwidth to the #Tor network. https://atlas.torproject.org/#search/country:de
could become
<metrics-bot> 1304 relays in Germany are contributing 4.6GiB/s bandwidth (19.9%)...<metrics-bot> 1304 relays in Germany are contributing 4.6GiB/s bandwidth to the #Tor network. https://atlas.torproject.org/#search/country:de
could become
<metrics-bot> 1304 relays in Germany are contributing 4.6GiB/s bandwidth (19.9%) to the #Tor network. https://atlas.torproject.org/#search/country:de
I'm not sure the right way to phrase it -- originally I had in mind just to hear one percentage, which is the percentage of total bandwidth that 4.6GiB represents. But there are also other percentages we might try to work in, e.g.
<metrics-bot> 1304 relays in Germany are contributing 4.6GiB/s bandwidth (23.6%, 22.6%, 6.9%) to the #Tor network. https://atlas.torproject.org/#search/country:dehttps://gitlab.torproject.org/legacy/trac/-/issues/25219Reduce size of relay flags and align center in badges2020-06-13T07:24:11ZirlReduce size of relay flags and align center in badgesIn the design in #24717 the relay flags should have been 20px, but 32px icons were used. The tor-icons Makefile should be updated to produce 20px icons and then include these instead. The icons should be aligned in the center, not to the...In the design in #24717 the relay flags should have been 20px, but 32px icons were used. The tor-icons Makefile should be updated to produce 20px icons and then include these instead. The icons should be aligned in the center, not to the left, when drawn onto the badge.https://gitlab.torproject.org/legacy/trac/-/issues/24074Refactor IRC connection and authentication into an IRCManager class2020-06-13T06:59:43ZirlRefactor IRC connection and authentication into an IRCManager classCurrently all of this code sits in the main function for metrics-bot, and this prevents metrics-bot from joining multiple networks.Currently all of this code sits in the main function for metrics-bot, and this prevents metrics-bot from joining multiple networks.https://gitlab.torproject.org/legacy/trac/-/issues/24077Refactor microblog accounts setup and updates into a MicroblogManager2020-06-13T06:59:44ZirlRefactor microblog accounts setup and updates into a MicroblogManagerMost of this code is currently in the MetricsBot class directly, with the setup in the main method.
The `microblog(MicroblogStatus)` and `error(String)` functions should be moved. Also, there should be new functions that also serve for ...Most of this code is currently in the MetricsBot class directly, with the setup in the main method.
The `microblog(MicroblogStatus)` and `error(String)` functions should be moved. Also, there should be new functions that also serve for logging:
* `debug(String)`
* `info(String)`
* `warning(String)`
* `relay(String)`
* `network(String)`
* `alert(String)`
* `event(String)`
This will depend on #24075 to have the StatusTypes available. It will probably also depend on #24076 in order to have the logging to the console functionality.