Clarion vs Federated Systems (e.g. Matrix, Mastodon, Diaspora) #12
Replies: 6 comments 11 replies
-
Users can access their "email" directly from a smartphone to connect to other users' nodes, and send/receive forward messages. But this still requires the existence of nodes/users that manage a server, or am I wrong? |
Beta Was this translation helpful? Give feedback.
-
your data is hosted by your friends' node and yourself, only all node are lost, your data will be lost, all your data is private, and if you want to send some data to your friends or public, you use your friends' public key or a group key to encrypt it, like keybase |
Beta Was this translation helpful? Give feedback.
-
This sounds the same as Nostr. They share the same criticism for federation and accounts work the user relays - any user can use many relays, and relays don't own the account as they do in federation-based networks. |
Beta Was this translation helpful? Give feedback.
-
Did you check https://scuttlebutt.nz/ ?
|
Beta Was this translation helpful? Give feedback.
-
Matrix's Pinecone is a hybrid of a federated system and p2p communication and collaboration network. (https://matrix.org/blog/2021/05/06/introducing-the-pinecone-overlay-network) |
Beta Was this translation helpful? Give feedback.
-
The ZOT protocol servers are interesting as they allow channel cloning and multiple home servers for the same identity. Zap, Hubzilla, Mistypark, etc. That deals with some of the concerns. Clarion looks really interesting. Is there provision for multi-homing an identity in Clarion? Or is identity tied to the device/instance? |
Beta Was this translation helpful? Give feedback.
-
There are a lot of "decentralized" social media systems that utilize a Federated Model. From what I can deduce from reading the documentation these include Mastodon and Diaspora.
In a federated system a "user" has a "home server" (or hub) and hubs are connected together. These "servers" or "hubs" are small in number because of the technical skills required to operate a full node.
The most widely known example of a Federated System is email. You can have an [email protected] and an [email protected], but these are two different accounts. Your ability to utilize your email account is subject to the email service provider you have chosen. These service providers are in turn subject to all manner of regulation and/or cancel culture pressure.
Under Clarion "email", you would have an account identified by a public key. This single account could be hosted on many different nodes at the same time Red.com and Blue.com and Friend.com and Family.com as well as YourHomeComputerIP.
Someone who wants to send you an email can deliver it to any node operated by a friend of yours. And even if you lose all of your friends, you can still make new friends and retain your Clarion "email" account.
The goal with Clarion is to make it so easy to "admin" a node that most people don't even realize they are doing admin or running a server. You just download an application, run it, and create or import an account, and then invite friends.
Beta Was this translation helpful? Give feedback.
All reactions