First talk today at the Social Web Devroom we have @pfefferle talking about the state of WordPress's fediverse integration
#FOSDEM #ActivityPub #fedidev
Excited to see WordPress still using the @FediverseSymbol throughout the interface
Next up is @andypiper and @haubles talking about @Mastodon's vision
@andypiper: "mastodon is part of a movement" "it is part of the fediverse"

@haubles just dropped the massive news that Mastodon is going to be changing the default signup flow on mobile apps to choose an instance thats geographically close to you instead of choosing mastodon.social by default!

UPDATE: their official announcement here: https://mastodon.social/@Mastodon/115989801184595302

the internet went down and then I went to get a coffee with @douginamug! Just got back and caught the end of @bjoernsta's talk about https://savesocial.eu
Homepage

Networks For Democracy. Das freie Internet wird abgeschafft – es wurde von den Big-Tech-Monopolen übernommen. Die wachsende Dominanz der Plattformkonzerne für Information und Austausch führt zu einer Konzentration von Meinungsmacht, die unsere Demokratie gefährdet. Doch das Internet gehört uns allen, wir müssen es von der Dominanz der Monopolkonzerne befreien: Unsere Gesellschaft braucht andere Plattformen für...

Save Social
And now @cypherhippie has a lightning talk about bringing #DIDs to the fediverse
A slide of a slide of @arcalinea talking about using DIDs for ATProto
A slide of @snarfed.org agreeing with the premise of bringing DIDs to the fediverse
Core Assumptions
1) "Communities must be in control"
2) "Nobody shall be locked-in"
3) "There is NO FREE marketplace of ideas."
Next we have @django presenting some ideas about moving the ActivityPub API C2S forward
A quote from @Gargron about how C2S was seriously lacking
Oh hell yeah looks like @django used my https://iconography.fediverse.info for their slides!
After a short break we have @raffomania is presenting a new federated bookmark sharing software called 'ties'
https://github.com/raffomania/ties
The philosophy of 'ties'
Oh @raffomania wants to do full text search of an archived version of websites from 'ties'
@samvie up next with a talk about digital sovereignty!
all the orgs that signed the "open networks and democratic public spheres" alience
Fedimedia Italia presenting their association!
Who is Fedimedia Italia:
Wow Fedimedia Italia has *a lot* of instances
Oh cool and also @raccoonforfriendicaapp and #Flohra are also under their umbrella

@tsyesika and @cwebber up next talking about what's next for the fediverse!

https://stream.fosdem.org/h2215.m3u8

The fediverse is not done!
@tsyesika is talking about issues with naming and fishing and has a slide up with a fake @Gargron account
They are talking about what the fediverse would look like if we were using more generic servers
@FediVariety up next about getting public agencies to use the fediverse
Taking a tiny break to get some fresh air and then ruin the freshness with a cigarette and then back to my regularly scheduled programming. @andypiper has awarded me "official love blog status" so now my duty has peerpressure!
Had a longer break then I meant to opps!
Now we have @mayel and @ivan presenting @bonfire!
"ActivityPub is a contaminatiion vector" - @Bonfire
@coopcloud getting a shoutout from #Bonfire
Wow Jacobin.de is gonna be using Bonfire and Lauti with a white-labeled mobile app by Newsmast
Just shouted out some important things to come like working with @anewsocial and @bsky.brid.gy and with @swf on encryption
Now we have @hongminhee presenting @fedify!
@fedify abstracts away complexity in building for the fediverse
I sadly had to step out so I missed @tobias's presentation about the amazing Friendica but there should be a recording of it
https://fosdem.org/2026/schedule/event/DNS7Z8-friendica_-_hidden_in_plain_sight_since_2025/
FOSDEM 2026 - Friendica - Hidden in plain sight since 2025

Then @cubicgarden and Samuel Margerison are presenting their Fedi Legacy project
https://fosdem.org/2026/schedule/event/VGXMXE-machine_readable_wishes/
Now @mobilizon is presenting a quick overview of their event software
@liaizon @mobilizon Hey thank you so much for those posts!
@raphael I hope it was useful! It was sorta exhausting but it seemed like someone needed to be doing it so I figured it might as well be me
@liaizon @mayel @ivan @bonfire I missed the Bonfire talk unfortunately but I'm very interested in watching the recording when that's up! I've been thinking about standing up an instance for my local community recently - it seems super cool
@liaizon @tsyesika @Gargron this is what rel=me integration is for.
@KevinMarks @tsyesika that doesn't help in this case unless that information is used and visualized in places like name autocomplete and weighting of search results. Also it requires everyone to have a website or place that they own which is only the case for tech and larger personalities
@liaizon @tsyesika I've had 2 impersonators on mastodon.social in the last month, so prioritising accounts with bidirectional rel=me links in autocomplete would help.
@liaizon I can see an open source solution already exist for each issue, why groups don't talk each other's?
@uriel there isnt an implementation of any protocol that has all these properties, which is one reason why Christine has been working on Spritely Goblins this whole time

@liaizon There are—and more than one. Never heard of RetroShare? Instead of declarative sentences like "there is no," why not say "I am not aware of any"?

Yet you've answered my question: you don't exchange knowledge because you think you know everything.

@uriel this is a talk about these properties *for* the fediverse. Retroshare is not being made for global public communication or many of the things that we use the fediverse for. I don't think Retroshare would want people to try to shoehorn the project into use for the sorts of things that Spritely is being built for

@liaizon

Not quite.

ActivityPub doesn’t prescribe a specific transport layer for delivering its activities. In practice, most deployments use HTTPS today, but in principle the transport could be swapped for something else—anything from SIP to SMTP to libp2p.

So there would be no inherent obstacle if an implementation chose to use Bitmessage (the protocol behind retroshare) as its transport.

You’re not seeing many alternatives largely because you’re assuming that what you haven’t encountered simply doesn’t exist.