Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-22T11:55:46Zhttps://gitlab.torproject.org/legacy/trac/-/issues/32908Only re-build missing incremental .mar files2020-06-22T11:55:46ZGeorg KoppenOnly re-build missing incremental .mar filesSometimes we only want to re-build a subset of incremental .mar files but that does not seem to be possible right now.
The way this could handled is like proceed with regular artifact builds: only the missing parts are (re-)built. Thus,...Sometimes we only want to re-build a subset of incremental .mar files but that does not seem to be possible right now.
The way this could handled is like proceed with regular artifact builds: only the missing parts are (re-)built. Thus, for incremental .mar files this would mean we'd delete the ones we want to rebuilt and `make incrementals-release` (assuming we are in a release build process) would be smart enough to just re-build the deleted ones.https://gitlab.torproject.org/legacy/trac/-/issues/34026Cannot change Background Color in Preferences2020-06-22T12:02:33ZTracCannot change Background Color in PreferencesUsing Tor 9.0.9 , based on Firefox 68.7.0esr,
2019 iMac running Catalina 10.15.4
In preferences, I can change the font color, but not the background color.
I have no problem changing everything in Firefox.
**Trac**:
**Username**...Using Tor 9.0.9 , based on Firefox 68.7.0esr,
2019 iMac running Catalina 10.15.4
In preferences, I can change the font color, but not the background color.
I have no problem changing everything in Firefox.
**Trac**:
**Username**: Tinkerhttps://gitlab.torproject.org/legacy/trac/-/issues/24070Generate an event if more than X relays join2021-11-29T14:35:53ZirlGenerate an event if more than X relays joinWe should decide on what this threshold is.
If more than the threshold of relays join, generate an EVENT status update and send to all channels subscribed to the EVENT type.We should decide on what this threshold is.
If more than the threshold of relays join, generate an EVENT status update and send to all channels subscribed to the EVENT type.https://gitlab.torproject.org/legacy/trac/-/issues/24071Generate an event if the most used Tor version changed2021-11-29T14:35:54ZirlGenerate an event if the most used Tor version changedIf the most popular Tor version used (by relays) has changed, generate an EVENT and send to all microblog accounts subscribed to EVENT updates.If the most popular Tor version used (by relays) has changed, generate an EVENT and send to all microblog accounts subscribed to EVENT updates.https://gitlab.torproject.org/legacy/trac/-/issues/24073Generate an event if there is a major relay outage2021-11-29T14:35:54ZirlGenerate an event if there is a major relay outageGenerate an event if there is a major outage of relays. We should decide on thresholds for relay counts/consensus weight. This may actually be just a part of #24070.Generate an event if there is a major outage of relays. We should decide on thresholds for relay counts/consensus weight. This may actually be just a part of #24070.https://gitlab.torproject.org/legacy/trac/-/issues/15035URI format for bridges2022-03-15T17:14:23ZeighthaveURI format for bridgesRight now, according to @n8fr8, this is the URI format for the bridge URIs:
bridge://obfs3+99.999.99.999%3A10223+c6fa110ebcd8979b0a57617bf2d6e82bbecd287d+%0A
There is a problem with this format because it doesn't follow the URI RFC so ...Right now, according to @n8fr8, this is the URI format for the bridge URIs:
bridge://obfs3+99.999.99.999%3A10223+c6fa110ebcd8979b0a57617bf2d6e82bbecd287d+%0A
There is a problem with this format because it doesn't follow the URI RFC so that standard URI parsers won't parse it very well. Adding the `//` after `bridge:` makes it a "hierarchical" URI, which means that it has the standard sections of authority, user info, host, port, path, query, and fragment. But the above URI will just stick all of the text in the "authority" part, but that section can't be broken down into the standard parts of the "authority", i.e. user info, host, and port.
To keep the same data format, then this URI should be an "opaque" URI. That just means removing the `//`. So that makes it like a `mailto:` URI.
Otherwise, the data could be refactored to fit into the standard parts for a hierarchical URI, then standard URI parsing classes will be able to parse it. For example, android.net.Uri, java.net.URL, etc. That would make the URI look something like this:
`obfs4://xx.xx.xxx.xxx:18965/asdasdasldkasjlasjkdd4?cert=3wYasdasdasdasBmsIat+RMmMDV5BV4jDvXuzasdasdasdas8Dz8J1MUvLKHKaQ&iat-mode=0`
* `getScheme()` would be bridge type
* `getAuthority()` would be IP and port number
* `getHost()` would be IP
* `getPort()` would be port number
* `getPath()` would be this thing: `95151988dc29fccb4f610a1c700a1ddf7d5ffbd4`
* then `cert=`, `iat-mode=`, etc. would be in the query string
The downside of this approach is that there could only be a single bridge per URI, but maybe that's not so bad.Nathan FreitasNathan Freitas