[tor-bugs] #13135 [Onionoo]: Support various fingerprint formats

[Tor Bug Tracker & Wiki]

#13135: Support various fingerprint formats
-----------------------------+-----------------
     Reporter:  Sebastian    |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by phw):

 Replying to [comment:3 karsten]:

 > 1. The `search` parameter supports searching by (beginning of)
 base64-encoded relay fingerprint.  This needs input from Onionoo client
 developers for escaping `+` and `/`.  Technically, this constitutes a
 major protocol change that requires at least one month notice before
 deployment to give client developers the chance to implement filters if
 their searches are not supposed to return matching base64-encoded
 fingerprints.

 If a relay would have a nickname identical to another relay's
 base64-encoded fingerprint, Onionoo would return both relays, right?

 > 2. (This is actually a suggestion to not change anything in Onionoo:)
 Regarding listing base64-encoded fingerprint, I'm considering not to add a
 field for that but asking client developers to re-encode the hex
 fingerprint if they want to display the base64-encoded one.  Let's save
 bandwidth by avoiding to transmit redundant data.  Unless binary encoding
 is something that clients cannot or shouldn't be required to do?

 That sounds like a good option to me but would it work with the upcoming
 JavaScript-free version of Globe?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13135#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online