| Age | Commit message (Collapse) | Author |
|---|
|
version adds protocol overhead and probably is not that effective.
|
|
|
|
|
|
|
|
There were cases in the code where time calculations and comparisons were overflowing and causing connection instability. This will keep time calculations within expected ranges.
|
|
|
|
|
|
|
|
|
|
|
|
then passed to handler functions resulting from a call.
|
|
rapid setup. Will need to revisit later.
|
|
normally use expired paths. Expired paths might still be tried if nothing else is reachable.
|
|
|
|
|
|
(will be replaced with federation stuff).
|
|
|
|
received-on address to eliminate false symmetric classification.
|
|
|
|
since this supersedes it.
|
|
|
|
1.1.3 (dev)
|
|
|
|
|
|
some spurious resets under symmetric NATs), and simplify some logic.
|
|
|
|
rate limiting in PUSH_DIRECT_PATHS for now (but we will do something else to mitigate amplification attacks)
|
|
in SelfAwareness (will need to test ALL versions in the wild with this), and (3) add more TRACE instrumentation to Cluster.
|
|
|
|
|
|
|
|
full identity of peers instead of just address.
|
|
|
|
won't keep resetting the same scope repeatedly.
|
|
|
|
|
|
assign different external IPs for each external destination. Keeping just one known surface could create a race condition.
|
|
|
|
|
|
|
|
|
|
scope.
|
|
|
