16:00:24 #startmeeting tor anti-censorship meeting 16:00:24 Meeting started Thu May 22 16:00:24 2025 UTC. The chair is onyinyang. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:24 hello everyone! 16:00:24 here is our meeting pad: [https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469](https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469) 16:00:29 hi~hi~ 16:01:07 hello 16:03:08 I think the point in the agenda is from last week 16:03:25 should we remove it or there is more to talk about this week? 16:03:44 no news from me about that 16:04:16 ok, removed :) 16:04:39 So there are no discussion points :( 16:04:41 I guess we might not have much to discuss this week :) 16:04:46 but there are interesting links! 16:05:27 looks like we'll need to keep an eye to myanmar 16:06:01 I think one particular thing we should look for is that 16:06:16 we already have myanmar in circumvention settings 16:06:19 we usually assume that censor only controls the network in one region 16:07:03 but we typically don't think they could combine data from more than one region and sharing data between them 16:07:06 yes, will be interesting to see if bridges get blocked together in both regions 16:08:05 let's say if a user setup proxy in US and access it from China, then US deploy a censorship device made in that that send its data to assist china in censorship of that proxy 16:08:15 which is not something we usually think about 16:08:43 but maybe in the future we need to say that when this happen, whether the proxy protocol will work less well 16:09:06 since user might wish to deploy proxy in a nearby region to improve network performance 16:09:33 without thinking too much about whether the firewalls will whispering with each other 16:09:44 and yes, they can also share block list 16:09:45 over 16:10:10 yes, something to keep in mind 16:10:33 on the other link, happy families is comming 16:10:58 we've being discorgaing people to run exit nodes and bridges, because you can't add bridges to your family 16:11:15 and clients might choose a path that goes both over your bridge and your exit node 16:11:25 AFAIK happy families solves that 16:11:55 nice! 16:12:03 cool 16:12:07 this was not the main intention of happy families, the interest was to reduce the descriptors size by removing the long list of relay fingerprints of families on each relay 16:12:18 but that use case was also taken into account 16:12:58 that is all from me 16:13:06 eof 16:13:49 alright, I guess if there's nothing else we can end the meeting 16:14:02 sounds good 16:14:15 #endmeeting