Re: [tor-bugs] #10128 [Atlas]: Search and family very limited

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#10128: Search and family very limited
----------------------------+-------------------------------
     Reporter:  kwadronaut  |      Owner:  hellais
         Type:  defect      |     Status:  needs_information
     Priority:  normal      |  Milestone:
    Component:  Atlas       |    Version:
   Resolution:              |   Keywords:
Actual Points:              |  Parent ID:
       Points:              |
----------------------------+-------------------------------
Changes (by karsten):

 * status:  new => needs_information


Comment:

 Replying to [ticket:10128 kwadronaut]:
 > Seems that search is very limited (maybe intentional?)

 Full-text search in Atlas/Onionoo is limited for a reason: it's quite
 expensive to perform searches on many fields, so we limited those fields
 to the most important ones.  We also shouldn't extend this set of fields
 now, because we may want to extend the search feature to more than just
 the past 7 days soon, and we shouldn't make things more complicated than
 they are.

 > I get no results in the following cases:
 >
 > * If I click the family members on a node (ie:
 https://atlas.torproject.org/#details/2A431444756B0E7228A7918C85A8DACFF7E3B050
 )

 Quite possible that those nodes are not running.  In theory, there's no
 reason why searching for family members of a node shouldn't work.

 > * If I search by location (Tried Hong Kong, there are only ~16 nodes)

 Onionoo has a `country` parameter that allows searching by location, but
 Atlas does not use it.  That is mostly an interface problem though.  I
 could imagine an extended search where you pick a country, but I'll leave
 that to phw and hellais.

 > * If I search by hostname (ie: tor.bitmask.net )

 True, that's not supported by Onionoo nor Atlas.

 > And it goes totally haywire (backend error) if try:
 > * to search for a hostname with 2 subdomains

 Can you be more specific what search does not work?  Atlas shouldn't give
 you a backend error.  It should either validate searches before sending
 them to the Onionoo backend, or maybe there's really an error in Onionoo
 that we should fix.

 > * put the data from a 'Contact' into the search field (sysdev {at} leap
 {dot} se)

 Onionoo has a `contact` parameter that could be used here; see the
 `country` part above.  But Atlas shouldn't say "backend error" here
 either.  I just opened #10184 for this.

 > I took all data from
 https://atlas.torproject.org/#details/7DE636B00A0B5C4AEDBACA9F44C801F3E00B94AD

 Changing to needs_information, because I think I addresses all possible
 bugs.  It would be interesting to learn more about the "backend errors".
 If you have more such cases, please let us know.  Thanks for the report!

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10128#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs