Coordination of censorship analysis tool
Hi Deepak, Utsarga, Tobias, and Yiwen! The four of you recently expressed interest in the censorship analyser project [1]. At this point, we only have a paper which discusses what we want from the tool [2]. There is no official code repository but Tobias recently started experimenting with some modules [3]. It would be great if you all could join forces and split the workload. I understand that some of you have some constraints from your respective university. As a result, could you please reply to this email (don't forget to CC tor-dev) and sum up what you can/want to do and if you are under any constraints such as a time-limited class project? We can then see if and how we can divide the project into several sub projects. Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better. There's also #ooni for OONI-specific questions (most of the developers are in Europe, so you might have to wait for answers). I am not sure how familiar you are with git but it is certainly the preferred version control system in and around Tor. So this might be a good opportunity to learn how to use it :) [1] https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer [2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf [3] https://tobiasrang.com/svn/analyser/ Cheers, Philipp
ons 2014-02-05 klockan 15:29 +0100 skrev Philipp Winter:
Hi Deepak, Utsarga, Tobias, and Yiwen!
The four of you recently expressed interest in the censorship analyser project [1]. At this point, we only have a paper which discusses what we want from the tool [2]. There is no official code repository but Tobias recently started experimenting with some modules [3].
It would be great if you all could join forces and split the workload. I understand that some of you have some constraints from your respective university. As a result, could you please reply to this email (don't forget to CC tor-dev) and sum up what you can/want to do and if you are under any constraints such as a time-limited class project? We can then see if and how we can divide the project into several sub projects.
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better. There's also #ooni for OONI-specific questions (most of the developers are in Europe, so you might have to wait for answers). I am not sure how familiar you are with git but it is certainly the preferred version control system in and around Tor. So this might be a good opportunity to learn how to use it :)
[1] https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer [2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf [3] https://tobiasrang.com/svn/analyser/
Cheers, Philipp
Hey everyone. I'm doing this in my spare time; not as part of anything school-related. As such, I'm not under any real time constraints. As for what I can/want to do, I do have some prior experience with Twisted, and I've familiarized myself a bit with ooni's API. If the project is to be divided into sub-projects, perhaps the logical thing would be for me to continue working on implementing tests. When it comes to version control, I agree that Git is the best option. I've been meaning to set up a Git-repo on my server and use that instead of my current svn-repo, so I guess that is one option. Although It might be better to host it on Tors servers. You can find me in #tor-dev under the nick edagar. Tobias
Hi everyone! Like Tobias, I am willing to devote my spare time to the tool and see through its completion and further maintenance. I am not really bounded by any time constraints. Currently I am familiarizing myself with Twisted and OONI and excited about kick-starting the project as soon as possible! Dividing the project into sub-parts seems like a nice idea. I welcome any suggestions on how we can go about it. Tobias: We could use git until we are good enough to push it on the Tor servers. What do you say? You can find me in #tor-dev as dkathayat. Cheers. Deepak On Thu, Feb 6, 2014 at 3:42 AM, Tobias Rang <tobiasrang@gmail.com> wrote:
ons 2014-02-05 klockan 15:29 +0100 skrev Philipp Winter:
Hi Deepak, Utsarga, Tobias, and Yiwen!
The four of you recently expressed interest in the censorship analyser project [1]. At this point, we only have a paper which discusses what we want from the tool [2]. There is no official code repository but Tobias recently started experimenting with some modules [3].
It would be great if you all could join forces and split the workload. I understand that some of you have some constraints from your respective university. As a result, could you please reply to this email (don't forget to CC tor-dev) and sum up what you can/want to do and if you are under any constraints such as a time-limited class project? We can then see if and how we can divide the project into several sub projects.
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better. There's also #ooni for OONI-specific questions (most of the developers are in Europe, so you might have to wait for answers). I am not sure how familiar you are with git but it is certainly the preferred version control system in and around Tor. So this might be a good opportunity to learn how to use it :)
[1] https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer [2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf [3] https://tobiasrang.com/svn/analyser/
Cheers, Philipp
Hey everyone.
I'm doing this in my spare time; not as part of anything school-related. As such, I'm not under any real time constraints.
As for what I can/want to do, I do have some prior experience with Twisted, and I've familiarized myself a bit with ooni's API. If the project is to be divided into sub-projects, perhaps the logical thing would be for me to continue working on implementing tests.
When it comes to version control, I agree that Git is the best option. I've been meaning to set up a Git-repo on my server and use that instead of my current svn-repo, so I guess that is one option. Although It might be better to host it on Tors servers.
You can find me in #tor-dev under the nick edagar.
Tobias
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On Thu, Feb 6, 2014 at 8:57 PM, Deepak Kathayat <deepak.mk17@gmail.com> wrote:
Hi everyone! Like Tobias, I am willing to devote my spare time to the tool and see through its completion and further maintenance. I am not really bounded by any time constraints. Currently I am familiarizing myself with Twisted and OONI and excited about kick-starting the project as soon as possible! Dividing the project into sub-parts seems like a nice idea. I welcome any suggestions on how we can go about it. Tobias: We could use git until we are good enough to push it on the Tor servers. What do you say? You can find me in #tor-dev as dkathayat.
Cheers. Deepak
On Thu, Feb 6, 2014 at 3:42 AM, Tobias Rang <tobiasrang@gmail.com> wrote:
ons 2014-02-05 klockan 15:29 +0100 skrev Philipp Winter:
Hi Deepak, Utsarga, Tobias, and Yiwen!
The four of you recently expressed interest in the censorship analyser project [1]. At this point, we only have a paper which discusses what we want from the tool [2]. There is no official code repository but Tobias recently started experimenting with some modules [3].
It would be great if you all could join forces and split the workload. I understand that some of you have some constraints from your respective university. As a result, could you please reply to this email (don't forget to CC tor-dev) and sum up what you can/want to do and if you are under any constraints such as a time-limited class project? We can then see if and how we can divide the project into several sub projects.
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better. There's also #ooni for OONI-specific questions (most of the developers are in Europe, so you might have to wait for answers). I am not sure how familiar you are with git but it is certainly the preferred version control system in and around Tor. So this might be a good opportunity to learn how to use it :)
[1] https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer [2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf [3] https://tobiasrang.com/svn/analyser/
Cheers, Philipp
Hey everyone.
I'm doing this in my spare time; not as part of anything school-related. As such, I'm not under any real time constraints.
As for what I can/want to do, I do have some prior experience with Twisted, and I've familiarized myself a bit with ooni's API. If the project is to be divided into sub-projects, perhaps the logical thing would be for me to continue working on implementing tests.
When it comes to version control, I agree that Git is the best option. I've been meaning to set up a Git-repo on my server and use that instead of my current svn-repo, so I guess that is one option. Although It might be better to host it on Tors servers.
You can find me in #tor-dev under the nick edagar.
Tobias
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hello Guys, Until recently, I wasn't aware of the censorship analysis project that is being discussed here. I find it interesting and I would like to help out with the development during my free time. Cheers! -- Abhiram Chintangal
Hi everyone, I'm working on the censorship analyzer for a semester long independent research project. Because of this, I need to finish my work by May 6. Philipp has told me this isn't a terribly large amount of time, so it's great that there's a lot of us working on it. Does anyone have any ideas on how we can split up the work? Thanks, Utsarga On Fri, Feb 7, 2014 at 1:45 PM, Abhiram Chintangal < abhiram.chintangal@gmail.com> wrote:
On Thu, Feb 6, 2014 at 8:57 PM, Deepak Kathayat <deepak.mk17@gmail.com> wrote:
Hi everyone! Like Tobias, I am willing to devote my spare time to the tool and see through its completion and further maintenance. I am not really bounded by any time constraints. Currently I am familiarizing myself with Twisted and OONI and excited about kick-starting the project as soon as possible! Dividing the project into sub-parts seems like a nice idea. I welcome any suggestions on how we can go about it. Tobias: We could use git until we are good enough to push it on the Tor servers. What do you say? You can find me in #tor-dev as dkathayat.
Cheers. Deepak
On Thu, Feb 6, 2014 at 3:42 AM, Tobias Rang <tobiasrang@gmail.com> wrote:
ons 2014-02-05 klockan 15:29 +0100 skrev Philipp Winter:
Hi Deepak, Utsarga, Tobias, and Yiwen!
The four of you recently expressed interest in the censorship analyser project [1]. At this point, we only have a paper which discusses what we want from the tool [2]. There is no official code repository but
Tobias
recently started experimenting with some modules [3].
It would be great if you all could join forces and split the workload. I understand that some of you have some constraints from your respective university. As a result, could you please reply to this email (don't forget to CC tor-dev) and sum up what you can/want to do and if you are under any constraints such as a time-limited class project? We can then see if and how we can divide the project into several sub projects.
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better. There's also #ooni for OONI-specific questions (most of the developers are in Europe, so you might have to wait for answers). I am not sure how familiar you are with git but it is certainly the preferred version control system in and around Tor. So this might be a good opportunity to learn how to use it :)
[1]
https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer
[2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf [3] https://tobiasrang.com/svn/analyser/
Cheers, Philipp
Hey everyone.
I'm doing this in my spare time; not as part of anything school-related. As such, I'm not under any real time constraints.
As for what I can/want to do, I do have some prior experience with Twisted, and I've familiarized myself a bit with ooni's API. If the project is to be divided into sub-projects, perhaps the logical thing would be for me to continue working on implementing tests.
When it comes to version control, I agree that Git is the best option. I've been meaning to set up a Git-repo on my server and use that instead of my current svn-repo, so I guess that is one option. Although It might be better to host it on Tors servers.
You can find me in #tor-dev under the nick edagar.
Tobias
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hello Guys,
Until recently, I wasn't aware of the censorship analysis project that is being discussed here. I find it interesting and I would like to help out with the development during my free time.
Cheers!
-- Abhiram Chintangal _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi everyone! Like Tobias, I am willing to devote my spare time to the tool and see through its completion and further maintenance. I am not really bounded by any time constraints. Currently I am familiarizing myself with Twisted and OONI and excited about kick-starting the project as soon as possible! Dividing the project into sub-parts seems like a nice idea. I welcome any suggestions on how we can go about it. Tobias: We could use git until we are good enough to push it on the Tor servers. What do you say? You can find me in #tor-dev as dkathayat.
Cheers. Deepak
So I've set up a Git repo. Since a few of us (including myself) seem to be pretty green when it comes to git, I figured a less formal setting might be a good way to learn. I'm not sure why, but so far I couldn't get git clone to work over http. The gitweb[1] is working though, so read-access could be handled using that until I can figure that out. For commit rights: just email me your ssh public rsa key. [1] http://gitweb.tobiasrang.com/ Tobias
Greetings! I am very interested in helping out with this project in my free time (in addition to the other Tor related projects that I am already trying to work on in my free time)... I am already somewhat familiar with Twisted and the OONI api: I'm currently working on a NFQueue traceroute test for ooni-probe... ( I'm "dawuud" on #tor-dev and #ooni ) I am located in Europe... and my free time is going to be somewhat limited... since I got recently acquired a job. Cheers! On Wed, Feb 5, 2014 at 2:29 PM, Philipp Winter <phw@nymity.ch> wrote:
Hi Deepak, Utsarga, Tobias, and Yiwen!
The four of you recently expressed interest in the censorship analyser project [1]. At this point, we only have a paper which discusses what we want from the tool [2]. There is no official code repository but Tobias recently started experimenting with some modules [3].
It would be great if you all could join forces and split the workload. I understand that some of you have some constraints from your respective university. As a result, could you please reply to this email (don't forget to CC tor-dev) and sum up what you can/want to do and if you are under any constraints such as a time-limited class project? We can then see if and how we can divide the project into several sub projects.
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better. There's also #ooni for OONI-specific questions (most of the developers are in Europe, so you might have to wait for answers). I am not sure how familiar you are with git but it is certainly the preferred version control system in and around Tor. So this might be a good opportunity to learn how to use it :)
[1] https://www.torproject.org/getinvolved/volunteer.html.en#censorshipAnalyzer [2] http://www.cs.kau.se/philwint/pdf/foci2013.pdf [3] https://tobiasrang.com/svn/analyser/
Cheers, Philipp _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
We recently had a small IRC chat in #tor-dev about the project. Deepak was wondering if the project could be implemented as browser extension. It would be interesting to explore this direction in more detail -- perhaps in parallel to an implementation based on OONI. Another important side-project I didn't mention yet is unit and integration testing. For last year's GSoC, EvilGenius was developed which could be helpful: <https://github.com/TheTorProject/EvilGenius> Finally, there's building and bundling. Once there's code, we need a way to bundle it into a single executable. Cheers, Philipp
On 02/05/2014 07:59 PM, Philipp Winter wrote:
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better.
Should I create a temporary wiki-page at tor/wiki ? It seems like a good idea to keep us on all on the same page. thanks!
On Wed, Feb 12, 2014 at 6:15 AM, Abhiram Chintangal < abhiram.chintangal@gmail.com> wrote:
On 02/05/2014 07:59 PM, Philipp Winter wrote:
Regarding development and coordination: This mailing list is great for high-latency, broad, conceptual, and public discussions. For low-latency questions, the #tor-dev channel on OFTC is better.
Should I create a temporary wiki-page at tor/wiki ? It seems like a good idea to keep us on all on the same page.
Also, would it be possible to have a chat over #tor-dev sometime, where each of us could discuss in length about how the work could be divided and the amount of time one would be willing to put in for their part? Thanks.
thanks!
_______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On Wed, Feb 12, 2014 at 12:32:27PM +0800, Deepak Kathayat wrote:
Also, would it be possible to have a chat over #tor-dev sometime, where each of us could discuss in length about how the work could be divided and the amount of time one would be willing to put in for their part?
Sounds like a great idea. Do you feel like creating a Doodle calendar or something similar? :) Cheers, Philipp
Hi all, I have to finish part of the project before May 2. And I am starting to implement Website Probing (section 3.1.3 in the paper). My plan is to implement 3.1.3 and then see how far I can go. Thanks, Yiwen On Feb 12, 2014, at 2:37 AM, Philipp Winter <phw@nymity.ch> wrote:
On Wed, Feb 12, 2014 at 12:32:27PM +0800, Deepak Kathayat wrote:
Also, would it be possible to have a chat over #tor-dev sometime, where each of us could discuss in length about how the work could be divided and the amount of time one would be willing to put in for their part?
Sounds like a great idea. Do you feel like creating a Doodle calendar or something similar? :)
Cheers, Philipp _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Hi all,
I have to finish part of the project before May 2. And I am starting to implement Website Probing (section 3.1.3 in the paper). My plan is to implement 3.1.3 and then see how far I can go.
Thanks,
Yiwen
Hey, Sorry for not responding to this sooner. I've actually written some code related to that part of the paper (3.1.3), too. You can get it from http://git.tobiasrang.com/analyser.git/ Tobias
http://whenisgood.net/nhhy5yt If you guys want to set up a meeting time, fill this out. If you want to see the results, go here - http://whenisgood.net/nhhy5yt/results/gqtpzak Best, Utsarga On Wed, Feb 12, 2014 at 3:37 AM, Philipp Winter <phw@nymity.ch> wrote:
On Wed, Feb 12, 2014 at 12:32:27PM +0800, Deepak Kathayat wrote:
Also, would it be possible to have a chat over #tor-dev sometime, where each of us could discuss in length about how the work could be divided and the amount of time one would be willing to put in for their part?
Sounds like a great idea. Do you feel like creating a Doodle calendar or something similar? :)
Cheers, Philipp _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
On Wed, Feb 12, 2014 at 08:53:53PM -0500, Utsarga Sikder wrote:
If you guys want to set up a meeting time, fill this out. If you want to see the results, go here - http://whenisgood.net/nhhy5yt/results/gqtpzak
Looks like Feb. 22nd at 15:00 UTC is fine for us all. Let's meet in #tor-dev on OFTC, then. Cheers, Philipp
participants (7)
-
Abhiram Chintangal -
David Stainton -
Deepak Kathayat -
Philipp Winter -
Tobias Rang -
Utsarga Sikder -
Yiwen Zhu