-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[Moving this thread back to the list.]
On 16/08/15 12:50, l.m wrote:
> So how does one actually fix it. All I've read here is that there
> may be a new version, and thanks for anyone who makes an effort.
> Who makes an effort? How to make an effort. It should be obvious
> why the list should stay. It makes censorship visible which then
> makes analysis easier.
>
> If you're not going to provide method that people can contribute to
> a fix you might as well get rid of it then.
I could imagine two scenarios here:
- Somebody writes a better censorship detector on their own which
produces fewer false positives than the one we currently have [0], and
at some point we start running that on a Tor host and possibly have it
send notifications to this list.
- The Tor Measurement Team sketches out requirements and possibly a
design for a future censorship detector and finds somebody to work on
it with the goal to run it on a Tor host and possibly send
notifications to this list. The planning part here may take another
four to six weeks [1], and it's yet uncertain whether this project
will be higher priority than all the other things that need doing.
Karsten
[0] https://research.torproject.org/techreports/detector-2011-09-09.pdf
[1]
https://people.torproject.org/~karsten/volatile/measurement-roadmap.pdf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJV0G+IAAoJEJD5dJfVqbCr6GEH/2hqv0LUsiM8YicQHWHrEVuQ
qb/pKl+tHexW0CcqdzPfXG8AmZsnFKof9ADewoNUX04kSXeizt6PyuvgSOP8/KhS
YwIw2oHg3AFB5sfi+xLFuWB8WSmEr38K8ctJx8Vmjt2s+pDjiuLRkvxFU5Iemaa6
4Qezgk43zxK8r5O+Z2lvxguOkQfalqot0eN695glQ5iNDmynrsOAGiwJrv+QcCtB
V3GWeflbYe19pp3XDDxIweIksaz4AW4E/C7E/IMdM3MPrL2R5gfsekwqLqkmzJ5e
jbUok4mmUqho3XgAztgXpdtaJoHsrC8EizKTum8hCLldCe8GrhAbf7MeKvsUFwg=
=bUUH
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear person who is interested in Tor censorship events,
how sad would you be if we shut down the tor-censorship-events@
mailing list?
I'm asking, because I'm about to move the Metrics website to a new
host, and I'd want to leave behind any unused parts while doing so.
This list very much looks like the perfect candidate for not being moved.
Here's why:
- All mails sent to this list in August covered July 30, and yet
nobody noticed.
- A couple months back I changed how userstats are updated from daily
to every three days, but I didn't adapt the script sending out these
mails, which still only covers a single day, and yet nobody noticed.
- The links contained in these emails have been broken since November
2014, and yet nobody noticed.
Note that I understand the desire to be informed about automatically
detected censorship of the Tor network. But this script and mailing
list is not what we want, it just leaves us under the impression that
we have a somewhat working solution. We don't. And maybe that even
prevents people from building something better.
Here's my plan:
- If I hear a convincing reason why we should keep this mailing list
in the next 72 hours (that would be Wednesday, August 12, 12:00 UTC),
I'll move it to the new host and will even try to fix the bugs above.
- If I don't hear such a reason, I'll kill the list with fire.
Thoughts? (Just respond to this list, and I'll manually approve your
posting, despite this list not being a discussion list.)
All the best,
Karsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJVx0DBAAoJEJD5dJfVqbCr43UH/jcytvnuNY4x6+iFSV7ggq3x
3SBB9dqY/ftkPOVrQ+oOsuweM5UVOfr2Brne0o2cjVSz0blsIYGk/iW60/J7jdWJ
P1qZlh1qhpmZ+CjccTPT1hJJJhfo5HfWbcvHvYev4YV65/pzkdxAN9FxDJmkegFS
+fnvUWY/hqxOCHBMFoAeOKtFRp0EX1LLpumi0HDP3PizhadmchTf18EgXC29SF1a
v0XJhyChLNz8Q5MmtzyKovR8uZ3xwv5RMbmg6CZaU84z7Jh9moO8cDDgL0fRUheS
3KXQ9e1S7Lv93XM0nFj3jOEXFSrXiHyhPWNkDMtPofqXOI6C+Q3ih5o7QY5ApGs=
=f2AD
-----END PGP SIGNATURE-----