15:59:00 #startmeeting network-health 05/15/2023 15:59:00 Meeting started Mon May 15 15:59:00 2023 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:00 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:04 hello! 15:59:09 https://pad.riseup.net/p/tor-nethealthteam-2023-keep 15:59:12 is our pad 15:59:14 o. 15:59:15 o/ 15:59:17 o/ 15:59:20 Hi everyone! 15:59:21 please add items as you see fit 15:59:25 mattrighetti[m]: welcome! 15:59:32 nice to have you here 15:59:34 welcome mattrighetti[m] 15:59:43 ggus: meeting time 15:59:48 juga: ^ 15:59:53 hello 15:59:57 o/ 16:00:01 wb! 16:00:51 :D 16:01:05 alright 16:01:32 o/ 16:01:50 ggus: so, i did all the bridge ops contacting for eol bridges and keeping track of new eol relays 16:02:00 i think it's time now to get the relays out of the network 16:02:10 i've prepped a commit to do so 16:02:24 but thought about waiting for you to push me off that cliff :) 16:02:40 as to the stats 16:03:11 it's not much difference compared to what we rejected when 0.3.5 went EOL 16:03:17 alright! 16:03:20 it's about the same amount of relays and bw 16:03:24 which seems reasonable 16:03:41 even though i'd had of course hoped to have less relays to reject... 16:04:51 if you think that's okay, i'll push after the meeting and send a follow-up to tor-relays@ 16:05:11 it's okay, do you plan to reject new EOL relays every week then? 16:05:17 yeah 16:05:28 until the dirauths have picked up 0.4.8 16:05:41 ok! 16:05:41 which will have the commit to reject those relays at the dirauth level 16:05:47 great 16:06:01 ggus: it might be useful to sync maybe tomorrow or so? 16:06:15 there are a bunch of things that have piled up while you were afk 16:06:25 sure! 16:06:35 including the core contributors follow-up from cr and s112 stuff etc. 16:07:07 tomorrow works for me 16:07:09 okay, we can do a 2 person doodle after this sync i guess :p 16:08:08 do we have anything else before moving on to the s112 part? 16:08:40 i need to work on the tor relay meetup notes from april, will do this week 16:08:51 nice 16:08:58 did we say when the next meetup will be? 16:09:13 i don't recall anything like that 16:09:42 the first weekend in june does not work for me 16:09:50 but i could do before and after 16:10:35 i guess we will need to do later in june 16:10:41 in may will be difficult for me 16:11:18 okay 16:12:25 let's talk some s112 16:12:48 hiro: thanks for all the follow-up issues for collector#40016 16:13:06 o/ no probs 16:13:08 i guess we still need to file some or go over the comments again? 16:13:27 or do you think you have everything accounted for? 16:13:33 i can take a fresh look tomorrow 16:13:40 I was just going over all the comments 16:14:00 I think what I can do is attach the tickets number to the comment 16:14:25 okay, feel free to do so 16:14:35 i'll have another look at that tomorrow as well 16:15:18 i worked on small doc fixups while i was at it and a bit at moving the proposal stuff forward for o2.2 16:15:30 ggus: i cc'ed you on the dirauth thread 16:15:47 we'll see how that cat-herding will play out... 16:16:24 that's all from me for s112 16:16:37 anything else from anybody? 16:16:45 * juga is fine 16:16:47 juga: wb to you as well :) 16:16:52 I just wanted to give an update on network apis 16:16:55 GeKo: thanks! 16:17:13 juga: we could sync tomorrow as well (one day earlier) if that helps you 16:17:27 for planning your work and getting up-to-speed or anything 16:17:37 GeKo: wednesday as usual is fine, so is tomorrow, as you prefer 16:17:38 otherwise i guess wed would work as well 16:17:54 let's do wed then, thanks 16:18:01 GeKo: yrw 16:18:05 mattrighetti[m]: nice. go ahead 16:18:19 I mostly read code this week, especially onionoo to see how responses are constructed from files. I've also started to do some env setup and coded a small part of the api endpoints and responses 16:18:51 I'm currently waiting for pg access and I'll probably need a hand or two to understand how I can query onionoo data from the metrics tables 16:19:11 yeah 16:19:29 I think that table attributes don't have the same name of table attributes but that shouldn't be a problem 16:19:34 oh, and juga is back so we could ask them to add the rust coding style stuff to our wiki :D 16:19:50 GeKo: ah, noted 16:19:50 Yeah that would be great 16:19:52 mattrighetti[m]: yes we need some mapping 16:20:22 That's it from me 16:20:30 the onionoo fields are spec-ed out, but the names with what we were parsing in metrics-library might differ 16:20:37 we have actually an issue to address that 16:21:05 ping me anytime you find something that needs clarification 16:21:28 sure will! thanks 16:23:07 alright 16:23:11 do we have anything else for today? 16:23:23 i'm good 16:23:35 as a PSA i will be out on thursday due to a pubic holiday :( :) 16:24:22 * hiro is groot 16:24:37 okay 16:24:46 thanks folks and have a nice week o/ 16:24:48 #endmeeting