ooni-dev

ooni-dev@lists.torproject.org

306 discussions

Re: [ooni-dev] Campus Network Cencorship & OONI
by Arturo Filastò 17 Feb '14

17 Feb '14

Moving the thread to ooni-dev so that we can continue the discussion there. On 2/17/14, 2:43 AM, Abel Corver wrote: > Hi Art, > > Thanks! > > Yeah, let's move this to the ooni-dev mailing list! (I've subscribed to > both lists) > > Shall we discuss the what exact ticket to open there, or do you want to > file one now? Opening a ticket on this would be great! ~ Art. > > On Sun, Feb 16, 2014 at 4:06 PM, Arturo Filastò <arturo(a)filasto.net > <mailto:arturo@filasto.net>> wrote: > > On 2/16/14, 12:13 AM, Abel Corver wrote: > > Hi, > > > > I'm a student in the US interested in finding out if my university is > > censoring certain pages. > > > > (1) Are there any UI tools to visualize OONI reports? > > There is currently one graphical tool for aiding in visualizing > ooniprobe reports called ooniprobix: > https://github.com/AccessNow/ooniprobix. > > This can be useful for parsing and analyzing the reports, but not > visualizing the report data. > > > (2) Do you know of existing initiatives to monitor censorship _within_ > > networks, as opposed to by country? If so, are any of them > specifically > > targeting possible campus surveillance? > > > > That is also what we are interested in measuring. That is why for > example we include by default the AS number of the network that is being > tested in the report. This allows us to know not only in which country > censorship is happening, but also which ISP is performing censorship. > > The problem, however, is that there is currently no way to say that the > censorship you are witnessing is caused by the ISP, but a local network > policy (a campus performing censorship or an office). > > I think this is a worthwhile thing to have and I think we should open a > ticket on our issue tracker to discuss how we could tackle implementing > it: https://github.com/TheTorProject/ooni-probe/issues. > > > Let me know if there're better places to ask this question. I wasn't > > able to find an OONI mailing list. > > We do have a mailing list! > > You should subscribe to ooni-dev and ooni-talk: > https://lists.torproject.org/pipermail/ooni-dev, > https://lists.torproject.org/pipermail/ooni-talk/ > > Do you mind if we move this discussion to the ooni-dev mailing list? > > ~ Art. > >

1 0

Blockpage Detection
by Ben Jones 27 Nov '13

27 Nov '13

Hello, I am a PhD student at Georgia Tech and I am collaborating with researchers at Stony Brook University to find an effective means of detecting block pages. We have access to a very robust set of both real pages and blocked pages (~2.4 million pages) which we are using to evaluate block page detection metrics. We already have two measures to detect block pages and would like to evaluate your DOM similarity measure alongside our own metrics. Since we are planning on publishing our results, may we include your DOM similarity measure in our evaluation? Also, I would like to look more into this similarity measure, is there a paper that I can read? Thanks, Ben Jones

3 2

Future weekly meeting schedule
by Tom Lowenthal 18 Nov '13

18 Nov '13

Howdy, y'all! In a great departure from my tradition of using Doodle for everything, I'm going to try to find the best time for future Ooni weekly meetings by simply **asking** y'all when you can make it. Crazy, eh? Here's the conundrum for you: what recurring timeslots do you have available on the regular? If you could either answer in Pacific time, or tell me your time offset from Pacific, that'd be lovely. It'd probably be easier on everyone's inboxes if you replied off-list (but on thread). I'll announce the best time at Monday's meeting, which will be at 0900h Pacific. Any other questions? -Tom

2 1

Summary of OONI weekly meeting 2013-11-05 9:00 AM PST, 18:00 CET
by Arturo Filastò 05 Nov '13

05 Nov '13

This weeks call was very dense of content as it was a while that we had not done one with all the team present. Here goes an attempt to summarize briefly what was discussed. We did a summary of the work so far done on the OONI side and the possibility of a collaboration between least authority. They will be assisting us starting in February to do release engineering. They will start doing their audit of the OONI codebase starting in December. This means that the OONI team will continue working on testing, bugfixing until mid December and continue tagging new releases as we go onward. We will also in light of the schedule changes review the current milestones and adjust them in favor of the work that will be done by least authority. The next call will happen on Monday 2013-11-12 at 9:00 A.M. PST 18:00 CET. I invite all the participants to integrate what I may have missed out in this summary. Thank you all for being present in the call, ~ Art.

1 0

OONI Weekly meeting Monday 2013-11-04 h 18:00 CET
by Arturo Filastò 02 Nov '13

02 Nov '13

