Opened 7 years ago

Last modified 3 years ago

#9323 new enhancement

Option to start as a bridge by default, but change to relay if bw is super-high.

Reported by: saint Owned by: chiiph
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay tor-bridge usability
Cc: griffinboyce@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


There are some minor ongoing problems with Tor speed, which has cascade effects in user adoption and accessibility.

If there were a type of node that starts as a middle relay and changes into a bridge if average speed in the past day were unacceptably low, that could dramatically improve mean transfer time. And then, if conditions improved, a convertible node would change from a bridge back to a relay.

Given that bridges become unusable in the most high-risk areas in just a few days (Winter & Lindskag 2012), its side effect of increasing the bridge population would be a very positive thing.

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by saint

Cc: griffinboyce@… added
Component: TorVidalia
Owner: set to chiiph

(changed component to Vidalia. See also #9324, which tackles user uncertainty and performance in a different way)

comment:2 Changed 7 years ago by hsn

If node was relay, then its useless to change it into bridge because its blocked already.

comment:3 Changed 7 years ago by nickm

Component: VidaliaTor
Keywords: tor-relay added; Vidalia relay node bridge performance removed
Milestone: Tor: unspecified

hsn is right: starting as a bridge makes much more sense.

Moving this back to Tor, since absolutely nobody is working on Vidalia, and this ticket could plausibly go either way.

comment:4 Changed 3 years ago by nickm

Keywords: tor-bridge usability added
Severity: Normal
Summary: Convertible node typeOption to start as a bridge by default, but change to relay if bw is super-high.
Note: See TracTickets for help on using tickets.