The ecosystem is moving ... away from corporate centralization and mindsets. Billionaires are out, federated and multi-player systems are in, if we gather the many chats, gossips and happenings around #fosdem correctly. Dispersing ourselves around Bruxelles the last couple of days was very enjoyable (thanks Sun!) and helpful to orient in convivial directions in this otherwise extraordinarily stupid 2025 timeline ... thanks to the many people we enjoyed conversations and hang outs with! ❤️
@mostafa228 Federation is not just a technical but also a social direction: different groups can have have different policies yet federate .... The #fediverse and activity pub also provide an upgrade protocol for lifting existing media platforms into the fediverse. There is a lot out there already and you can't rewrite it all.
@8petros This picture is appearing here and there all the time, but what is drawn above the "distributed" label is a mesh network topology and does not describe the type of service running on top.
@mostafa228 mentioned Nostr and Delta Chat already moves in this direction. Chatmail servers are used to create mailboxes, but user identity is their key, not the email address.
@mostafa228 And with details we'll be able to ask higher level info security questions. Also let's comment, how on level of details, delta manages to have chat like aspects, while delivery/high-level-transport isn't aware, unlike say Matrix. In classical federation transport and metadata-rich aspects are mixed. Delta shows how it can be different. Details are revealing. Details, please.
@mikalai @mostafa228 it's indeed a good question how #deltachat avoids storing group metadata on servers. The answer is it implements a P2P group membership model (briar often described as a P2P messenger does have a centralized group membership model btw) . Here is technical documentation about our TLA+ modeling github.com/chatmail/specs/blob… a complementary python simulation model github.com/chatmail/specs/tree… and the just merged rust implementation rolling out in releases github.com/deltachat/deltachat…
Δж➂
in reply to Delta Chat • • •Delta Chat
in reply to Δж➂ • • •treefit
in reply to Delta Chat • • •FOSDEM - video recordings
video.fosdem.orgMostafa228
in reply to Delta Chat • • •Delta Chat
in reply to Mostafa228 • • •Mostafa228
in reply to Delta Chat • • •Mostafa228
in reply to Delta Chat • • •8Petros [$ rm -rv /capitalism/*]
in reply to Mostafa228 • •l
in reply to 8Petros [$ rm -rv /capitalism/*] • • •@8petros
This picture is appearing here and there all the time, but what is drawn above the "distributed" label is a mesh network topology and does not describe the type of service running on top.
@mostafa228 mentioned Nostr and Delta Chat already moves in this direction. Chatmail servers are used to create mailboxes, but user identity is their key, not the email address.
@delta
8Petros [$ rm -rv /capitalism/*]
in reply to l • •Mikalai
in reply to Mostafa228 • • •And with details we'll be able to ask higher level info security questions.
Also let's comment, how on level of details, delta manages to have chat like aspects, while delivery/high-level-transport isn't aware, unlike say Matrix. In classical federation transport and metadata-rich aspects are mixed. Delta shows how it can be different.
Details are revealing. Details, please.
Delta Chat
in reply to Mikalai • • •specs/group-membership/README.md at main · chatmail/specs
GitHub