Since it's been some time that we have not had the weekly meeting for the OONI project it is time to fill in that void and meet up next week. We are going to be discussing the possibility of a collaboration between us and the least authority team to assist us in release engineering. The proposed agenda is as follows: 17:55 - Meet on IRC (#ooni) to get the link or wait for the follow up email to this thread 18:00 - Meet and greetz 18:05 - Discuss what is the current status of the project, what has been done. 18:20 - Discuss what we need to do for the current milestone, what tasks are still pending 18:35 - Discuss with the least authority team this collaboration. 19:00 - Wrap it all up and say bye until next week (: ~ Art.

1 0

OONI weekly meeting call 18:00 CET
by Arturo Filastò 01 Nov '13

01 Nov '13

For starters I excuse myself for the absence in the last couple weeks, but I was not feeling very well. I am now back in Italy where at least the sun shines. Can we organize to meetup in a call to discuss the current project status and identify the next steps? I created a doodle to facilitate agreeing on a date and medium (I set it to 18:00 CET since that seemed to be working well in the past). Could you please cast your vote on this doodle here if you are going to be present in the call: https://doodle.com/uprtfyf7ncaeuptrfbacr3r5 I think it is crucial that in this call are present: * Aaron * Somebody from m-lab google * Somebody from least authority I would say since it has been a bit of time that we have not synched back up that we get don't have a strict agenda, but try and figure it out along the way. ~ Art.

3 3

OONI weekly meeting call 18:00 CET
by Arturo Filastò 28 Oct '13

28 Oct '13

For starters I excuse myself for the absence in the last couple weeks, but I was not feeling very well. I am now back in Italy where at least the sun shines. Can we organize to meetup in a call to discuss the current project status and identify the next steps? I created a doodle to facilitate agreeing on a date and time (I set it to 18:00 CET since that seemed to be working well in the past). Could you please cast your vote on this doodle here if you are going to be present in the call: https://doodle.com/uprtfyf7ncaeuptrfbacr3r5 I think it is crucial that in this call are present: * Aaron * Somebody from m-lab google * Somebody from least authority I would say since it has been a bit of time that we have not synched back up that we get don't have a strict agenda, but try and figure it out along the way. ~ Art.

1 0

Audit Status
by Nathan Wilcox 07 Oct '13

07 Oct '13

Hi all, I apologize for missing this week's meeting. Our audit schedule has slipped. We'll be at the weekly meeting on Monday the 14th to go over our findings, and if there are unfinished contract hours, we can discuss scheduling those at that time. -- Nathan Wilcox Least Authoritarian

1 0

Meeting notes for OONI weekly call 19 August 2013
by Arturo Filastò 02 Oct '13

02 Oct '13

Hi all, As promised here are the notes for the last OONI weekly call of August 19th 2013 18:00 CET. People present * Meredith * Nathan * Tom * Arturo * Stephen This is what was discussed: # Drop /nettest part of API Stephen raised some good points on the /nettest API. We agreed that since keeping track of versioning is something a bit complicated we should not implement this feature at this time. We should always update net tests and the probe software at the same time, therefore having a feature that could possibly lead to this un-alignement is not ideal. ## Next steps We will remove from the oonib.md specification the /nettest API and remove support for it inside of oonib. # Doing the security audit with test infrastructure Nathan said that it would be useful to have oonib deployed in an environment that resembles production is useful to them. We will not manage to have ooni deployed on the m-lab production nodes, but we can easily deploy it on the m-lab test nodes. Stephen says that as long as the package building process keeps on working, this will be easy for him to do. Making sure this stays true we have created this ticket: https://github.com/TheTorProject/ooni-probe/issues/161 ## Next steps OONI team will finish development on oonib, tag a release and test it with the deployment scripts. # Issue of backend collector mapping server side reports I explained the rationale behind having the test helpers keyed to a collector. As long as we make it that you report to the collector run by the test helper you used we will be able, in future versions, to collect also reports from the backend side. # Slight delay on this weeks milestone We are a bit behind on the next milestone, but we have however a bit of buffer with the one before the least authority audit starts. We will finish it by this week, but we will not change the date on the github milestone. It is just expected to be closed on the 25th. # Merging of wiki with ooni-spec We agreed that the wiki is going to go into the ooni-spec repository (https://github.com/TheTorProject/ooni-probe/issues/159?source=c) ## Next steps Merge the wiki into the ooni-spec repository and add a link in the wiki front page pointing to it's new location. -- If you think I missed something feel free to append your comments to this email. ~ Art.

3 2

OONI weekly meeting
by Aaron 23 Sep '13

23 Sep '13

Hi All, Arturo is out sick, and I haven't heard an agenda from Tom. I'm hanging out in the #ooni channel. --Aaron

1 0

← Newer
1
...
24
25
26
27
28
29
30
31
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

ooni-dev