Notices by Richard "RichiH" Hartmann (richih@chaos.social)

@fosdem we finished teardown, cleanup, and volunteer dinner at around 21:30, and went for #FOSDEM staff dinner right afterwards. We got to sleep at around 0030.

Today, the trucks will be unloaded, stuff put away, sorted and repackaged.

Two weeks of no FOSDEM anything (hopefully) and then it's back to Brussels for the Post Mortem in two weeks.

@fosdem if you want to #getfedihired #fedihired , feel free to look through the #job corner at #FOSDEM

@fosdem #FOSDEM ask: If you have any #Cisco #SPA500 series #VoIP phones you don't need any more or might be cycling out of use over the year, please get in contact with us / me.

We have had fixed phones at a few key locations this past weekend and want to expand the use of static phones. So an upper bound of maybe 50-60 phones would be very useful to us accounting for all devrooms and for a few spares.

Edit: Retoots explicitly appreciated.

@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 1-2 weeks, 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 a 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 :p

@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/

@fosdem And then, I closed #FOSDEM out with the closing keynote: https://fosdem.org/2025/schedule/event/fosdem-2025-6713-closing-fosdem-2025/

Second time in a row that I couldn't do the closing dance for health reasons, hopefully 2026 is better.

But no matter if kidney stone, car accident, or whatever. I'd attend #FOSDEM in a wheelchair if need be.

Two weeks! Two. Whole. WEEKS!

As of 30 minutes ago, the published videos from #FOSDEM 2025 have more than TWO WEEKS OF TOTAL RUNTIME!

If you sat down on day 1 in the morning and started watching videos all day every day, no breaks and no sleep, you would still be watching by the time we're sitting down for the Post Mortem in Brussels next Saturday noon. And we still have 100+ videos left to finish.

Largest #OpenSource conference on Earth.

https://video.fosdem.org/2025/

Hey @ConnyDuck before I open a bug report, I just wanted to check:

The mute times for #Tusky and Mastodon's web interface are different: On the app, I can set a maximum of 7 days, on the web interface it's 30 days max.

Is that a free-form number / target datetime storage in the backend or how does this work?

Expanding Tusky to support at least 30 days would appear to be easy, then?

@ConnyDuck Thanks! Would you be willing to toss 30 days, and maybe 180 or even 364 days, into the options?

I've had 1-2 cases where I took manual notes; some people calm down after a longer time.