[ooni-dev] One of these people should be invited to the OONI meeting

[Virgil Griffith]

Correction: strict *subset*
On Sat, 12 Sep 2015 at 19:59 Virgil Griffith <i at virgil.gr> wrote:

> oh this is interesting, and news to me. i suspect there is much here i
> need to learn.
>
> however, if we reframe OONI's mission as "we're interested in certain
> kinds of network outages", then OONI's goals become a strict superset of
> Atlas's goals.
>
> it seems we could at least get them on board for putting Atlas
> probes/anchors next to major Tor relays. then if anything goes amiss not
> only do we register it as a "censorship event", RIPE registers it as a
> "network/connectivity degradation". And that latter point can only help
> OONI.
>
>
> -V
>
> On Sat, Sep 12, 2015 at 19:20 <balooni at espiv.net> wrote:
>
>> Hi,
>>
>> i at virgil.gr wrote:
>>
>> > http://atlas.ripe.net/
>> >
>> > The idea of putting their probes (or even anchors) next to Tor relays
>> > and/or OONI probes seems an immensely good idea because doing this
>> > will yoke the interests of generic network infrastructure people with
>> > those of Tor and OONI.
>> >
>> > I'd be happy to bring them to the Tor meeting in Berlin, but they
>> > seem a better fit for the OONI meeting in Italy.  So I'm inclined to
>> > have you invite them.  Their community contacts are:
>> > becha at ripe.net
>> > mcb at ripe.net
>>
>> IIRC Ripe atlas would not like to be associated with
>> neither Tor nor OONI. At some point they have explicitly mentioned
>> that they would not like to be involved in any "conflict of interests"
>> by their parent organization Ripe.
>>
>> I will be more than happy to find out that this is not the case anymore?
>> _______________________________________________
>> ooni-dev mailing list
>> ooni-dev at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/ooni-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/ooni-dev/attachments/20150912/64d01389/attachment.html>