14:59:47 <richard> #startmeeting Tor Browser Weekly Meeting 2024-03-04 14:59:47 <MeetBot> Meeting started Mon Mar 4 14:59:47 2024 UTC. The chair is richard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:47 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:54 <richard> i think that date is right 14:59:59 <richard> the pad: https://pad.riseup.net/p/tor-tbb-keep 15:00:51 <richard> as usual please take this time to update your boards, and provide some time estimate breakdowns in the pad 15:01:21 <richard> 13.5a5 is out and deployed for all platforms 15:01:44 <richard> we didn't have any spikes in 13.5a5 related crashes on Android over the weekend, so that's moved up to 100% deployment 15:03:50 <richard> and that concurrent data modification crash from 13.5a4 seems to have disappeared in 13.5a5 as well :) 15:04:03 <Jeremy_Rand_36C3[m]> yay 15:05:27 <richard> We may be releasing an early stable to deal with a censorship circumvention issue but we will see how that plays out 15:11:16 <richard> ok does anyone have any dicussion points? anybody blocked on anything? 15:11:40 * PieroV doesn't 15:11:47 <Jeremy_Rand_36C3[m]> Nothing here 15:11:55 <ma1> good here 15:12:19 <henry-x> nothing from me 15:12:23 <dan_b> all good 15:12:45 <richard> alright then, short and sweet today 15:12:54 <richard> have a good rest of your day and rest of your week o/ 15:12:57 <richard> #endmeeting 15:13:02 <Jeremy_Rand_36C3[m]> Thanks! 15:13:11 <PieroV> Thanks! o/ 15:13:18 <ma1> grazie, ciao 15:58:27 <ggus> o/ 15:58:34 <juga> o/ 15:59:10 <ggus> i heard about network health meeting, is this the right place? :) 15:59:24 <hiro> o/ 15:59:26 <GeKo> yeah 15:59:40 <GeKo> sorry, i am in another meeting 15:59:42 <GeKo> and coming 15:59:50 <hiro> ggus: just around the corner from the coffee machine, feel free to grab a drink on the way 16:00:01 <MeetBot> GeKo: Error: Can't start another meeting, one is in progress. 16:00:03 <ggus> thanks! 16:00:17 <GeKo> hah, the application team folks did not close their meeting 16:00:36 <ggus> #endmeeting 16:00:37 <hiro> well seems richard tried but something didn't work 16:00:37 <GeKo> richard: can you end your meeting? 16:01:03 <GeKo> hrm 16:01:05 <richard> #endmeeting 16:01:06 <richard> ??? 16:01:18 <GeKo> o_O 16:01:22 <GeKo> #endmeeting 16:01:26 <GeKo> awesome 16:01:30 <ggus> #endmeeting 16:01:44 <richard> #endmeeting 16:01:46 <richard> ... 16:01:49 <GeKo> we should have a meeting about how to end meetings :) 16:02:03 <MeetBot> richard: Error: Can't start another meeting, one is in progress. 16:02:08 <richard> oook 16:02:31 <richard> look at me, I'm the meeting runner now 16:02:38 <GeKo> good stuff 16:02:55 <GeKo> let's just do it and ignore our meetbot 16:02:56 <richard> who's in charge of meetbot? 16:03:01 <richard> ack l8r sk8rs 16:03:06 <GeKo> will be the longest meeting in history 16:03:09 <GeKo> o/ 16:03:13 <ggus> o/ 16:03:20 <GeKo> so 16:03:26 <GeKo> https://pad.riseup.net/p/tor-nethealthteam-2023-keep is our pad 16:04:02 <GeKo> ggus: so, one item i have: what do we do for eol bridges? 16:04:18 <GeKo> do we wait a bit or should we start reaching out to folks this week? 16:04:34 <GeKo> the situation for bridges is usually worse than for relays 16:04:42 <GeKo> which is kind of interesting in itself 16:05:08 <ggus> it's an entire phd dissertation 16:05:20 <GeKo> lol 16:05:23 <ggus> we could do this week 16:05:42 <ggus> and reject sometime in april 16:06:04 <GeKo> well, it's actually not so many more bridges 16:06:06 <GeKo> 629: 0.4.7 [28.82 %] (MAJOR) 16:06:24 <ggus> :S 16:06:25 <GeKo> it's "just" a large fraction of them 16:06:30 <GeKo> *larger 16:07:14 <GeKo> okay, i can try to compile the spreadsheets this week and get this started 16:07:15 <ggus> actually 16:07:24 <GeKo> i'll add stuff to the eol ticket 16:07:27 <ggus> we should check if the docker image is up to date 16:07:36 <GeKo> meskio said, yes 16:07:55 <GeKo> but, sure, doublechecking might be goood 16:08:50 <GeKo> okay, what else do we have for this week? 16:08:51 <ggus> another proposal: we only work on this after the elections in russia, end of march? first week of april i'll be afk 16:09:05 <GeKo> ggus: i am fine either way 16:09:43 <ggus> ok, let's contact bridge operators on week of 18th 16:09:54 <GeKo> ack 16:11:15 <GeKo> hiro: welcome back! :) 16:11:25 <hiro> o/ 16:11:44 <GeKo> for the sponsor112 stuff we have a whole meeting tomorrow on bbb 16:11:59 <GeKo> so, as a reminder that's 1600utc :) 16:12:06 <juga> ack 16:12:14 <hiro> ack 16:12:25 <ggus> ack 16:12:28 <GeKo> ack 16:12:46 <GeKo> everyone on the same page, awesome :) 16:13:02 <GeKo> any other questions, concerns, proposals etc? 16:13:11 * juga is good 16:13:56 <ggus> there are some issues with metrics 16:14:03 <ggus> i reported on #tor-project 16:14:06 <GeKo> tell me something new :) 16:14:10 <hiro> yeah 16:14:26 <hiro> ggus I have seen the snowflake issue 16:14:31 <hiro> but I haven't been to look into that 16:14:35 <hiro> is there something else? 16:14:43 <hiro> been able* 16:14:52 <ggus> this graph is also broken: https://metrics.torproject.org/bridgedb-distributor.html 16:15:08 <ggus> i guess it fwas fixed, but it's broken again 16:15:18 <hiro> uhm I wonder if the r server is ok 16:15:22 <hiro> let me check real quick 16:17:00 <GeKo> ggus: so the snowflake graps is correct, though? 16:17:17 <GeKo> or what is wrong with that one? 16:17:20 <GeKo> *graph 16:17:32 <hiro> yeah the rserver is ok 16:17:45 <hiro> might be something w the code but I wonder what since we haven't changed it 16:18:57 <GeKo> ggus: anyway, i guess file a ticket? 16:19:24 <GeKo> i am not sure what is wrong with the bridges graphs you posted to #tor-project 16:19:42 <GeKo> but, yeah, https://metrics.torproject.org/bridgedb-distributor.html is not happy, for sure 16:20:04 <GeKo> okay, let's close this meeting, though 16:20:07 <ggus> 2 hours ago it didn't have any drop on snowflake usage and the "Any pluggable transport" wasn't reporting any drop of snowflake usage 16:20:08 <GeKo> #endmeeting 16:20:28 <GeKo> ggus: ah, so, it's right now? 16:20:54 <ggus> there is a small drop on total bridge users now, but i don't know if it corresponds with the amount of snowflake drop 16:22:06 <juga> on grafana2 i can see something happened at 15:30 16:22:28 <juga> hmm, or at 13 16:22:33 <GeKo> okay, does not look too bad to me 16:23:37 <hiro> the update process finished around 12.30 CET 16:24:51 <ggus> ok! 17:19:10 <MeetBot> ggus: Error: Can't start another meeting, one is in progress. 17:21:37 <trinity-1686a> hum, maybe ask on #meetbot ? 17:51:56 <richard> #endmeeting 17:52:03 <richard> vOv 12:52:43 <trinity-1686a> #endmeeting 12:53:15 <MeetBot> trinity-1686a: Error: Can't start another meeting, one is in progress. 12:53:19 <trinity-1686a> #endmeeting 12:55:39 <emmapeel> #info 12:56:22 <ggus> #endmeeting 12:56:34 <ggus> #endmeeting 12:57:33 <emmapeel> hmm. i read on the backlog and it seems the last meeting was closed 12:57:56 <emmapeel> not sure what is going on 12:57:56 <gaba> meetbot is getting tired of meetings 12:57:56 <MeetBot> gaba: Error: "is" is not a valid command. 12:58:09 <MeetBot> ggus: Error: Can't start another meeting, one is in progress. 12:58:19 <gaba> uh 12:58:38 <emmapeel> it seems is this meeting still: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-03-04-14.59.log.txt 12:59:09 <emmapeel> richard has tried to close it several times, but the meetbot does not believe them 13:00:03 <trinity-1686a> from #meetbot > something spammed its access.log, disk full. meh. fixed. 13:00:19 <emmapeel> thanks trinity-1686a 13:00:41 <trinity-1686a> afaict, it's not fixed, so we'll wait for more replies ig 13:25:33 <emmapeel> #endmeeting 13:25:48 <MeetBot> emmapeel: Error: Can't start another meeting, one is in progress. 13:25:51 <emmapeel> hmm 13:26:01 <emmapeel> richard: could you please try again? 13:26:10 <richard> #endmeeting