15:59:00 #startmeeting tor anti-censorship meeting 15:59:00 here is our meeting pad: https://pad.riseup.net/p/tor-anti-censorship-keep 15:59:00 feel free to add what you've been working on and put items on the agenda 15:59:00 Meeting started Thu Jul 7 15:59:00 2022 UTC. The chair is shelikhoo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:00 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:08 hi~ 15:59:31 hello o/ 16:01:36 I kept the first point in the agenda, but not sure if we need to talk about it 16:01:39 hello 16:01:54 re about snowflake russia blockade 16:02:43 If I recall correctly, we are yet to have a tor browser with supported group patch applied 16:03:31 yes, is someone working on that? 16:05:03 I guess the silence means no 16:05:19 we should ask cohosh? 16:05:34 I'm not expecting cohosh to be working on it 16:05:41 but maybe I'm wrong 16:06:08 yes... 16:06:24 so I guess the question is, do we really need the tor browser with the group patch and we need to find the time to do that? or can we have another approach to the problem? 16:07:03 we can build a version of snowflake-client, replace the binary, and then distribute it 16:07:14 instead of the full browser build 16:07:23 that makes sense 16:08:06 unless we need something like mobile version 16:08:33 do I understand correctly that the plan is to produce something to hand out for people to test and confirm it works fine? 16:09:12 I think it is the plan 16:09:17 great 16:09:55 shelikhoo: can you produce that binary and produce the tor browser tgz with it? 16:10:14 yes, I will do that! 16:10:18 great 16:10:40 once is ready we can talk with ggus to see how to ask people to run it 16:11:18 yes, anything more on this topic? 16:11:33 not from me 16:11:35 the next topic is 16:11:35 BridgeDB provides offline bridges(example,https://metrics.torproject.org/rs.html#details/A0B6EBF970BBA8411AB032A36C026B387A4BF7CF) 16:12:21 I don't know anything about it, but in my queue of things to investigate there are other quirks on rdsys/bridgedb distributing bridges that should not be distributed: 16:12:24 https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/80 16:12:41 I'll add that comment to this issue and investigate it 16:12:49 does someone has more info about it? 16:12:50 Yes, I don't think meskio is the one that added this topic 16:12:58 (that point was already in the pad few days ago) 16:13:13 yes... maybe yet another unattended topic 16:13:18 yep :) 16:13:40 let's just move it to that ticket and discuss there 16:13:49 +1 16:14:19 we should have a rule that each topic should identify source 16:14:46 so that we know who provide more context during the discussion 16:15:06 (just an opinion) 16:15:09 yes, or at least not expend much time if the person that added it is not around 16:15:21 anything more on this topic? 16:15:22 wolpertinger retirement 16:15:22 https://gitlab.torproject.org/tpo/anti-censorship/wolpertinger 16:15:22 https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/85#note_2819202 16:15:33 yes, this one is mine 16:15:45 I'm looking at retiring wolpertinger 16:16:13 wolpertinger is a service designed to distribute bridges to projects like ooni 16:16:38 but we haven't found a good way to provide bridges to ooni and don't leak them to censors 16:16:50 AFAIK is not in use, but it is deployed in polyanthum 16:17:14 I think we can retire the service and archive the project, and if we revisit the idea in the future we can bring it back 16:17:32 yes... I have no objection to this 16:17:43 so if someone knows of it being used anywhere or have an opinion against the retirement I'm all ears 16:18:47 anyway, I'll wait a couple of weeks just in case before shutting it down 16:19:30 yes, I think this is the last topic in the discussion.... 16:19:41 anything more we need to discuss in this meeting? 16:20:27 not from me 16:20:43 +1 16:21:15 okay, let's call it a meeting.... ^~^ 16:21:16 #endmeeting