A home for discussion of Lemmy apps and tools for all platforms.
RULES:
An extensive list of Lemmy apps is available here:
Visit our partner Communities!
Lemmy Plugins and Userscripts is a great place to enhance the Lemmy browsing experience. [email protected]
Lemmy Integrations is a community about all integrations with the lemmy API. Bots, Scripts, New Apps, etc. [email protected]
Lemmy Bots and Tools is a place to discuss and show off bots, tools, front ends, etc. you’re making that relate to lemmy. [email protected]
Lemmy App Development is a place for Lemmy builders to chat about building apps, clients, tools and bots for the Lemmy platform. [email protected]
What?
I don't understand what you mean.
I'm looking at a post in a community from lemmy.world from a user of spouli.xyz in my instance lemmy.pe1uca.dev from jerboa.
All lemmy clients can federated content from multiple instances because lemmy can federated content from multiple instances.
The question seems like a misuse of the word 'federate'.
In this context it probably is, since the federation that is done on the fediverse is something else entirely. "Collate" might be a better word, perhaps.
Liftoff allows you to specifically choose the instance you see the content from.
It can be useful when sometimes one of the instances will have older posts while another would not.
I didn't mean federate in the Lemmy/Fediverse sense, but rather in the collation/multireddit sense. In other words, gathering posts from many different sources, in this case instances, and displaying them as a single list. Given the context, calling this "federation" was probably very confusing, and definitely a poor choice of words. I apologize for that.
In Liftoff, this takes the form of an All/Everything view (where "All" means all currently logged in instances) which collates and displays posts from many different Lemmy instances at once. This is the feature I was looking for in other clients.
Liftoff is the only one with its "view from another instance feature" AFAIK
I assume this is not frequently implemented because it's a nuisance (from a developer's point of view) if you centralized all API requests in a shared component, since you have to point to another base URL on the fly. I am developing a small "toy" client myself and I implemented this feature because I wanted to explore all (and only) the communities on a given instance to list them and access their posts. But subscribing to a community from another instance is more difficult. Since it's not a highly requested feature, maybe many projects prefer to focus on other features.