@fosdem #FOSDEM highlights. We tried something new, and it was a bit bumpy, but it was fun! I was volunteered to MC it, which meant I had three talks back to back. I like stress I guess.

@fosdem #FOSDEM closing talk. I promised not to blur the sides photos this time

@fosdem #FOSDEM debugging... Part of K lost power. We traced it to one circuit breaker, and kept putting it back in while dividing and conquering towards finding the fault.

As @SwiftOnSecurity keeps saying, there's an advantage in being tall. Instead of going up and down the ladder all the time, I simply grabbed a broom and kept pushing the lever up again and again and again until we found it. A power strip had developed a short...

@fosdem and finally, #FOSDEM staff dinner. I've been looking forward to this weekend for weeks, and I am sooooo happy it's finally over.

People will unload the vans tomorrow, sort and count and account and repair and such over the next week or so. We'll do a mix of in-person and remote post mortem in two weeks. And then we don't want to think about FOSDEM until August...

@fosdem random #fosdem reminder:

If you have T-shirts from previous editions, do bring them.

We will have a group photo with 25 years of [F]OSDEM shirts

@fosdem all #FOSDEM #Monitoring & #Observability devroom acceptance emails have been sent out and all reconfirmations received. Subsequentially all rejections have been sent just now.

@fosdem if you're a #photography person and attending #fosdem: we're planning to do a "25 years of FOSDEM shirts" photo with as many people as we can get. If you can commit to coming to FOSDEM with a decent full frame digital camera, a tripod, and maybe some flash(es) we would hugely appreciate it.

Reply in thread or send me a DM with your email address or something to get in contact

@fosdem I just announced our temporary #IPv4 PI space 151.216.128.0/17 for #FOSDEM. If you want, you can follow it starting to become visible over the next hours and days on any #BGP #lookingglass, e.g. https://lg.de-cix.net/ has quite a few globally so you can see it spread.

As of this writing, https://lg.de-cix.net/search?q=151.216.128.0%2F17 has it in Frankfurt and Marseille, and nowhere else. Usually for new BGP announcements from EU, they show up in LATAM last, with a delay of up to three days.

@fosdem ignore the route object errors for now; the databases for ISPs (Internet Service Providers) and IXPs (Internet Exchange Point) get updated every few hours to once per day.

If you want to see the route object I created for #FOSDEM earlier, see
whois -h whois.ripe.net 151.216.128.0/17AS62392

Not a lot to it, but maybe it's interesting for someone?

@fosdem I was asked privately for the "how", and figured a public reply makes sense

https://www.ripe.net/publications/docs/ripe-801 is the policy.

Fun fact: The extra time around an event used to be 7 days, and this was distilled pain as I had to chase #FOSDEM #BGP upstreams to update sessions, filters, etc and usually needed to escalate through to last level support

Before automation and the Cloud, a new #BGP announcement took days to weeks by default

So I got the #RIPE policy changed and extended to 1 month

@fosdem I should probably get started on writing the #FOSDEM opening talk

Today was a very interrupty day, but everything's working, the network is up and reachable everywhere, and half of us are already looking forward to the event being over

@fosdem I didn't get to start the slides until 23:30 and only finished at 09:08, but the #FOSDEM opening slides were done and presented successfully. Only five more sessions to go

@fosdem #FOSDEM is running well enough that I was able to leave the NOC for something other than toilet breaks repeatedly today!

I got to see the sun!

This is good, as I was able to, you know, do stuff.

But it also meant that it took me ~1.5 hours to get from H to K because I met so. Many. People.

Several, I have not seen since before the pandemic and always missed them as I was stuck in the NOC.

To compensate, I will be doing five sessions tomorrow and still need to prepare four of them

@fosdem only need to prepare three now

@fosdem Reminder: The #FOSDEM 25 year t-shirt photo takes place today at 14:30 in K.1.105:

https://fosdem.org/2025/schedule/event/fosdem-2025-6728-group-photo-25-years-of-fosdem-shirts/

CC @thomas @helioloureiro

@fosdem That's a wrap!

We're still tearing down & cleaning up, but I'll spend some minutes on #FOSDEM updates backfill

A view into our new video boxes.

More details in https://fosdem.org/2025/schedule/event/fosdem-2025-6714-fosdem-infrastructure-review/ & https://fosdem.org/2025/schedule/event/fosdem-2025-6832-fosdem-videobox-2025/

@fosdem Opening the #FOSDEM #Monitoring & #Observability devroom on Sunday. It was empty in the morning but flipped to being full with lines outside soon enough.

Again, another videobox, showing the built-in display

Edit: the first photo was from 30 minutes before we opened. During opening, we were at maybe 1/3th capacity already

@fosdem Shortly after, i talked about 25 years of #FOSDEM, sharing various anecdotes.

https://fosdem.org/2025/schedule/event/fosdem-2025-6729-anecdotes-from-25-years-of-fosdem/

We had Raphael join us and also share a few stories. He started OSDEM 25 years ago!

There was also the dance.

@fosdem Right afterwards, we had the 25 years of #FOSDEM and open source t shirt photo. Maybe we will do that again in the future.

I'll share photos later when I have had some time.

https://fosdem.org/2025/schedule/event/fosdem-2025-6728-group-photo-25-years-of-fosdem-shirts/

@fosdem Then, Basti and myself did the #FOSDEM infrastructure review.

It was rather empty, as the videobox talk was at the same time. Bad planning in hindsight, but I'm very happy the videobox talk had so many attendees

https://fosdem.org/2025/schedule/event/fosdem-2025-6714-fosdem-infrastructure-review/