After almost a year of hard work implementing ActivityPub support on Lemmy, it is finally done! Anything that works here on dev.lemmy.ml, also works over federation between different instances (with one notable exception, community mods have to be on the same instance as the community for now).
Before we consider federation ready for production, some more testing is needed. And that’s where you come in: go to our test instances enterprise.lemmy.ml, ds9.lemmy.ml and voyager.lemmy.ml, and try things like:
- post, comment and vote
- delete and restore posts/comments
- send private messages
- create communities, remove/restore posts and ban/unban users
- setup your own lemmy instance, and federate with enterprise.lemmy.ml or ds9.lemmy.ml
If you notice any bugs, please report them on Github, as comments on this post, or in our Dev Chat on Matrix. Please keep in mind that our code of conduct also applies to the test instances.
The more you test, the sooner we will feel confident to enable federation on dev.lemmy.ml. Happy testing!
deleted by creator
Or wait, you mean they are completely independent? Of course that works, lemmy.ml isnt referenced anywhere in the federation code. So you can make arbitrary networks between instances.
deleted by creator
Activitypub is a protocol, think of it like HTTP between servers. And then forgot that comparison, because Activitypub runs on top of HTTP and is completely different.
deleted by creator
I have no idea about digitalocean, but in fact we are thinking about offering managed Lemmy instances ourselves in the future.
deleted by creator
My https://fanonwave.ml test instance is digitalocean, I just used the ansible deploy install and it worked great.
deleted by creator
The smallest, I think 500 MB. Lemmy’s super light on resources.
You mean A - B - C with no connection between A and C? I think it should work fine in theory, but no clue how it would go in praxis. Definitely needs testing.
deleted by creator