17:59:07 #startmeeting anti-censorship checkin 2020-02-27 17:59:07 Meeting started Thu Feb 27 17:59:07 2020 UTC. The chair is cohosh. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:59:13 hi! 17:59:17 hi 17:59:33 it's likely a small and short meeting today since we don't have much on the agenda 17:59:42 our meeting pad is here: https://pad.riseup.net/p/tor-anti-censorship-keep 18:00:02 hi! 18:00:17 anyone have any discussion topics or announcements? 18:00:22 yes! :) 18:00:27 shall I add it to the pad 18:00:29 hi pili! 18:00:34 (I have to be on another meeting now also though) 18:00:42 hopefully I can split myself 18:01:01 heh 18:01:25 or I can get ggus to bring the topic on our behalf 18:01:26 I'll put it onthe pad anyway 18:01:45 okay you or ggus can have the mic now 18:03:25 right 18:03:36 so we want to run a session during IFF related to the S30 work and bridges to get people to try to circumvent censorship 18:03:48 for that we would need to provide a censored network 18:04:03 and we were wondering if you had some advice on how we can do that 18:04:09 ah nice 18:04:23 so this is to see how usable our current tools are? 18:04:36 I have some notes from the UX sprint in 2015 where we simulated censorship. We used a local host firewall to do it. I will find some links. 18:04:37 yes, and to see how people deal with it 18:05:01 dcf1: yeah i think we discussed this briefly at the last tor meeting 18:05:14 pili: when is IFF? 18:05:25 and how they find information about circumvention in censored contexts 18:05:34 April 20-24 18:06:22 cool 18:07:03 maybe some kind of setup around librarybox is something you can use. Maybe we can wait for phw to be back to have this discussion 18:07:26 ok 18:07:54 but the links and documentation from dcf1 will be very helpful :) 18:08:26 i think this is the paper that came out of that work: https://petsymposium.org/2017/papers/issue3/paper2-2017-3-source.pdf 18:08:55 source code and documentation for that is at https://github.com/lindanlee/PETS2017-paper 18:09:08 let me collect a few more links 18:09:16 thanks dcf1! 18:10:24 thank you dcf1 and cohosh! I'll take a look 18:11:32 I am dropping the notes in the meeting pad 18:11:42 sounds good 18:11:48 any other discussion items for today? 18:12:06 if not, we can more onto our needs help with 18:12:45 cjb: it looks like you have a question on #31011? 18:13:26 hi! not an urgent question, but maybe someone can take a look at whether to split this ticket up, later is fine 18:14:13 okay, i'd suggest asking on the ticket 18:14:19 yup already did 18:14:27 alright nice 18:14:45 i'm not super familiar with bridgedb so you might want to wait until phw is back 18:15:38 looks like my question on #33211 was answered 18:15:38 sounds fine. it's actually the tor/bridgeauth side of the change that's difficult. bridgedb was parsing extrainfo docs already but tor wasn't, so getting tor (when being a bridgeauth) to poke at extrainfo transport lines is more work than I expected. 18:15:55 yes I'll close #33211 probably in the next hour 18:16:24 cjb: okay, you might want to join the network team meeting if you don't get a response on the ticket then 18:17:08 dcf1: cool, do you want to handle the deployment? if not i can do that after the meeting 18:17:32 it's already deployed that's what I mean 18:17:47 I was doing it when the meeting started 18:18:26 oh okay, great! 18:18:38 hi agix! 18:19:02 Hi, sorry for being late 18:19:08 no worries :) 18:19:15 we're just going over our needs help with 18:19:30 do you have any questions or reviews you need? 18:20:16 i have submitted my patch but i dont know if it has been reviewed yet 18:20:20 it was only a small one 18:20:49 agix: how did you submit it? 18:21:31 i falsely opened a new ticket, phw told me to just comment the patch on the open ticket of the issue 18:21:46 do you know the ticket number? 18:22:00 yes #31967 18:23:33 okay great, i'll take a look but might decide to defer this for when phw gets back 18:23:49 sure thing 18:23:53 agix: you need to change the ticket status to needs_review 18:24:19 i tried to but it seems like i dont have the rights to do so 18:24:32 If you put {{{ }}} around the patch, it will format better in the ticket 18:24:39 agix: you can also submit patches by uploading the patch file as an attachment, this presents it in a slightly more readable way 18:24:43 oh I didn't know that it required special permission, sorry 18:24:51 i just changed the status 18:25:00 dfc1: thanks for the tip :D 18:25:29 cohosh: ok i will do that in the future 18:25:46 thanks for working on this agix 18:25:59 pili, ggus: I posted all my links at https://pad.riseup.net/p/tor-anti-censorship-keep . Watch some of the videos, they are fun. 18:26:03 yup, thanks! 18:26:08 dfc1: thanks for being a part of this :) 18:26:27 okay anything else? 18:26:37 cohosh: could you also help me to close the ticket i mistakenly opened? it seems like i don't have rights to close as well 18:27:02 ah yes 18:27:09 do you remember the ticket number for that one? 18:27:14 yes its its #33388 18:27:35 (hmm this is disempowering if contributors can't close their own tickets) 18:28:00 yeah we should get you updated permissions 18:28:13 i will ask in #tor-dev who has the power to do that 18:28:16 that would be nice :) 18:28:28 I had to ask for super-Trac permissions for all the links I add to wiki/doc/MetricsTimeline and now I don't see rough edges like that 18:29:49 #24120 18:30:24 lol, i've run into that with patches before 18:30:46 hopefully contribution gets easier in the switch to gitlab 18:31:25 for now, i've asked in #tor-dev to give agix more permissions for trac 18:31:39 thanks for that 18:32:19 any last topics for discussion? 18:33:57 okay i'll end the meeting for today 18:34:01 #endmeeting