- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
cross-posted from: https://lemmy.world/post/169206
Wouldn’t it be better to merge than to compete?
Edit: Looks like the community on lemmy.ml
is pretty much dead.
cross-posted from: https://lemmy.world/post/169206
Wouldn’t it be better to merge than to compete?
Edit: Looks like the community on lemmy.ml
is pretty much dead.
[email protected] is pretty dead, but I don’t see why [email protected] and [email protected] couldn’t co-exist. They are even on two different platforms.
Well, I’m currently subscribed to all 3 and since federation now works with kbin.social I can access their GW2 community just like it were on a native lemmy instance. Which is pretty cool.
It is, until federation breaks again (hopefully not) :P
I’m subscribed to the ml as well as kbin and have accounts in both but I can’t seem to view posts from the ml there alongside the kbin ones. I can see that the ml is linked and I can subscribe to it, but how do I get the kbin to show a merger of both?
Also shouldn’t we link the wtf instance too in the kbin?
Usually you don’t need accounts on other instances to interact with their communities, e. g. my account is on lemmy.world, but I’m subscribed to 3 GW2 communities on 3 different instances one of which even being a different platform (
kbin
and notlemmy
).These communities now appear as if they were on my instance, but are in fact local copies which are synchronized/federated using the
ActivityPub
protocol.Note that these communities are not merged, i .e. they still appear as separate communities, but there is a (pretty popular) feature request for this on
GitHub
.Support for grouping communities / multi-communities #818
I don’t know whether federation from
lemmy
tokbin
is currently supported. I’m only using the other direction.Thanks for the answer and the link ! That makes sense, then I’ll wait and see if there is some traction/progress on the GitHub post!
I thought that going to https://www.lemmy.world/c/[email protected][email protected] would work but that’s the whole point of the request