If you are interested in how the Fediverse really works and some of the key people making it happen, sit down with a coffee and check out one (or all!) of the presentations from #fedicon.

Mine was about my journey finding the Fediverse and eventually teaming up with folks to create socialbc.ca and what I learned along the way.

And yes, I am pretty sure we are in a Stanley Kubrick movie.
#fediverse #mastodon #socialbc #democracy #webstandards #activitypub #community
https://spectra.video/w/p9nScG9XFX81iE89ufmWUM

You can see all the videos that have been uploaded so far on the #fedicon page here at spectra.video. #peertube

https://spectra.video/c/fedicon_videos/videos

#fediverse #mastodon #socialbc #democracy #webstandards #activitypub #community

You can see all the videos that have been uploaded so far on the #fedicon page here at spectra.video. #peertube

https://spectra.video/c/fedicon_videos/videos

#fediverse #mastodon #socialbc #democracy #webstandards #activitypub #community

If you are interested in how the Fediverse really works and some of the key people making it happen, sit down with a coffee and check out one (or all!) of the presentations from #fedicon.

Mine was about my journey finding the Fediverse and eventually teaming up with folks to create socialbc.ca and what I learned along the way.

And yes, I am pretty sure we are in a Stanley Kubrick movie.
#fediverse #mastodon #socialbc #democracy #webstandards #activitypub #community
https://spectra.video/w/p9nScG9XFX81iE89ufmWUM

"The solution isn’t building better platforms — it’s making platforms an obsolete concept. Platforms concentrate power; protocols distribute it. Platforms extract value from users; protocols enable users to create value for themselves. Most importantly: platforms can be captured by bad actors, but protocols resist capture by design."

https://www.techdirt.com/2025/08/05/take-back-our-digital-infrastructure-to-save-democracy/

#Technology#PeopleNotPlatforms#Fediverse#ActivityPub#Bluesky#ATProto#OpenSocial#OpenSocialWeb

(1/2)

"It's very hard to build on top of the fediverse as it is now. It's easy to build *part* of the fediverse, but you can't build a layer on top of it."

@rabble, 2025

https://wedistribute.org/podcast/s2e3-rabble-from-nos-social/

What about the FEP process? It's already documented a range of protocol extension proposals and more are in the works. If we can get reps from a critical mass of app teams, then mass adoption gets much easier.

#ActivityPub #FEP

@76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa

#nextcloud made it possible for me to (self-)host my (and my family's) phone calendars, contacts, and even when pictures are taken, they get uploaded to our Nextcloud instance, and NOT to google/apple.

10/10, would recommend for any household looking to #degoogle.

Others include #searxng, has literally replaced all monolithic search engines, works great, no ads or AI

#mastodon, for my #activitypub based social network

#matrix for chatting with my social network

and also #KDE.

Hallo @acka47 et al.

ich habe nun wegen semantischer Kompression ein Demo hierhin gepackt
:digitalcourage: https://github.com/sebilasse/compressDE

Das Ziel ist es, #ActivityPub Objekte um etwa 80% zu komprimieren. Das Resultat ist ein UInt8Array für alle naturalLanguage-Texte. Andere Sprachen können aus Corpora generiert werden.

Es bietet sich insbesondere für ältere oder wenig genutzte Objekte an.
Das Resultat im Demo ist etwa 25% des Originals. Ich weiss halt nicht, ob das gut ist.

[EN] Esteemed fediverse
see the readme of the repo for semantic compression

Monthly meetings are held on the first Thursday of each month, at 13h00 to 14h00 Eastern Time (currently 17h00 to 18h00 UTC). You can find them listed in the SocialCG Calendar. The next meeting will be held on 7 August 2025.

We will be discussing:

• FEP 7888/f228 adoption update
• Context Inheritance
• Context Ownership
• Merging of Contexts (aka "cross-posting")

We'd like to recognize some excellent contributions from our #OSSCA (Open Source Contribution Academy) participants who have been working on #Fedify.

@gaebalgom contributed PR #339, which introduces the @fedify/elysia package to provide Elysia integration for Fedify. This work addresses issue #286 by creating a plugin that enables developers using #Bun and #Elysia to integrate Fedify's #ActivityPub capabilities into their applications. The contribution includes the core integration module, documentation, examples, and proper monorepo configuration, making Fedify accessible to the Elysia community.

@r4bb1t submitted PR #315, implementing comprehensive AbortSignal support across multiple APIs to resolve issue #51. This contribution adds request cancellation capabilities not only to lookupWebFinger() but also to lookupObject(), DocumentLoader, and the HTTP signature authentication flow (doubleKnock()), allowing developers to properly handle timeouts and abort ongoing requests throughout the entire request chain. The implementation includes extensive test coverage for cancellation scenarios across all affected components and lays the groundwork for adding --timeout options to various CLI commands like fedify lookup, fedify webfinger, and fedify nodeinfo, making federated applications more robust and responsive.

