Week in Fediverse 2026-05-22
Servers
- Gush! v0.0.37
- Stegodon v1.8.5
- Iceshrimp.NET v2026.1.1-beta
- Iceshrimp v2026.5.1
- Hollo v0.9.0
- Mastodon v4.5.10
- PeerTube v8.1.6
- Sharkey v2025.4.7
- Hubzilla v11.2.1
- Friendica v2026.05
- Ktistec v3.3.9
- Smithereen v1.0.0
- Vernissage Server v1.38.0
- ActivityPub for WordPress v8.3.0
- Misskey v2026.5.4
- tootik v0.22.2
- NeoDB v0.14.4
- Open beta testing for Lemmy 1.0.0
- Trunk & Tidbits, April 2026
- XMPP/ActivityPub Bridge: Chat between XMPP and the Fediverse
- Cookifed: A free and federated recipes management app and cooking social network
Clients
- Nicolium v0.3.0
- Fedilab v3.40.1
- Aria v1.5.1
- Blorp v1.14.0
- Impressia v3.2.0
- Holos v1.6.0
Tools and Plugins
- Analytodon: Analytics for Mastodon
For developers
- Fedify v2.2.3
- BotKit v0.4.2
Protocol
- Basic Profile for Social API Servers
- FEP-baf5: Administrator Collection
Articles
- the may 2026 fedi software vulnerability
- Never Lose a Toot Again: Full-Text Search for Your Mastodon Feed
-----
#WeekInFediverse #Fediverse #ActivityPub
Previous edition: https://mitra.social/objects/019e2d21-c15d-7653-a6d5-f476dcc0559d
Tak! (@[email protected])
gush! v0.0.37 is here! gush! is the federated social media platform for gushing about the things you love For users Add search to the gushable list candidate selector https://codeberg.org/gush/gush/issues/122 Add an explicit merge button to the gushable view Add a skip link to the post page in the header Try extra super hard to not merge gushables based on blank identifiers Add redirects for gushable add to list / follow / unfollow instead of silent success or failure in background Linkify post context breadcrumbs Clean up the event creation ui layout Fix posting language-tagged code blocks Fix the conversation reference on event reminder notes Support peertube View activities Accept a wider range of declared attachment types on remote objects Track the new names of gotosocial approval types (Approval => Authorization) Don't fail to federate outgoing activities if the rdf normalizer throws an exception Fix the following endpoint returning followers 🤦 For admins Experimental support for using an s3-compatible service as the storage backend for attachments Implement http message signatures (rfc 9421) Handle exceptions in note cleanup batches Add a better log message for when an unhandled exception causes a service to exit Add more logging to the federated import service Only sign and store outgoing activity objects once gush
