[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #12547 [BridgeDB]: Get analysed data from bridge reachability tests to tor-devs
#12547: Get analysed data from bridge reachability tests to tor-devs
--------------------------+---------------------------------------
Reporter: hellais | Owner: sysrqb
Type: task | Status: new
Priority: normal | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords: ooni, bridge-reachability
Actual Points: | Parent ID: #12544
Points: |
--------------------------+---------------------------------------
Comment (by asn):
I assume that originally the data will be exposed as an HTTP dir
listing, similar to: https://ooni.torproject.org/reports/0.1/
That's fine since it allows Tor developers to quickly search for
bridget results (to see if/when bridges got blocked) and it can also
act as an initial interface for people to fetch data to test their
visualization ideas.
A question here is how the directory listing should look like, to make
it easier for humans to go through it. My use case, is going over the
results to find whether a bridge was blocked in a given day. Here is a
directory listing format that could be helpful for this use case:
{{{
bridge_reachability/<country>/<day>/br_<timestamp>_<country>.yaml
}}}
for example:
{{{
bridge_reachability/CN/2014-09-03/br_2014-09-03T15:40:00_US.yaml
bridge_reachability/US/2014-09-05/br_2014-09-05T22:10:00_US.yaml
bridge_reachability/US/2014-09-05/br_2014-09-05T23:10:00_US.yaml
}}}
Any other ideas?
This use case will potentially be deprecated after visualization is
done. The visualization should make it easy to check whether a bridge
was blocked in a given date, without having to go over all the reports
of that day.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12547#comment:3>
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