16:00:21 #startmeeting tor anti-censorship meeting 16:00:21 Meeting started Thu Nov 20 16:00:21 2025 UTC. The chair is meskio. Information about MeetBot at https://wiki.debian.org/MeetBot. 16:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:26 hello everybody!! 16:00:48 here is our meeting pad: https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469 16:00:50 ask me in private to give you the link of the pad to be able to edit it if you don't have it 16:00:52 I'll wait few minutes for everybody to add you've been working on and put items on the agenda 16:01:12 hi~hi~ 16:01:23 hihi! 16:01:37 hi 16:02:22 looks like we have all the updates in the pad, I guess we can start 16:02:31 the only topic in the agenda (for now) is from me 16:02:43 I have implemented multi-domain front support for meek 16:03:00 so it can be configured to use multiple provider-domain pairs 16:03:34 in the review cohosh pointed out that my designed bridgeline arguments were not great 16:03:38 and I agree 16:04:14 but we are not sure what will be the best way to pass multiple url-domain pairs on the bridgeline 16:04:28 we have basically two proposals in here: 16:04:35 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/merge_requests/142#note_3289114 16:04:58 one is to do a targets= 16:05:16 with the danger of json usually having spaces and bridgelines interpreting spaces as separators 16:05:52 and another is to add support in goptlib to pass an argument multiple times and pass something like 'target=domain,url' 16:06:05 does it make sense what I am saying? 16:06:12 any better ideas or preferences? 16:06:53 we can also give you some time to think about it and respond in the MR next week, I don't think there is any rush to merge this 16:07:10 BTW, I poked the applications team about it also 16:07:18 Let me have some think and post it to MR.... 16:07:35 I don't know if I could come with any nice idea live... 16:07:48 sure, no prob 16:08:07 having had time to think about it, i like the idea of having two separators (e.g., ',' and '|') and making then doing "target=front,url|front,url|..." 16:08:23 ok, then we have 3 options 16:08:24 it's not as efficient as json but it's simple and groups pairs together 16:08:41 where space could be a separator option between pairs 16:09:09 that option doesn't sound too bad 16:09:19 although as you pointed out, we might not want to use "," if we want to support full URIs 16:09:33 is fine if we use it to separate the front 16:09:37 as domains don't have , 16:09:48 but urls need another character as separator 16:10:00 ah yeah true, if fronts are always first in that pair 16:10:02 so the proposal you have were urls are actually separated by | should be fine 16:11:36 ok, that's my recommendationf or now but let's give others time to come up with more options 16:12:05 sounds good to me, lets wait for the opinions of others 16:12:22 I think we are done with this topic 16:12:30 any other topic to discuss? 16:13:00 Just noting that we don't have a reading group coming up. Should we pick something? 16:13:15 sure, any proposals? 16:13:37 ummmmmmm, not in particular XD 16:14:05 I could look into it but need another week hehe 16:14:07 I don't have any suggests either.... 16:14:14 so maybe we could have a todo for next week 16:14:30 yes...maybe we can choose the reading group next week... 16:14:39 sounds good, let's look for interesting papers, I recall having some that I wanted to read but forgot which 16:14:42 yes, and come with some proposals :) 16:15:22 ok, so we discuss it next week 16:15:30 anything more for today's meeting? 16:15:49 nothing more from me 16:16:31 then, I'll end the meeting here 16:16:34 #endmeeting