@ooheunda addressed a testing infrastructure issue with PR #350, fixing a race condition in PostgreSQL message queue tests that was causing intermittent failures (issue #346). By adding explicit initialization before concurrent message queue listeners, this fix prevents table creation conflicts that were affecting test reliability, ensuring more consistent PR testing for all contributors.

@songbirds provided two test stability improvements with PR #344 and PR #347. The first PR adds skip guards to RedisKvStore tests as a workaround for a known Bun runtime issue, keeping the test suite functional while awaiting an upstream fix. The second PR resolves a race condition in the code generation process by randomizing output filenames, preventing conflicts during parallel test execution. These contributions help maintain a stable testing environment for the project.

Thank you all for your contributions to Fedify. Your work helps make federated social networking more accessible to developers.

#opensource #fedidev #fediverse

We'd like to recognize some excellent contributions from our #OSSCA (Open Source Contribution Academy) participants who have been working on #Fedify.

@gaebalgom contributed PR #339, which introduces the @fedify/elysia package to provide Elysia integration for Fedify. This work addresses issue #286 by creating a plugin that enables developers using #Bun and #Elysia to integrate Fedify's #ActivityPub capabilities into their applications. The contribution includes the core integration module, documentation, examples, and proper monorepo configuration, making Fedify accessible to the Elysia community.

@r4bb1t submitted PR #315, implementing comprehensive AbortSignal support across multiple APIs to resolve issue #51. This contribution adds request cancellation capabilities not only to lookupWebFinger() but also to lookupObject(), DocumentLoader, and the HTTP signature authentication flow (doubleKnock()), allowing developers to properly handle timeouts and abort ongoing requests throughout the entire request chain. The implementation includes extensive test coverage for cancellation scenarios across all affected components and lays the groundwork for adding --timeout options to various CLI commands like fedify lookup, fedify webfinger, and fedify nodeinfo, making federated applications more robust and responsive.

@ooheunda addressed a testing infrastructure issue with PR #350, fixing a race condition in PostgreSQL message queue tests that was causing intermittent failures (issue #346). By adding explicit initialization before concurrent message queue listeners, this fix prevents table creation conflicts that were affecting test reliability, ensuring more consistent PR testing for all contributors.

@songbirds provided two test stability improvements with PR #344 and PR #347. The first PR adds skip guards to RedisKvStore tests as a workaround for a known Bun runtime issue, keeping the test suite functional while awaiting an upstream fix. The second PR resolves a race condition in the code generation process by randomizing output filenames, preventing conflicts during parallel test execution. These contributions help maintain a stable testing environment for the project.

Thank you all for your contributions to Fedify. Your work helps make federated social networking more accessible to developers.

#opensource #fedidev #fediverse

We'd like to recognize some excellent contributions from our #OSSCA (Open Source Contribution Academy) participants who have been working on #Fedify.

@gaebalgom contributed PR #339, which introduces the @fedify/elysia package to provide Elysia integration for Fedify. This work addresses issue #286 by creating a plugin that enables developers using #Bun and #Elysia to integrate Fedify's #ActivityPub capabilities into their applications. The contribution includes the core integration module, documentation, examples, and proper monorepo configuration, making Fedify accessible to the Elysia community.

@r4bb1t submitted PR #315, implementing comprehensive AbortSignal support across multiple APIs to resolve issue #51. This contribution adds request cancellation capabilities not only to lookupWebFinger() but also to lookupObject(), DocumentLoader, and the HTTP signature authentication flow (doubleKnock()), allowing developers to properly handle timeouts and abort ongoing requests throughout the entire request chain. The implementation includes extensive test coverage for cancellation scenarios across all affected components and lays the groundwork for adding --timeout options to various CLI commands like fedify lookup, fedify webfinger, and fedify nodeinfo, making federated applications more robust and responsive.

@ooheunda addressed a testing infrastructure issue with PR #350, fixing a race condition in PostgreSQL message queue tests that was causing intermittent failures (issue #346). By adding explicit initialization before concurrent message queue listeners, this fix prevents table creation conflicts that were affecting test reliability, ensuring more consistent PR testing for all contributors.

@songbirds provided two test stability improvements with PR #344 and PR #347. The first PR adds skip guards to RedisKvStore tests as a workaround for a known Bun runtime issue, keeping the test suite functional while awaiting an upstream fix. The second PR resolves a race condition in the code generation process by randomizing output filenames, preventing conflicts during parallel test execution. These contributions help maintain a stable testing environment for the project.

Thank you all for your contributions to Fedify. Your work helps make federated social networking more accessible to developers.

#opensource #fedidev #fediverse

"The solution isn’t building better platforms — it’s making platforms an obsolete concept. Platforms concentrate power; protocols distribute it. Platforms extract value from users; protocols enable users to create value for themselves. Most importantly: platforms can be captured by bad actors, but protocols resist capture by design."

https://www.techdirt.com/2025/08/05/take-back-our-digital-infrastructure-to-save-democracy/

#Technology#PeopleNotPlatforms#Fediverse#ActivityPub#Bluesky#ATProto#OpenSocial#OpenSocialWeb

#fedidev