| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
task/5430
Conflicts:
templates/search/do.html
|
| | |
| |
| |
| |
| |
| |
| | |
* Displays the search query for searches
* Displays "Top 10 Relays by Consensus Weight" for the top 10 page to
avoid confusion as to why the top 10 are not sorted by bandwidth
(#5430)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Adds a navbar to the top of the page for Home, About and Top 10
Relays.
* Re-uses the search results view using a hardcoded Onionoo URL (taken
from Globe) to show a list of the top 10 relays by consensus weight.
* Disables sorting by default of the datatables, and disables saving of
state for sorting options. This allows the list of the top 10 to be
sorted by consensus weight as reported by Onionoo, though manual
sorting is still possible as before.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Added the ability for errors to be passed along when rendering result
sets, to display an error or warning message while still allowing
a result set to be rendered.
* Results are only rendered once all the requests have succeeded (or
failed), not every time there is a response. This greatly improves
the performance and now up to 50 results can be rendered reasonably.
* Limits the result set to a maximum of 50 results, introducing a new
error message when this number is exceeded. (Fixes: #15395)
* Introduces a new error message when an empty string is passed and
fixed the rendering of that error message by displaying it. (Fixes:
#19372)
* Thanks to karsten and hellais for their help on this patch. (:
|
| |
|
|
| |
Signed-off-by: Philipp Winter <phw@torproject.org>
|
| |
|
|
| |
instead.
|
| |
|
|
|
|
| |
If Atlas cannot get a response from Onionoo, it's not always the user's
fault. This fix changes the error message to make that clear.
Hopefully, this will result in less bug reports when Onionoo is offline.
|
| |
|
|
|
|
|
| |
The bridge pool assignment field is now deprecated and no longer
provided by Onionoo. At the same time, Onionoo now provides a field
containing a bridge's transport protocols. This patch makes Atlas show
the transport protocols instead of the pool assignment.
|
| |
|
|
|
| |
This graph is going to be removed from Onionoo as part of #13674.
Replace it with the middle probability graph.
|
| | |
|
| |
|
|
|
|
|
|
| |
Onionoo was recently extended and now understands several advanced
search expressions. This commit explains to users how to use these
expressions.
This fixes <https://bugs.torproject.org/13599>.
|
| |
|
|
|
|
|
| |
Add a column representing router type (Bridge/Router) to the search
view.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
| |
|
|
|
|
|
|
| |
Onionoo provides another API method for bridges - information about
clients that used the bridge. Let Atlas provide average client count
graphs.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
| |
|
|
|
|
|
|
| |
It is possible to issue search to Onionoo using hashes of fingerprints
and hashes of hashes of fingerprints. Thus always hash a fingerprint
before searching. Onionoo will return correct results in any case.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
| |
|
|
| |
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
| |
|
|
|
|
|
|
|
|
| |
Bridges have fewer fields compared to plain relays. It does not make
sense to have several if(!bridge) constructions in the main template, so
rename main.html to router.html and add a special bridge.html template.
As we are at it, split away error handling from template - it is now
done by a separate error.html.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
| |
|
|
|
|
|
|
| |
Onionoo provides information about bridges in nearly the same way as it
does for relays. So this commit extends relay model with two more
properties and adds bridges to the list of relays for processing.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
| |
If present, the "exit_policy_v6_summary" data is displayed right underneath its
IPv4 equivalent. In addition, we reduce the vertical size of the <pre>
environment so that the additional IPv6 box doesn't waste too much space.
This should fix bug <https://bugs.torproject.org/12124>.
|
| |
|
|
|
|
|
|
| |
When moving the mouse over the bandwidth value under "Advertised
Bandwidth", a tool tip shows the bandwidth rate, burst, and the observed
bandwidth of the respective relay.
This should fix <https://bugs.torproject.org/11195>.
|
| |
|
|
|
| |
Having code run in your browser doesn't automatically make it open source code.
While it's probably meant as a joke, it might confuse users.
|
| |
|
|
|
| |
Atlas is released under 2-Clause BSD. The license template was taken from
<http://opensource.org/licenses/BSD-2-Clause>.
|
| |
|
|
| |
Fixes <https://bugs.torproject.org/9920>.
|
| |
|
|
|
| |
At this point, Atlas is not able to extract bridge information from onionoo
data. We shouldn't pretend that it does.
|
| |
|
|
| |
Fixes <https://bugs.torproject.org/9015>.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
If a relay is offline, write 'Last Known Properties' instead of merely
'Properties' and display an additional field called 'Last Seen'. That should
cause less confusion.
|
| | |
| |
| |
| | |
That should cause less confusion for users.
|
| |/
|
|
| |
Thanks to "rndm" for the patch.
|
| |
|
|
| |
should provide.
|
| |
|
|
| |
goes beyond the scope of a simple README.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
should fix ticket #9231.
|
| |
|
|
| |
true.
|
| |
|
|
|
|
| |
Previously, we'd display the dir address of the previously shown relay.
Fixes #9302, similar to #9281.
|
| |
|
|
|
|
| |
Previously, we'd display the contact of the previously shown relay.
Fixes #9281.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
