Draft of basic info about federationToday's tea: HōjichaSome of us have been discussing different types of documentation for (streams) and Forte, and I'm planning to write some "How To" mini-tutorials for new users. But I realized that I can't write
Chapter 2: How To Comment without explaining the differences between our systems and Mastodon, which means explaining federation.
Anyway, here is my draft of a beginners' introduction to federation. Improvements and corrrections are requested.
Using your account on a Forte/Streams-based service, you can connect with people on thousands of other independently-operated services. This is called "federation". (Hence the word
Fediverse, a vaguely-defined universe of federated services.) A single independently-operated system is called an
instance, and may have any number of users.
Traditional social networking services (Facebook, X, internet forums, etc) are centralized, not federated. One entity, a giant corporation or something smaller, keeps all of your posts, user information, images, etc on one or more computers that are under its own control. You can't send your Facebook posts to followers on X, and you can't comment on a Reddit discussion from your YouTube account.
In contrast, consider e-mail. There are many independently-operated e-mail providers, but they have all agreed on one communications protocol for sharing data. So you can send mail from your GMail account to your friend's Outlook account, or to your bank's customer service account on its corporate e-mail server.
Federated social networks are somewhere in-between. Thousands of independent instances have agreed to exchange information via standard communications protocols. So you
can send your posts from an account on a Facebook-like service (such as Forte and Streams) to your followers on an X-like service (such as Mastodon and Akkoma).
These thousands of independent instances can be running any of
dozens of platforms which can be very different from each other. And this is why the Fediverse can never exchange information as smoothly as e-mail: these platforms are specialized for different purposes.
For example, Pixelfed is a replacement for Instagram. You can connect to a Pixelfed user from your Forte/Streams instance, and you can receive and comment on their photos. But the Pixelfed user will not see
your posts unless they contain at least one photo, because Pixelfed is built to ignore text-only posts.
Here's another example that is more subtle. Facebook users expect that if they post and start a conversation, they
own that conversation. The owner controls who can see the conversation. Nobody can reply without the owner's permission. Everyone who has permission to see the conversation can also see all the replies. And this (minus Meta's spying) is how we handle conversations with Forte and Streams and a few other Fediverse platforms.
Mastodon and most other X-like Fediverse platforms don't work this way. Nobody owns anything, anybody can read anything, anybody can reply to anything, nobody is assembling the replies into a coherent conversation, and nobody will automatically forward
your reply to all the other participants. Mastodon users tolerate this and seem to enjoy it. We can communicate with them from Forte/Streams, if we comply with the requirements of their very different system.
Technical differences across the Fediverse have given birth to very different social environments and specializations. So if you don't mind the extra effort, you can get a lot of variety via federation. But if you prefer, Forte and Streams give you the tools to ignore almost anything that you find annoying.
