Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2017-12-06T04:45:21Zhttps://gitlab.torproject.org/legacy/trac/-/issues/5050tor times out websites with .onion2017-12-06T04:45:21ZTractor times out websites with .onioni really need help i have been trying to get on .onion websites but they all just timeout and i get a error message
**Trac**:
**Username**: samgyeri really need help i have been trying to get on .onion websites but they all just timeout and i get a error message
**Trac**:
**Username**: samgyerhttps://gitlab.torproject.org/legacy/trac/-/issues/3714Speed up application logic/loading time of the index page2020-06-13T00:26:09ZcypherpunksSpeed up application logic/loading time of the index pageIt'd be nice to show all of the routers on a single page for some clients, but an unpaged index page loads far too slow to consider doing this at the moment. Even the paged index page loads slower than it should. To remedy this, an upper...It'd be nice to show all of the routers on a single page for some clients, but an unpaged index page loads far too slow to consider doing this at the moment. Even the paged index page loads slower than it should. To remedy this, an upper bound on the "Relays Per Page" parameter has been set at 200 relays per page.
Preliminary testing hints that this may be a problem may be related to the speed of Django's template logic, but there are likely other reasons that the page loads so slowly.https://gitlab.torproject.org/legacy/trac/-/issues/3716Add "hostname" column to index page.2020-06-13T00:26:10ZcypherpunksAdd "hostname" column to index page.Some clients may miss the hostname column from the old implementation of TorStatus.
Currently, this information is only available on a per-relay basis -- when a client views the detail page for a router. When this page is requested, the...Some clients may miss the hostname column from the old implementation of TorStatus.
Currently, this information is only available on a per-relay basis -- when a client views the detail page for a router. When this page is requested, the hostname is looked up. It'd be nice to have a hostname column in the `cache.active_relay` table so that it could be cheaply displayed in the index page. This would also mean that hostnames would not have to be looked up whenever a router detail page is requested.
This should probably be implemented on the database level by keeping a table consisting of an `INET`, a `TIMESTAMP`, and a `CHARACTER VARYING(255)`, with indexes on the `INET` and `TIMESTAMP`. Then, when the join to create the `cache.active_relay` table is performed, we can LEFT JOIN that result with the hostname table on the IP addresses. We'd lookup hostnames whenever a new IP address is added to the table, whenever we have a hostname that more than (interval) old and the IP address is in the active_statusentry table, or an IP address is added to the active_statusentry table that does not exist in the hostname table. We'd delete hostnames that are older than (interval) old.https://gitlab.torproject.org/legacy/trac/-/issues/3931Display Options in TorStatus have duplicate entries2020-06-13T00:31:00ZKarsten LoesingDisplay Options in TorStatus have duplicate entriesComment from the blog:
"There are multiple selections of the same title in the display options add/remove up/down page thing. Very confusing."
I have no idea what causes this problem. jfehr, do you have any suggestions how I could fin...Comment from the blog:
"There are multiple selections of the same title in the display options add/remove up/down page thing. Very confusing."
I have no idea what causes this problem. jfehr, do you have any suggestions how I could find out?