flan (@flan@bonito.cafe)
El futuro del #fediverso será #holos, o no será
Show Original Post
apps (@apps@toot.fedilab.app)
#Holos will be available on #FDroid soon, and we hope to get more feedback to improve the project. While #Fedilab uses server APIs, here we can do much more to improve your #Fediverse experience with an #ActivityPub server running directly on your device. We already introduced E2EE DMs and personal identity. We will go further with automatic deletion, even at posting level. You decide the availability of a message. We will also work on interaction controls from #GoToSocial.
Show Original Post
r (@r@fed.brid.gy)
Oh what a shame 😁 Why anyone is still on there is frankly perplexing, everyone should join the open social web it's awesome! #ATmosphere #atproto #activitypub
X briefly hit by 'internationa...
Show Original Post
r (@r@fed.brid.gy)
This is cool, a post from Mastodon on Bluesky/atproto in the ATmosphere via @surf.social@bsky.brid.gy got to love the open social web! #ATmosphere #atproto #activitypub
RE: https://bsky.app/profile/did:plc:2ldddqzgrab5by6r255zwszf/post/3meyq4fmi3vu2
Show Original Post
marcpires (@marcpires@mastodon.social)
Bem interessante os encontros do Bolha.us sobre ActivityPub.
https://bolha.tube/w/ePRfzoLrRbnB2PMHfj6Tgb
Show Original Post
radwebhosting (@radwebhosting@mastodon.social)
Deploy #Castopod on #AlmaLinux #VPS
This article provides a production-ready, step-by-step guide to deploy Castopod on AlmaLinux VPS using Nginx + PHP-FPM + MariaDB + HTTPS.
What is Castopod?
Castopod is an open-source #podcast hosting platform designed to give podcasters control over their content while supporting the latest podcasting innovations, such as ...
Continued 👉 https://blog.radwebhosting.com/deploy-castopod-on-almalinux-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #podcasthosting #opensource #fediverse #selfhosting #letsencrypt #selfhosted #activitypub
Show Original Post
archives (@archives@neon-blue-demon-wyrm.x10.network)
ActivityPub Server’s Custom Reply‑Control Extensions Undermine Federation
It seems like Activitbypub developers are extending ActivityPub with optional metadata to fix a lot of its issues, but that is still problematic. Trying to add moderation tools and user control to threads seems to be the ongoing battle. I am fascinated by dumpster fires, so I’ve started looking at the ActivityPub protocol in detail. I tend to become fascinated with things that are going down in flames.
As a brief recap of the problem:
So, one of the very popular features on Bluesky—also popular on Twitter—is the ability to select who can reply to a post. A major issue in the Fediverse is the inability to decide who can reply, and once you block someone, their harassing reply is still there. I honestly thought it was simply a case of them choosing not to add or address it for cultural reasons. What is clear from that thread is that they were always aware that the ActivityPub protocol and most Fediverse implementations don’t provide a universal way to control reply visibility or enforce blocks across instances.
An ActivityPub server that has reply control is GoToSocial. ActivityPub, as defined by the W3C specification, standardizes how servers federate activities. It defines actors, inboxes, outboxes, and activity types (Create, Follow, Like, Announce, etc.) expressed using ActivityStreams 2.0. It also specifies delivery mechanics (including how a Create activity reaches another server’s inbox) and how collections behave.
The specification does not include interaction policy semantics such as “only followers may reply” or “replies require manual approval.” There is no field in the normative vocabulary requiring conforming servers to enforce reply permissions. That category of rule is outside the protocol’s defined contract.
GoToSocial implements reply controls through what it calls interaction policies. These appear as additional properties on ActivityStreams objects using a custom JSON-LD namespace controlled by the GoToSocial project.
JSON-LD permits additional namespaced terms. This means the document remains structurally valid ActivityStreams and federates normally. The meaning of those custom fields, however, comes from GoToSocial’s own documentation and implementation. Other servers can ignore them without violating ActivityPub because they are not part of the interoperable core vocabulary.
Enforcement occurs locally. When a remote server sends a reply—a Create activity whose object references another via inReplyTo—ActivityPub governs delivery, not acceptance criteria. Whether the receiving server checks a reply policy, rejects the activity, queues it, or displays it is determined in the server’s inbox-processing code. The decision to accept, display, or require approval happens after successful protocol-level delivery. This behavior belongs to the application layer.
These are server-side features layered on top of ActivityPub’s transport and data model that are not actually part of ActivityPub. The protocol ensures standardized delivery of activities; however, the server implementation defines additional constraints and user-facing behavior. Two GoToSocial instances may both recognize and act on the same extension fields. However, a different implementation, such as Mastodon, has no obligation under the specification to interpret or enforce GoToSocial’s interactionPolicy properties. These fields function as extension metadata rather than protocol requirements.
The semantics of GoToSocial are not part of the specification’s defined vocabulary and processing rules for ActivityPub. They no longer operate purely at the protocol layer; it has become an application-layer contract implemented by specific servers. Essentially, it’s an API. To put it concisely: the developers are no longer developing ActivityPub—they’re developing their own APIs. This is a mess!
Let’s use the AT Protocol as an example. Bluesky’s direct messages (DMs) are not currently part of the AT Protocol (ATProto). The AT Protocol has nothing that specifies anything for DMs, so DMs are not part of the AT Protocol. The AT Protocol was designed to handle public social interactions, but it does not define private or encrypted messaging. Bluesky implemented DMs at the application level, outside of the core protocol. DMs are centralized and stored on Bluesky’s servers. What is happening with servers like GoToSocial is sort of like that. The difference is that the AT Protocol was designed for different app views; ActivityPub was not.
The issue is the divergence in semantic interpretation that emerges at the interpretation layer. ActivityPub standardizes message delivery and defines common activity types. However, it leaves extension semantics and application-layer policy decisions to individual implementations. Servers may introduce custom JSON-LD namespaces and enforce local behaviors, such as reply restrictions, while remaining protocol-compliant. But, the noise created by divergences are problematic, because it creates unexpected, unintended, and unpredictable behavior.
Divergence appears when implementations rely on non-normative metadata and assume reciprocal handling to preserve a consistent user experience. Behavioral alignment then varies. Syntactic exchange succeeds, but behavioral consistency is not guaranteed. Though instances continue to federate at the transport level, policy semantics and processing logic differ across deployments. Those differences produce inconsistent experiences and results between implementations.
That leads to fragmentation, specifically semantic or behavioral fragmentation and an inconsistent user experiences. ActivityPub ensures syntactic interoperability, but semantic interoperability (everyone interprets and enforces rules the same way) varies. This creates a system that is federated at the transport level yet fragmented in behavior and expectations across implementations. It is funny how the thing that the fediverse touted has made the entire thing very brittle. ActivityPub technically federates correctly, but semantically falls apart once servers start adding their own behavioral rules.
Show Original Post
FinchHaven (@FinchHaven@sfba.social)
Clicked through on that link for some reason
"The spec is ActivityPub, but federation is unfortunately Mastodon."
No
#ActivityPub is a protocol
It requires some sort of implementation in some sort of distribution/app
Mastodon (for one) is only *one* distribution/app
There are others
These others may or may not "federate" with each to varying degrees
They are all *different* and "varying" implementations of ActivityPub
I don't know why this is so hard to understand, but it sure seems to be...
Show Original Post
pub (@pub@btfree.social)
Fireside Fedi 75** **- Late‑Night Fireside: Joe Ressington Unpacks the Future of Decentralized Social
Special thank you to @joeress@mastodon.social ** **!
🚀 **Watch the full VOD:** tubefree.org/w/bRS7fTJfUQYSo...
🔎 **Explore more episodes:** tubefree.org/a/ozoned/video-channels
🔔 Subscribe to the RSS feed so you never miss a future deep‑dive.
📡 **Subscribe via RSS:** tubefree.org/feeds/videos.xml?videoChannelId=5934
🎧 **Podcast feed:** tubefree.org/feeds/podcast/videos.xml?videoChannelId=5934
#FiresideFedi #FiresideChat #Podcast #VideoPodcast #Fediverse #Fedi #ActivityPub #BSKY #DecentralizedSocial #OpenSocialWeb #Community #TechCulture #FutureOfSocial #TechTalk #DevCommunity #CodingFun
Show Original Post
spla (@spla@mastodont.cat)
El meu entorn de desenvolupament del codi d'appy. Absolutament tot el codi l'he programat amb #Vim 
Qui necessita un #IDE quan tens Vim?
#appy #Python #fastAPI #ActivityPub
Show Original Post
pablopernot (@pablopernot@toot.portes-imaginaire.org)
ça y est ça arrive doucement @pablo-pernot #ponos #activitypub
Show Original Post
smallcircles (@smallcircles@social.coop)
PS. I track a list of #ActivityPub #C2S implementations and didn't add #Holos till now. If I should add it, pleas let me know, or comment directly to the issue.
https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130
Show Original Post