• 0 Posts
  • 13 Comments
Joined 24 days ago
cake
Cake day: March 4th, 2025

help-circle
  • If an instance decides to not federate with another one they don’t see each other anymore. You can’t subscribe to their communities and vice versa, you don’t see their users posts in third instance communities. From your perspective it stops existing.

    It’s sometimes necessary e.g. if an instance doesn’t do moderation by itself and hoards of trolls are coming from one instance spamming in many communities so you don’t have to ban each of their trolls. It can also be a tool if moderation goals differ too strongly from each other, and some instances have decided to defederate from lemmy.ml and more vocal tankie instances like lemmygrad and hexbear.








  • It is, but it’s not recommended for productive use yet. Quote from their newsletter March 2nd:

    What about self-hosting?

    Several people have asked about using ActivityPub if you’re hosting Ghost elsewhere. Some quick notes about that:

    Importantly, Ghost’s ActivityPub service is already out in the wild, open source, and released under the MIT license. We build in public, and all our work is up on GitHub for anyone to download, fork, run or deploy if they want to.

    What’s missing right now, mainly, is documentation. You could already self-host ActivityPub if you really wanted to, but there’s a lot you’d need to figure out to get it running properly.

    So the question is less “when will it be possible” and more “when will it be easy”?

    At the moment we’re moving quickly and making many breaking changes each week which aren’t backwards compatible (like switching to a new DB) – so the app isn’t stable. Even if we did document everything, if you self-hosted then it would just break constantly — so it doesn’t make much sense for us to try to document and promote self-hosting, because it won’t be a good experience for anyone.

    Right now we’re prioritising developing the app and building features, deployed in a single location, so we can make progress. Once the app is stable, then we’ll start documenting (and optimizing) the process of deploying it and hosting it elsewhere.

    We’re hoping to get to that work some time this summer, and we’ll share details of that here, as we go. Our first priority is just getting ActivityPub working and stable with a base feature set.