#FOSDEM opening talk from the other side.

#FOSDEM opening talk from the other side. It's really good to be back in person.

#FOSDEM infrastructure review talk, this time largely delegated to Basti Schubert (not on Mastodon). His first public talk!

@fosdem #FOSDEM closing talk about to start. We're letting the NASA talk run over schedule to a packed room

@fosdem Maybe I'll remember to keep all the #FOSDEM talks in in one thread? Let's see

#FOSDEM 2024 opening talk! We had 20-33% first timers!

As per usual, many, many people standing at the back and at the sides. (sorry for the blurry second photo, I hurried too much)

@fosdem we forgot if he lost a bet or why we ended up here...

Anyway, if you need urgent Pokemon help, come to #FOSDEM K Infodesk. All Pikachus are standing by.

@fosdem It's a bit of a #FOSDEM tradition by now.. in 2020, I put into an internal platform that I needed $something plus Gerry in a duck suit and he replied that if anything he'd only wear a moose suit.

Anyway, challenge me on those things at your own risk

@fosdem #FOSDEM Monitoring and Observability opening, Sunday morning are always slow; we had the room full and lines outside in no time

@fosdem #FOSDEM hack. We couldn't refill the hand towel dispensers in the toilets. So the #FreeCAD people designed a key for us, #Prusa people @3dprinting #3dprinting it for us, and the cleaning staff could refill everyone's hand towels.

@fosdem #FOSDEM infrastructure review; good crowd and many questions as per usual. I had to leave early to the FOSDEM highlights, but Basti covered the rest.

@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