16:01:11 <shelikhoo> #startmeeting tor anti-censorship meeting
16:01:11 <MeetBot> Meeting started Thu Jul 10 16:01:11 2025 UTC.  The chair is shelikhoo. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:11 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:01:14 <shelikhoo> here is our meeting pad: https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469
16:01:16 <shelikhoo> editable link available on request
16:01:20 <MeetBot> shelikhoo: Error: Can't start another meeting, one is in progress.
16:01:22 <shelikhoo> here is our meeting pad: https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469
16:01:24 <shelikhoo> editable link available on request
16:01:29 <shelikhoo> h~
16:01:48 <onyinyang> hello!
16:02:19 <shelikhoo> hi~hi~
16:02:49 <cohosh> hi
16:04:43 <shelikhoo> If you see your discussion point missing or wish to add a discussion point, please do so now
16:05:47 <shelikhoo> okay, let's start with a interesting link from me
16:05:53 <shelikhoo> https://github.com/net4people/bbs/issues/496 TLSMirror: Looks like TLS Censorship Resistant Transport Protocol is Looking for Developer Feedback
16:06:35 <shelikhoo> over the last tor wide vacation, I push a new transport protocol pass the minimal viable product line
16:06:43 <shelikhoo> and it is TLSMirror
16:07:21 <cohosh> awesome!
16:07:25 <onyinyang> nice work!
16:07:26 <shelikhoo> Developers are encouraged to provide feedback, before this protocol is announced and promoted to end users
16:07:29 <shelikhoo> hehe!
16:07:34 <cohosh> i'm looking forward to reading about it
16:08:12 <shelikhoo> hahaha! but if there is any question about this protocol I am happy to answer them
16:08:37 <shelikhoo> (That net4people bbs link is 14 pages long...)
16:09:17 <shelikhoo> but anyway, that's the head up(ad) from me
16:09:33 <shelikhoo> I didn't see any new discussion points
16:09:52 <shelikhoo> if there is anything you would like to discuss in this meeting please send something now
16:10:54 <dcf1> FYI, there are significant snowflake connections with "??" country in June 2025, on snowflake-01 only
16:11:00 <dcf1> https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40465#note_3220753
16:11:08 <dcf1> Don't know what to do but keep an eye on it.
16:11:53 <shelikhoo> yes. maybe we should update the IP database?
16:12:05 <dcf1> I don't think that's the cause.
16:12:33 <shelikhoo> so... the cause is some proxy is not forwarding the client's ip address?
16:12:35 <dcf1> More likely it's proxies that don't forward the IP address information, perhaps rogue proxies or outdated proxies.
16:12:55 <dcf1> Perhaps some kind of attempted attack, who knows
16:13:48 <shelikhoo> yes... I do have a feeling it might be some kind of custom proxy, since it is only connecting to snowflake-01
16:14:07 <cohosh> Or someone connecting directly the bridge without a proxy?
16:14:34 <shelikhoo> this might means its code is forked before the distributed snowflake proxy get merged
16:17:58 <shelikhoo> BTW: I was wondering if there is FOCI only online attendance for FOCI
16:18:36 <shelikhoo> I didn't see such option online
16:18:40 <dcf1> Yeah there is FOCI only https://petsymposium.org/2025/registration.php
16:18:55 <dcf1> Oh, FOCI online only, maybe not
16:19:20 <dcf1> But the $175 also grants online access, I believe
16:20:23 <cohosh> i just messaged the chairs about it, i can follow up with a forum post or email if i hear back
16:21:11 <shelikhoo> yes! thanks!
16:21:47 <shelikhoo> okay, anything else we would like to discuss in this meeting?
16:22:23 <onyinyang> nothing from me
16:22:49 <onyinyang> i ended up just doing full virtual registration btw shelikhoo
16:22:55 <onyinyang> but I had the same question
16:23:16 <shelikhoo> onyinyang: yeah, I mean in my case I do have physical time zone difference...
16:23:35 <onyinyang> that makes sense
16:24:01 <shelikhoo> so I have no intention to attend the full PETS remotely
16:24:04 <shelikhoo> anyway
16:24:14 <shelikhoo> let's call it a meeting!
16:24:26 <shelikhoo> #endmeeting