Skip to content

Tags

Tags give the ability to mark specific points in history as being important
  • v0.8.0
    38fd4f98 · Release 0.8.0 ·
    v0.8.0
    
  • v0.7.0
    93adeba7 · Release 0.7.0 ·
    
    
  • v0.6.0
    e1492850 · Release 0.6.0 ·
    
    
  • v0.5.0
    af8bb20e · Release 0.5.0 ·
    
    
  • v0.4.1
    26069fe2 · Bump to 0.4.1 ·
    Changed
    
    - If the relay to measure is an exit, put it in the exit position and choose a
      non-exit to help. Previously the relay to measure would always be the first
    hop. (GH#181)
    - Try harder to find a relay to help measure the target relay with two changes.
      Essentially: (1) Instead of only picking from relays that are 1.25 - 2.00
    times faster than it by consensus weight, try (in order) to find a relay that
    is at least 2.00, 1.75, 1.50, 1.25, or 1.00 times as fast. If that fails,
    instead of giving up, (2) pick the fastest relay in the network instead of
    giving up. This compliments the previous change about measuring target exits in
    the exit position.
    
    Fixed
    
    - Exception that causes sbws to fall back to one measurement thread. We first
      tried fixing something in this area with `88fae60bc` but neglected to
    remember that `.join()` wants only string arguments and can't handle a `None`.
    So fix that.
    - Exception when failing to get a relay's `ed25519_master_key` from Tor and
      trying to do `.rstrip()` on a None.
    - `earliest_bandwidth` being the newest bw not the oldest (thanks juga0)
    - `node_id` was missing the character "$" at the beginning
    
  • v0.4.0
    e0118941 · Bump version to 0.4.0 ·
    
    
  • v0.3.0
    
    
  • v0.2.0
    6212ede3 · Bump to 0.2.0 ·
    sbws now launches tor for itself
    
    Significant changes in [tor] section of config, hence the bump from
    0.1.2 to 0.2.0 (a "major" bump in these pre-1.0.0 times). Most likely
    you can leave your [tor] section empty now.
    
  • v0.1.1
    c95ffb1f · Bump version to 0.1.1 ·
    
    
  • v0.1.0