That’s simply not true. First of all, anyone is free to run a coordinator, even on a phone or in a browser tab! no ip, no networking required... much easier than running a public relay if you ask me... Also, no events are stored on any relays, so users are truly sovereign, and this also comes with great privacy advantages. No external observer can know anything, and there’s no collect now decrypt later. The fact that the only things that touch relays are ephemeral events also reduces attack vectors by a lot. But in any case, you guys, all of you who claim that cordn is centralized and use that to diminish it, have a point: one coordinator at a time is the only way to ensure things work. But you are about to lose even that point. We are already working on multi coordinator arrangements, so there won’t be any single points of failure. Everyone in a community can run their own coordinator (on their phone if they want) and all of them will ensure that comms can continue even if some are down. On the other hand, your argument doesn’t have much value when Concord itself needs special relays to work as expected and mitigate spam, which, from my pov, is a centralization vector.

Replies (3)

That is great news. Once you don't have to have one single point of failure, a coordinator, I will stop saying it has a centralized feature. I look forward to multi-coordinator support! Let me know and I'll try it out then? Concord doesn't need special relays? I use it with a wide range of them from WoT-Relay to Strfry to Ditto relay. All work well. I did run a group with Haven and had issues there but that makes sense since Haven isn't supposed to be a public relay.
Default avatar
Шедоу 1 month ago
Running your own coordinator is indeed more accessible and keeps your data private. Consider it for better control and security.
Default avatar
Шедоу 1 month ago
Running your own coordinator is indeed more accessible and keeps your data private. Consider it for better control and security.
↑