16:00:04 <shelikhoo> #startmeeting tor anti-censorship meeting
16:00:04 <shelikhoo> here is our meeting pad: https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469
16:00:04 <shelikhoo> editable link available on request
16:00:04 <MeetBot> Meeting started Thu Jul 31 16:00:04 2025 UTC.  The chair is shelikhoo. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:04 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:00:18 <shelikhoo> hi~hi~
16:00:40 <meskio> hello
16:01:10 <gaba[mds]> hi
16:02:21 <cohosh> hi
16:03:14 <shelikhoo> the first topic is Remove s390x container image build for snowflake-proxy
16:03:20 <shelikhoo> it is from me
16:03:47 <shelikhoo> s390x is a very rare ISA
16:04:10 <shelikhoo> and it is unlikely to be used by a large user base
16:04:21 <shelikhoo> and is not supported by TPA's base image
16:04:59 <shelikhoo> since
16:05:00 <shelikhoo> https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/597
16:05:43 <shelikhoo> we are using TPA's base image as a source of snowflake-proxy's file system template
16:06:06 <shelikhoo> I think we could remove support for s390x without impacting too much users
16:06:21 <meskio> I support that
16:06:58 <shelikhoo> do we know anyone that are using s390x machines?
16:07:12 <shelikhoo> I thing it quite hard to even find such vps
16:07:14 <meskio> I think we have a s390x machine in our CI, I also added support for it in the obfs4-bridge container without thinking
16:07:24 <meskio> but planning to remove it as part of https://gitlab.torproject.org/tpo/anti-censorship/docker-obfs4-bridge/-/issues/25
16:07:41 <shelikhoo> I think we could test the code on s390x
16:07:57 <meskio> shelikhoo: I don't expect anybody to use it, I would remove it and see if someone complains
16:08:25 <shelikhoo> yes
16:08:30 <shelikhoo> let's remove it for now
16:08:34 <meskio> +1
16:08:35 <shelikhoo> the next topic is
16:08:59 <shelikhoo> meek-azure being renamed to meek
16:08:59 <shelikhoo> https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43816
16:08:59 <shelikhoo> https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/272#note_3231570
16:09:20 <morganava> o/
16:09:35 <meskio> go ahead if you want morganava
16:09:39 <shelikhoo> we also received the feedback that the current meek operator is also operating a exit relay
16:09:41 <meskio> or I can describe it
16:09:57 <morganava> tldr meek-azure hasn't been azure for a long time
16:10:14 <morganava> so we need to update our publically visible strings in our various apps
16:11:04 <meskio> we are discussing to also rename it meek also in our internal APIs (circumvention settings)
16:11:17 <meskio> my plan is to support both for a while and provide everything duplicated
16:11:20 <morganava> as well as support the new name in rdsys's apis
16:11:32 <meskio> (ups, sorry for stepping)
16:11:34 <morganava> (sorry also in another meeting lol)
16:11:53 <cohosh> i think there is an old issue for this
16:12:06 <cohosh> ah https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/41359
16:12:41 <cohosh> ok it's being tracked in the new one
16:12:56 <meskio> :)
16:13:07 <shelikhoo> I am happy with renaming
16:13:12 <meskio> I'm poking other users of moat, so they know of the change
16:13:25 <cohosh> same
16:14:36 <meskio> that is all for me
16:14:41 <shelikhoo> okay
16:14:44 <morganava> i left a comment at the bottom of the tor-browser meta issue with a rough task dependency tree
16:15:03 <morganava> around the entire feature, so if there's anything there, other products using meek/rdsys that need to be informed please reply there
16:15:10 <morganava> https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43816#note_3231584
16:15:44 <shelikhoo> we have an announcement this week: telegram distributor hands out webtunnel bridges
16:16:03 <shelikhoo> thanks morganava!!!
16:16:14 <morganava> np o/
16:16:20 <cohosh> thanks!
16:16:34 <meskio> morganava: I'm sending other apps to https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/272
16:16:54 <morganava> great
16:17:09 <meskio> but I see your comment, is also a nice source
16:17:18 <shelikhoo> I hope by distributing webtunnel over telegram i will provide more choice for users...
16:17:26 <shelikhoo> (the topic is not added by me)
16:17:32 <shelikhoo> (just commenting)
16:18:10 <meskio> yes, we'll see
16:19:28 <shelikhoo> I wonder if there will be a way to make updating procedure for circumvention settings easier
16:20:18 <meskio> what do you mean?
16:20:31 <shelikhoo> like make sure the users of the circumvention setting does not assume or expect names of entries
16:20:54 <meskio> ahh, I see, is hard to know what each project uses from that API
16:20:57 <shelikhoo> and process entries in a general purpose way
16:21:06 <meskio> but my dream is to provide a library, so they don't consume the API directly
16:21:10 <meskio> and we control how it is used
16:21:48 <shelikhoo> for example, V2Ray's subscription system does not require the client to actually understand the subscription document's content
16:22:01 <shelikhoo> just input the url, and the core will handle the rest
16:22:21 <shelikhoo> the client just need to list server names, and select them
16:22:26 <shelikhoo> via grpc api
16:23:16 <shelikhoo> as a result the update of subscription's server name, even format is abstracted away from client
16:23:20 <shelikhoo> over
16:24:34 <shelikhoo> anyway, the announcement was
16:24:34 <shelikhoo> telegram distributor hands out webtunnel bridges
16:24:51 <shelikhoo> anything we would like to discuss about this announcement?
16:25:05 <meskio> not from me
16:25:09 <meskio> I just wanted to mention it
16:25:45 <shelikhoo> okay... anything more we would like to discuss in this meeting?
16:26:50 <meskio> EOF
16:27:33 <shelikhoo> okay if there is anything to discuss send something now...
16:27:45 <shelikhoo> thanks!!!!!!!
16:27:45 <shelikhoo> #endmeeting