[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #8614 [BridgeDB]: BridgeDB should be able to return multiple transport types at the same time
#8614: BridgeDB should be able to return multiple transport types at the same time
-----------------------+----------------------------------------------------
Reporter: asn | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone:
Component: BridgeDB | Version:
Keywords: important | Parent: #8615
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by sysrqb):
Replying to [comment:7 sysrqb]:
> One thing to note, when a user applies different filters they will
(likely) receive different bridges. I think we should decide that this is
ok before this is merged.
I don't think this is ok, but I also don't think we can accomplish this
goal without creating a temporary cache containing the mapping
area->distributed bridges. This has numerous consequences, but it will
also provide a significant improvement with regard to how long it takes to
scrape new bridges. I propose the cache be indexed by an hmac or salted
double hash of the ip addr area and we rotate the key/salt and clear the
cache every three hours (so that the rate-limiting occurs in the same time
period as the email dist).
Advantage: everyone within the same /24 receives the same bridges
Disadvantage: Every request sourced from within a small geographical
location receives the same bridges. =\
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8614#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs