17:59:42 #startmeeting anti-censorship team meeting 17:59:42 Meeting started Thu Nov 21 17:59:42 2019 UTC. The chair is phw. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:45 hi everyone! 17:59:52 hey 17:59:57 here's our meeting pad: https://pad.riseup.net/p/tor-censorship-2019-keep 18:00:40 i deleted last week's nextcloud announcement 18:01:01 shall we jump right in to the first discussion item? it's gettor's survival guide 18:01:12 but now i wonder if this was also from last week 18:02:28 the question about what's the canonical gettor repository is a good one, though. did you find out, cohosh? 18:04:31 cohosh: ^ 18:05:59 * phw takes a look at the censoredplanet/russia link in the meanwhile 18:06:23 There's a paper attached, but I haven't read the paper yet, only the web summary. 18:06:58 oh, i didn't realise that the paper was out already 18:07:57 hi! o/ 18:08:08 hi gaba! 18:08:13 https://censoredplanet.org/assets/russia.pdf 18:09:17 One of the main observations is that censorship is less centrally managed in Russia than in China, but nevertheless effective. 18:09:44 Another is that Russia has the unique(?) characteristic of publishing its list of sites that ISPs are obligated to block. 18:09:57 oh, that's interesting 18:11:37 on a somewhat related note: i was upset to learn that elsevier somehow got two austrian isps to block domain names for sci-hub 18:11:46 ( https://www.derstandard.at/story/2000111305516/netzsperre-a1-und-t-mobile-blockieren-pirate-bay-der-wissenschaft -- in german, though ) 18:11:59 Good old Wissenschaft 18:12:26 putting the 'schaf' in 'wissenschaft' 18:12:47 (the two isps, that is) 18:14:41 hey sorry! 18:14:46 i lost track of time >.< 18:15:19 yeah i have some questions for hiro about gettor 18:15:24 but if they are not here now i can ask later 18:16:16 ok, let's discuss #29207? 18:16:27 and the drop in proxies 18:16:31 I am here 18:17:09 hi hiro! 18:17:21 about the snowflake proxies, it's possible that most were cupcake proxies 18:18:38 cohosh: yeah, that's the only explanation I can think of. WebExtension proxies should have been updated through the browser, and hosted proxies (if there are any) would have restarted themselves within a day. 18:18:58 I'm wondering if there's something we did not account for, though, because 90% Cupcake proxies seems high to me. 18:19:11 dcf1: are you getting this data from collector? 18:19:14 or from the debug page? 18:19:18 debug page 18:19:26 because the browser proxies are also polling only every 300s 18:19:33 so in reality we must have much more than that 18:19:43 Oh hmm, tat coudl really explain it. 18:19:55 there may be some conflation between #29207 and the update that extended the poll period 18:20:08 i just looked though and collector seems to not have the last few days of snowflake data 18:20:11 perhaps there is a bug there 18:20:12 wouldn't we expect most of our proxies to be firefox? after the surge of roger's defcon talk? 18:20:17 Okay, I'll look at the broker code to check, but I think this is resolved. 18:20:35 Firefox has 2,127 users and Chrome 1,921 according to 18:20:41 https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/ 18:20:43 https://chrome.google.com/webstore/detail/snowflake/mafpmfcccpbjnhfhjnllmmalhifmlcie 18:20:51 wow nice 18:20:58 oh, that's very helpful 18:21:41 Cupcake is 2,102 https://chrome.google.com/webstore/detail/cupcake/dajjbehmbnbppjkcnpdkaniapgdppdnc 18:21:45 i assume "users" means "currently using" and not "installed at some point, and possible uninstalled since" 18:22:09 i actually expected the cupcake proxies to stop polling though due to the deadlock bug we patched in the summer 18:22:25 I assume so too, otherwise what's the point of all the telemetry Mozilla and Google cram into their browsers. 18:22:28 so i would expect, looking at collector, for the numbers not to have changed much after #29207 18:22:53 Right, I report that number because that's what made me think that 90% Cupcake was implausible. But I think your polling interval change explanation is right. 18:24:35 hiro: hey! i noticed that the main gettor repo at https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor is behind your personal clone 18:24:50 yes I haven't merged 18:25:05 that's why I need to act on your reviews 18:25:14 i think it's farther behind than that 18:25:21 uhm... 18:25:24 the deployed version is from october 18:25:31 and the main repo has the last commit in september 18:25:36 i'm lost here: how does the polling interval affect the proxy count on the debug page? 18:25:52 phw: the debug page shows the currently polling proxies 18:25:57 I do not deploy my personal project 18:26:02 oh okay 18:26:06 maybe i'm mistaken 18:26:14 cohosh: ah, gotcha 18:26:17 I deploy the stuff that is on git.tp.o 18:26:26 or gitweb for the web interface 18:26:33 oh then maybe dip is behind git.tp.o 18:26:44 it should be updated... but I can check that 18:27:03 I mean automagically updated with the git hooks 18:29:00 hiro: oh nice, yeah i'm seeing the last commit to be august instead of oct 18 for the git.tp.o repo 18:29:24 I have done a deploy in october 18:29:29 let me see 18:29:29 i wanted to check before making a merge request to dip 18:29:56 yeah 18-10 on gitweb 18:29:59 oops i should have phrased that better: the last commit on dip is august but git.tp.o is oct 18:30:08 ah I see 18:30:23 maybe something is not being synced I will check 18:30:28 ok thanks! 18:32:21 I think it is because things moved within dip... now that I think about it 18:32:39 gitlab should give a warning and redirect but maybe that broke the git hook 18:32:57 oh okay 18:33:37 that's all i had for discussion, sorry for jumping in late and then derailing 18:34:12 okay, let's do reviews 18:35:11 we have #32480, #31157, #30579 and an authentication token for cohosh 18:35:35 I'm swamped this week and cannot afford to do much review. 18:36:07 i think i can take all of these 18:36:17 except the authentication token :) 18:36:24 phw: thanks! 18:37:07 anything else left to talk about? if not, i'll end the meeting in a minute 18:38:16 #endmeeting