Re: [tor-bugs] #21588 [Metrics/Metrics website]: Rewrite the censorship detector used by the Tor Metrics website in Java

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#21588: Rewrite the censorship detector used by the Tor Metrics website in Java
-------------------------------------+------------------------------
 Reporter:  karsten                  |          Owner:  metrics-team
     Type:  enhancement              |         Status:  new
 Priority:  Medium                   |      Milestone:
Component:  Metrics/Metrics website  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:                           |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+------------------------------

Comment (by iwakeh):

 Replying to [comment:3 karsten]:
 > Sure, removing the keyword and discussing more internally works for me!

 Phhew :-)

 >
 > I guess one of my assumptions above was that step 4 wouldn't produce
 more than 100 or 200 lines of Java code, where we wouldn't have to worry
 much about design and could easily transform the output into whatever
 design we want as part of step 5.

 Well, we don't want to re-implement the Java re-implementation ;-)
 (And there might be more lines depending on the country code setup, which
 might also be used elsewhere ...)

 >
 > Another assumption was that reading the report in steps 1 and 2 wouldn't
 be necessary, because there's plenty of sample data to test that the
 rewrite produces the same results as the original.

 As this is going to be done by a Java person the python might be less
 readable to them than the report, which really describes the
 implementation.

 >
 > But I made those assumptions without having looked at the code for years
 (pretty much since 2011).  And I believe that you're more into this topic
 right now than I am, because of your work on that other technical report.
 Would you want to give this a few more thoughts, in particular whether we
 can turn this into a mostly self-contained task for a new volunteer?

 Sure, I'll think about this. (Actually, that was already on my list of
 suggestions for MetricsWeb.)

 >   I agree that we should be pretty sure what we want before asking
 somebody else to do it. :)

 And, that way the task will be more rewarding for a volunteer.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21588#comment:4>
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