this post was submitted on 08 Aug 2023
167 points (97.2% liked)
Asklemmy
43989 readers
1328 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
As I understand it, there's a huge downside to federated software in the requirement to be Always Online. Lots of people have slow internet connections, or no connection at all, preventing them from accessing their software. Everyone should be able to use the programs/apps they have without regard to whether they are online or can get online.
What federated software would actually make sense to work offline, though? Everything I've seen is literally internet tools like social media (forums, blogs, chats, etc). None of those things would work offline.
This isn’t really specific to federated software. The client can go offline but the server can’t. Same applies to all centralized services. The only place this really applies is for decentralized (as in, no central points) systems, and those tend to have a lot of special sauce to make other people being offline less painful