16:00:17 #startmeeting tor anti-censorship meeting 16:00:17 here is our meeting pad: https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469 16:00:17 editable link available on request 16:00:17 Meeting started Thu Apr 17 16:00:17 2025 UTC. The chair is shelikhoo. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:19 hi~hi~ 16:00:43 I was just about to start the meeting >.< 16:00:44 oh well 16:01:05 * dcf1 recognizes the facilitator 16:01:08 hi "D 16:01:11 :D 16:01:28 yes, I see I was the facilitator in the meeting 16:01:38 that was for next meeting 16:01:42 for the "next meeting" field 16:01:45 oooooooo 16:01:48 since meskio is away, we had to skil him 16:01:55 anyway it is not that important 16:02:01 yeah, it's not lol 16:03:27 I didn't see any discussion topic 16:03:43 but there was a interesting link about tls1.3 getting blocked 16:03:53 let's discuss about this link first 16:04:00 https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40057#note_3189889 16:04:00 "users from some regions report tls 1.3 being blocked" (Russia) 16:04:19 I wonder whether the thing get blocked is tls 1.3 or just ESNI 16:04:29 nina13[m]: do you have a link or reference? or is this information from user support requests? 16:05:06 dcf1: it is from ntc.party - users reported this 16:05:10 I am curious whether it is TLS 1.3 itself, or TLS 1.3 + ECH. 16:05:27 oh yes ECH, not ESNI 16:05:32 my bad.... 16:06:12 nina13[mds]: ok. if you have a link handy, it's helpful for me if you include it in the issue comment. otherwise I have to scroll through the NTC threads one post at a time, clicking the "translate" button, which I do sometimes but it takes a long time 16:07:16 dcf1: yep: https://ntc.party/t/%D0%BF%D0%B5%D1%80%D0%B5%D1%81%D1%82%D0%B0%D0%BB%D0%B8-%D0%BE%D1%82%D0%BA%D1%80%D1%8B%D0%B2%D0%B0%D1%82%D1%8C%D1%81%D1%8F-%D0%BC%D0%BD%D0%BE%D0%B3%D0%B8%D0%B5-%D1%81%D0%B0%D0%B9%D1%82%D1%8B/15818/6 16:07:57 Relating to the request to businesses to whitelist specific protocols/connections (https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40057#note_3187885), there's some references to similar requests back starting in 2021 16:08:01 https://github.com/net4people/bbs/issues/76 16:08:04 https://ntc.party/t/rkn-will-try-to-block-the-following-vpn-services/1022 16:08:15 nina13[m]: thank you 16:09:51 PS, sometimes it's convenient to know it's possible to trim the horrible '%XX%XX' part of those Discourse URLs: https://ntc.party/t/15818/6 16:10:33 The URLs derived from the thread title work ok for English, but not so much for UTF-8 Cyrillic text :) 16:13:04 at least it could be copy pasted.... for simplified chinese and japanese, characters share the same Unicode code, even if they are written differently 16:13:23 dcf1: thanks! Didn't know that 16:13:57 and basically one need to known that language the text is in to render it correctly 16:14:02 the same before unicode 16:14:05 shelikhoo: yes, the percent-encoding is the only reasonable thing to do for interchange of URLs, it's just not so nice to look at 16:14:56 I didn't see any discussion about ECH in the ntc party link 16:15:34 I could try if such blocking can be reproduced on vantage point 16:17:33 anything more we would like to discuss about this topic? 16:19:25 anything more we would like to discuss in this meeting? 16:19:37 nothing from me 16:20:59 thanks! we could discuss the tls1.3 censorship topic again once we have more data 16:21:01 #endmeeting