<html><head></head><body><div class="ydp55672b36yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div>David,</div><div><br></div><div>I see that the metrics change has been reverted.</div><div><br></div><div>If/When the metrics change is implemented, will loadbalanced Tor Relay Nodes need to be uniquely named or will they all be able to use the same nickname?</div><div><br></div><div>I'm glad to hear your loadbalanced Snowflake Relay continues to work well.</div><div><br></div><div>Thanks, again, for your efforts.</div><div><br></div><div>Respectfully,</div><div><br></div><div><br></div><div>Gary</div><div class="ydp55672b36signature">—<br>This Message Originated by the Sun.<br>iBigBlue 63W Solar Array (~12 Hour Charge)<br>+ 2 x Charmast 26800mAh Power Banks<br>= iPhone XS Max 512GB (~2 Weeks Charged)</div></div>
<div><br></div><div><br></div>
<div id="ydp55672b36yahoo_quoted_6681170847" class="ydp55672b36yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, March 3, 2022, 6:59:26 PM MST, David Fifield <david@bamsoftware.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div>On Thu, Mar 03, 2022 at 08:13:34PM +0000, Gary C. New wrote:<br clear="none">> Has Tor Metrics implemented your RFC related to Written Bytes per Second and<br clear="none">> Read Bytes per Second on Onionoo?<br clear="none">> <br clear="none">> As of the 27th of February, I've noticed a change in reporting that accurately<br clear="none">> reflects the aggregate of my Tor Relay Nodes opposed to the previously reported<br clear="none">> Single Tor Node. Are you seeing a similar change for snowflake.torproject.org?<br clear="none"><br clear="none">You're right. I see a change since 2022-02-27, but in the case of the<br clear="none">snowflake bridge the numbers look wrong, about 8× too high. I posted an<br clear="none">update on the issue. Thanks for noticing.<br clear="none"><br clear="none"><a shape="rect" href="https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40022#note_2783524" rel="nofollow" target="_blank">https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40022#note_2783524</a><br clear="none"><br clear="none">> Additionally, other than the hourly stacktrace errors in the syslog, the<br clear="none">> secure_onion_key workaround seems to be working well without any ill<br clear="none">> side-effects. I've been able to operate with the same secure_onion_key for<br clear="none">> close to 5 weeks, now. Have you run into any issues?<br clear="none"><br clear="none">Yes, it's still working well here.<div class="ydp55672b36yqt6062192202" id="ydp55672b36yqtfd71278"><br clear="none">_______________________________________________<br clear="none">tor-relays mailing list<br clear="none"><a shape="rect" href="mailto:tor-relays@lists.torproject.org" rel="nofollow" target="_blank">tor-relays@lists.torproject.org</a><br clear="none"><a shape="rect" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="nofollow" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br clear="none"></div></div>
</div>
</div></div></body></html>