Opened 7 years ago

Closed 6 years ago

#5255 closed enhancement (implemented)

Support search via Tor node contact / email address

Reported by: karsten Owned by: karsten
Priority: Low Milestone:
Component: Metrics/Onionoo Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by sjmurdoch)

djon3s says:

I'd like to be able to search for Tor nodes by the contact details left on the node. Say I wanted to see every server that runs. Currently, only servers that will return are those with Torservers in the title. It will miss servers with another name (e.g. 'Chomsky) for which is linked as a contact.

Thanks :-)

Sounds good. This is also related to #5254 (former GitHub issue 18).

(This was issue 19 in my GitHub repository.)

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by karsten

Priority: normalminor

We shouldn't extend the search parameter to include contact information. That would be just too confusing for users.

We could add a contact parameter that allows filtering for strings inside a relay's contact line. I'm going to postpone this idea, though, until there's a Python Onionoo or until there's an actual application wanting to use this feature. Changing priority to minor.

comment:2 Changed 6 years ago by sjmurdoch

Description: modified (diff)

comment:3 Changed 6 years ago by sjmurdoch

Description: modified (diff)

comment:4 Changed 6 years ago by sjmurdoch

I would like this too, to support the Tor Facebook app proposed here: (p8).

Currently I would have to download the whole detail document periodically, but I would prefer to be able to search for users who have added a fb-token to their contactinfo (e.g.

comment:5 Changed 6 years ago by karsten

Would the suggested new contact parameter work for you? It would work like this (not implemented yet):<fb-token:5sR_K_zs2wM=>

Or rather, I'm not sure about <, :, =, and > in that URL. They'd probably have to be escaped. And I'd have to check if Tomcat messes with these characters in some way, though I don't think so.

The semantics would be that you could specify one or more space-separated values for the contact parameter, and you'd receive all relays that have this string or all these strings in their contact line, in any order.

You could further narrow down results by specifying the search parameter or other parameters. The result would be the intersection of relays matching all parameters.

If this works for you, I can implement this feature quite easily.

comment:6 Changed 6 years ago by sjmurdoch

That proposal would work well for my purpose. Thanks.

I think I would use it in two ways. One would be to search for "<fb-token:" to find all people who have added a token, and another would be to search for a particular token such as "<fb-token:5sR_K_zs2wM=>".

I'm not sure what is best to do if a space is in the query. For my purpose, the fb-token doesn't contain spaces so it doesn't matter and your suggestion of treating them as two AND queries is fine. I'm not sure if anyone would want to search for a phrase containing spaces. For searching names, the mechanism you propose sounds good because it would handle people swapping firstname and lastname or having a middle initial.

comment:7 Changed 6 years ago by karsten

Resolution: implemented
Status: newclosed

Implemented. The following two URLs now work:

See the new contact parameter in the specification for details. Closing.

Note: See TracTickets for help on using tickets.