Besao

Cooking 🍳

Wanna chat? https://cordn.net/p/besao

Public Key

npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

NIP-05 Address

Profile Code

nprofile1qqsqvrswzdwm6at2szucdykfqfytdpkk24vxcvvfetjr2zeg6flw30spz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds9g6a0k

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

Show more details

Last Notes

2026-08-29 16:25:33 CEST

https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/76468b786ee96de4828756142991e034ace1813fc12113914777ae8ac883bc52.jpg
#nevent1q…y45e

2026-08-18 19:56:01 CEST

Wooop woop!!
#nevent1q…a55g

2026-08-11 17:59:38 CEST

- reply

Yes, Cordn is designed the way it is to allow exactly this: a leader or preferred coordinator per group that keeps everything in order and avoids races that might occur when multiple sources have competing or out‑of‑order commits. It isn’t implemented yet, but it will be, we haven’t put much work into it so far because it’s an advanced feature that only power users will need, and we wanted to polish the UI/UX first. It will definitely come. But make it work reliable and have a good UX semeed what users request the most

2026-08-10 19:44:57 CEST

- reply

Thanks guys!

2026-08-06 18:15:15 CEST

- reply

Thanks :) so do you want one?

2026-08-05 13:02:37 CEST

- reply

It is just a nip05 at cordn.net. Anyone can already just use their nip05 (e.g https://cordn.net/p/[email protected] ) but if you have one at cordn.net or the host where the app is living it will try to resolve from the host domain, that's why you can have a name without the nip05 domain part

2026-08-05 11:08:37 CEST

Who wants a Cordn name like https://cordn.net/p/besao ? So you can easily share it with people and start chatting 🔑

2026-07-27 18:44:18 CEST

Yo guys, exciting news. We ported the Cordn coordinator to rust. Now it is easier to run than ever, lighter, much more efficient, it can run in arm64 too, so you can just grab your pi be up in seconds. Hope you enjoy :)
#nevent1q…qmh0

2026-07-27 13:05:01 CEST

- reply

Thank you guys!

2026-07-26 23:34:15 CEST

- reply

Great article! really interesting

2026-07-24 19:18:33 CEST

Let's go!! Wanna chat? https://cordn.net/p/besao
#nevent1q…k73v

2026-07-24 17:16:01 CEST

- reply

Indeed. Will ship this in the next patch

2026-07-24 00:25:18 CEST

- reply

Yes, MLS is very complex to implement in a "decentralized" way. The bet we’re making is to make coordinators very easy to run and switch, just one at a time to avoid out of order messages, that’s the rule. For example, @npub1uac…99rx made a coordinator that can run in a browser tab, and it worked reasonably well even in its early version.#nevent1q…gwkn

2026-07-24 00:13:58 CEST

- reply

It is MLS, just transported differently. It uses coordinators, which are just as dumb, or even dumber than, relays these days, for the ordering of messages (MLS requires strong ordering, which is why Marmot struggles so hard to work properly). Nostr relays transport messages between coordinators and clients using CVM, so everything is ephemeral on relays. It uses Nostr keys for identities, just like Marmot.
Cordn and Marmot are not compatible (though they could be), since MLS is such a complex protocol. Given their different requirements, they would need to agree on certain parts that they currently don’t. Happy to keep clearing doubts any time. The @npub1gzu…a5ds article explains this very accurately.

2026-07-24 00:08:24 CEST

- reply

Sure

2026-07-23 21:04:26 CEST

- reply

I don't know why they hate us so much. Grassroots vs VC backed I supposed :/

2026-07-23 21:03:42 CEST

- reply

Why you guys hate us so much?

2026-07-23 19:41:42 CEST

- reply

@npub10xv…g437 @npub1m4n…c2jl @npub1l5s…gx9z @npub1ncf…j87x

2026-07-23 19:40:46 CEST

Boom! This is out! Fresh out of the oven. Publishing on @npub10r8…t2p8 has been a breeze so far.
#nevent1q…2z6n

2026-07-23 18:37:58 CEST

The Android app is coming out very soon 🔥🔥🔥 and in honor of that, we’ve created the official Cordn account. So far, we’ve been managing everything through this profile, but it’s time to move forward. Follow it for news and stay up to date about what’s coming for truly private messaging over Nostr.
#nevent1q…fue8

2026-07-23 12:14:21 CEST

Multiple Media Uploads: Send a whole batch at once. 📎
Some users requested the ability to upload multiple files at once, previously, you could only send one at a time. Now, you can select multiple photos or files and send them together. You’ll also see real-time progress, so you’ll know when a large file is being transferred, and you can cancel the upload with one tap if you change your mind. As always, everything remains end-to-end encrypted.
And for Android users waiting in the wings: a native Cordn app is just around the corner. 👀

2026-07-20 19:21:52 CEST

- reply

Yes, but fyi android native app is around the corner, probably this week or early next week, and it'll bundle nip 55 login with amber :)

2026-07-20 09:40:49 CEST

- reply

No, we considered using Unified Push, but it has two important tradeoffs. Users would need to install a third-party app to receive notifications, and someone would also need to run a server for notifications. We explored modifying the coordinator to add notification capabilities, but that wasn’t acceptable because it would violate the "dumb coordinator" constraint. So, we opted for the most straightforward solution: a worker that fetches messages from the coordinator at a specific frequency.
This approach is quite efficient because it involves a single API call (no subscriptions), and it only wakes the radio periodically. By default, we set the interval to 5 minutes, but users can configure it to 1 or 10 minutes. There’s also another option that doesn’t require persistent notifications but runs on a ~15-minute interval, this is the most reliable and battery lightweight mode. The faster options can be terminated in some phones.
In our testing, we’ve found it to be quite reliable. Even at the fastest interval of 1 minute, battery performance remains good. So far, it sits next to a signal with similar battery drain.

2026-07-19 15:25:15 CEST

We’re already working on the native Cordn app for Android. This feels like the next logical step after the multi-device release we recently launched. It’s already shaping up well, we have a very alpha version in internal testing, with native notifications working without third-party push notification servers or anything similar. It’s very private and efficient, with good battery performance so far. This is going to be lit!🔥🔥🔥
We’ll likely have a solid version ready by next week, which we will release on @npub10r8…t2p8 Looking forward to it!

2026-07-18 15:50:21 CEST

Join our cordn channel! https://cordn.net/chat/dfa7475d-c9ef-46df-bf85-1f481fdcf2c4?m=eyJuYW1lIjoiQ29yZG4gRGV2IiwiaWNvbiI6IvCfqqIifQ
#nevent1q…rcyu

2026-07-17 11:30:54 CEST

- reply

And the spirit of things. We would like to keep pushing organically. Let's see how it goes :)

2026-07-17 11:10:21 CEST

Cordn doesn’t have any funding, no VC money, no grants, like other projects do. Cordn doesn’t have a big team, nor an organization or a director behind it. We’re building Cordn as a service for the community and for ourselves because we believe that truly private, permissionless, secure, and accessible communications is a fundamental human right that we must defend in these darker times.
We’re pushing as hard as we can to make this a reality, so you don’t have to bend over when things get darker. In short, to be free.
This is a grassroots movement, and the people building it are doing so for the sake of making this a reality, to have a real alternative, totally voluntarily. This is a community project. So, if you like what we’re building, please consider contributing in any way you can, whether by testing, providing feedback, creating content, or sending us some zaps. Everything is welcome and helps us keep pushing and growing this.
#nevent1q…m6e3

2026-07-16 20:38:34 CEST

- reply

Good question. There are actually two ratchets in MLS and we handle them differently.
For application messages, we don't coordinate generation picks across devices. We let them race. The delivery stream carries the generation in the clear, so when one device sends at gen N, the other sees it and advances its own counter past N. Self-echoes we match by ciphertext bytes (not leaf index), so a device knows if a "self" message was its own send or a sibling's, and advances accordingly. For the rare case where two devices grab the same N in the same instant, the RFC 9420 reuse guard adds fresh randomness to the nonce so the key/nonce pair stays distinct. That guard exists in single-device MLS anyway, so we get it for free. No fighting, no extra sync.
Commits are the part that can't be shared over the stream. A Commit refreshes the leaf with new keys, and only the committer gets the private half. A sibling trying to ingest it would mark itself removed. So we detect sibling Commits (sender leaf index equals ours), skip them, and the committing device republishes its full state on Blossom for the others to fast-forward from.
App messages ride the stream because their keys are derivable from the shared epoch secret. Commits can't, because the new leaf keys only exist on the committer.

2026-07-16 17:53:20 CEST

- reply

Yes! We think so. Please share any feedback if you test it. The next things are the enhancements you proposed these past few days

2026-07-16 17:52:18 CEST

- reply

They share the same leaf node. The cool part is totally opt-in, you can keep using the manual multi-leaf-node approach that the RFC provides, or use this one, which is basically a mesh sync using Blossom and Nostr relays. Everything is in the spec if you're interested :)

2026-07-16 17:29:41 CEST

If you want to use it, go to Config > Multi-device and click the Sync & Generate button. Then, open Cordn on another device, log in with your account, and scan or paste the generated string. From there, you don’t need to worry about anything else.
#nevent1q…z3pt

2026-07-16 17:25:59 CEST

- reply

cc @npub10xv…g437 @npub1l5s…gx9z @npub1klk…x3vt

2026-07-16 17:24:27 CEST

Multi-device is here 💻📱💻
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/8f284485229315734b29af897fb8250825eda56fc2b1de0ff4abff39b86948c9.png
There's an expectation so basic it barely feels worth saying: if you join a group on your laptop, it should be on your phone too. Your account, your groups, on whatever device you're holding.
Until now, Cordn couldn't do that, and getting there took real engineering (and almost 2 weeks of work). This is one of the largest changes Cordn has shipped, because the obvious-sounding behavior required a genuinely non-obvious design.
The hard part is that MLS, the encryption protocol Cordn groups run on, doesn't hand you multi-device for free. There are two honest ways to add a device, and they pull in opposite directions.
The way the standard envisions makes each device its own member of the group, with its own keys and its own state. That's a legitimate model with real virtues: you can revoke a single device, and one compromised device doesn't compromise the others. It also has real costs: adding a device means an explicit invite every time, if you join a group you need to invite all your devices, and the group's membership structure reveals how many devices you run. In practice, people who wanted multi-device today were already doing a rough version of this by hand. They'd create a second account on the new device and add it to the group as a separate member.
We went the other way. Your devices share one identity inside every group. One set of keys, one membership, the same state replicated across all of them. Link a device once with a connection string, and from then on:
- A group you join or create on one device appears on the others, automatically.
- Remove a group from your list, and it's gone everywhere.
- Nothing to invite, nothing to babysit.
Because every device is the same member, the group can't tell how many you're running either, so your hardware footprint stays yours.
Under the hood this required solving a stack of genuinely hard problems: how devices reconcile state, how offline catch-up recovers messages without losing them, how deletions stick across the fleet, what happens when two devices act at once. The good news is you don't have to think about any of it. Turn on sync, link your devices, and the complexity stays out of sight.
This isn't free, and we want to be straight about the trade. Sharing the same state across devices means we give up per-device security. But the catastrophic case is losing your account key and your connection string together, but even then MLS's forward secrecy and post-compromise security still hold, rekeying/rotating the string recovers you, and no one else in your groups is affected.
Importantly, this doesn't replace the standard approach. It's an alternative, and both are legitimate. The RFC's per-device model gives you security properties ours trades away; ours gives you seamless sync and a hidden device count it structurally can't. Multi-device is entirely opt-in: nothing changes unless you explicitly turn it on and link devices. If you prefer the manual, per-device way, you can keep right on doing it. Nothing is forced on you.
We worked hard to catch the edge cases, and it's mature enough to depend on. But it's new, so treat it as experimental, and if you hit a bug, tell us.
The full design (every decision, every tradeoff, every invariant) is in the spec: https://github.com/Cordn-msg/cordn/blob/master/spec/applications/multi-device.md
We wrote it to be read.

2026-07-16 16:36:25 CEST

- reply

Actually is less overhead. MLS (Cordn) uses a tree-based group key agreement called TreeKEM to manage group state. In a balanced tree, join/leave/rotation operations touch only O(log n) nodes, so very large groups can handle rekeys (including member bans and key rotations) much more efficiently than protocols that re-encrypt or re-establish keys for all n members, such as Double Ratchet–based or naive custom group protocols, which are O(n) per rekey.
https://i.kym-cdn.com/photos/images/original/001/191/035/135.png

2026-07-16 16:10:42 CEST

- reply

GM!

2026-07-16 10:36:32 CEST

GM nostr! Today we'll release multi device feature, and it will be smooth af, automatic sync between devices, 0 babysiting. Stay tuned 🚀

2026-07-15 13:03:25 CEST

- reply

GM!

2026-07-14 10:30:47 CEST

Quietly working on the next big leap for Cordn. Stay tuned, lads.

2026-07-08 20:02:17 CEST

- reply

I type a lot already hahaha

2026-07-08 18:31:52 CEST

- reply

You can just create a new issue and paste the copy there so we can work over there. Is that or anyother way we can share the copy in text. Much easier for me to integrate it in the website than from an image

2026-07-08 16:51:50 CEST

New cordn coordinator 0.4.0 is here!
This release completes the rollout of sealed message delivery, every group message is now sent sealed by default, so hardened group privacy delivery is the standard rather than an opt-in. It was already since a couple of weeks ago, now all the legacy code in the coordinator have been removed.
We also fixed a bug where the streams that push messages out to clients (our writers) could keep running after a client disappeared without a clean goodbye. Left unchecked, those leftovers would gradually slow the server down over days of use. Writers now notice silent drop-offs and clean up on their own.
Thanks to everyone who's been testing along the way keep the feedback coming!

2026-07-08 10:13:37 CEST

Great pod! Also, Cordn received a shoutout here. Really appreciate it! 🎇 We will continue building, so hopefully more people and merchants can have a great experience with private comms over Nostr
#nevent1q…ms2a

2026-07-08 10:06:12 CEST

- reply

Yes, I agree, the copy on the site is too technical. We need a better way to communicate Cordn’s value proposition in simpler terms. If you have any suggestions, please share them.
If you’re comfortable with GitHub, we can collaborate there, you could open an issue with proposals or even submit your own pull request. I’d be happy to review it!
https://github.com/Cordn-msg/cordn-web
But if you’d prefer to share ideas here, that works too :)

2026-07-07 23:48:15 CEST

- reply

It will come. One think at time, we are a veeery small team pushing as hard as we can. A native app is around the cordner ;)

2026-07-07 23:47:01 CEST

- reply

Just send me a msg https://cordn.net/p/npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

2026-07-07 23:46:22 CEST

- reply

Yes, cordn is very signer friendly indeed.

2026-07-07 19:33:49 CEST

- reply

What do you think? Already live!
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/5e3db678bc10dfeb0c2bbdc6e143db850c5e9cd4601ec4e30191487601a1c371.png

2026-07-07 19:13:20 CEST

- reply

Man that would be amazing! 💛

2026-07-07 10:40:47 CEST

- reply

Oh, thank you so much! I like it. I’ll definitely update the landing page. Please keep the feedback coming! :)

2026-07-06 20:17:45 CEST

- reply

I think you are clearing all or using multiple devices. Currently if you clear everything you start over. And multi device support is coming

2026-07-06 10:02:21 CEST

- reply

No error, nothing? I've messaged you there 👌

2026-07-04 18:41:40 CEST

Multi-device support is coming along nicely. We already have it working in our dev branch, and feels like magic ✨ We're still polishing it, but we're confident we'll have it ready by next week!
#nevent1q…k3d5

2026-07-04 11:21:53 CEST

- reply

Oh yes, indeed! This is built on top of MLS (an emerging internet standard) and presents some UI/UX challenges. I’d love for you to try cordn.net and share your thoughts. We’ve done our best to create a good and consistent UI/UX, though it’s not currently super focused on being user-friendly. For now, we’re prioritizing power users due to these challenges, so it have more fidelity and transparency. Please take a look, and it would be amazing if you’d like to contribute!
If you like please join us: https://cordn.net/chat/dfa7475d-c9ef-46df-bf85-1f481fdcf2c4?m=eyJuYW1lIjoiQ29yZG4gRGV2IiwiaWNvbiI6IvCfqqIifQ

2026-07-03 22:21:08 CEST

- reply

Yes! up to the devs! The spec is open. Probably we will release an sdk eventually. But with the spec and the references should be good already

2026-07-03 16:23:31 CEST

We’ve started working on the multi-device spec! I already have a solid draft for it, along with test cases. If you’d like to review it, please take a look
https://github.com/Cordn-msg/cordn/blob/feat/multi-device/spec/applications/multi-device.md

2026-07-03 08:47:00 CEST

GM GM!

2026-07-03 08:43:37 CEST

- reply

Thanks! Appreciate the mirroring :)
I'm curious to know what are your thoughts on cordn. Do you like it?

2026-07-03 08:42:40 CEST

- reply

🫶

2026-07-03 08:42:28 CEST

- reply

🫶

2026-07-02 21:14:44 CEST

- reply

hahaha it was lying somewhere in my fs. Pure gold!

2026-07-02 21:13:12 CEST

- reply

Hahaha, grassroots ftw! The npub will come, in the meantime, feel free to tag me anytime

2026-07-02 21:12:03 CEST

- reply

Oh you’re going to make me sweat through my eyes 🥲💛 thanks for your words

2026-07-02 16:36:40 CEST

- reply

Encrpyted media spec: https://github.com/Cordn-msg/cordn/blob/master/spec/applications/encrypted-media.md

2026-07-02 16:35:26 CEST

🔥 Exciting news 🔥 Encrypted media and pinned messages🖼🔐📌
Now you can share files and media in Cordn, and it is end-to-end encrypted. Also messages can now be pinned to the top of the chat. ✨
We added a new application spec to Cordn that defines how to encrypt and decrypt media for the chat. A photo or document is sealed on your device before it ever leaves, with a key derived from the group's own shared session, and only members can derive the same key to unlock it. The coordinator and the storage layer only ever see opaque bytes. They can store and relay the file, but they can't read it.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/37797965261b03497a4e94814b6a7ac928871925217a0aa575f14f3c53d2fe74.png
For storage, the default is Blossom, though the spec doesn't mandate it. That keeps Cordn aligned with the Nostr ecosystem's media layer while leaving room for other backends. The practical size limit for a file comes from whatever server you choose.
In the web app you can now upload and share files and media straight into your groups. You can configure which servers Cordn uses for uploads, and we ship a curated list of Blossom servers that are friendly to opaque encrypted bytes.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/9c45ac0547b7b503a4c21673b663637bb5c9b3c8b12460782eab81e4644c11e7.png
Any media link you paste into a message also renders inline now, so an image or video URL shows up as a preview instead of a bare link. And under Config → Media you can choose whether images and avatars load automatically, useful on a metered connection.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/1fe67d9d21ef41d2ba366a94fd26eebb344c2a4ccd804ebf5118438139aec6c4.png
The second feature is pinned messages for groups. Anyone in a group can pin a message, and pinned ones gather in a carousel at the top of the chat. Jump straight to any of them, or open the full list to see them all and unpin. Each pin shows who pinned it.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/3b8da4c92e95b6c7410a3b05790317139805d020e6fa79a27a5dca6287416715.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/37bd8be94bc37d73cd976d30976f74551142682e35e6985b40b4a10db82bb0a9.png
A lot of media polish landed alongside:
• Tap any image to open it full-screen: zoom in or out (even past 100%), drag to pan, double-tap to fit, and save a copy.
• Download any shared file or image straight from its message menu.
• Media you've opened stays loaded when you scroll away and come back.
• Links, mentions, and previews now render in the message info panel too, not just in the chat.
• Avatars and banners respect your "load avatars" choice everywhere: chat bubbles, profile cards, and the group and direct-message list.
The complete list is available at https://cordn.net/chat/news
Aren't you using Cordn yet? Just start chatting at https://cordn.net/
If you like the project and want to see it grow, please consider contributing in any way you can. Every bit counts, report a bug, contribute with your expertise, send some sats. We are building this together in the open 💛

2026-07-01 19:02:49 CEST

Buckle up! Great new features are on the way 🚀

2026-07-01 18:57:34 CEST

- reply

Indeed, that’s one of the reasons we’re building Cordn the way we are, where nothing resides on relays, which are used merely as dumb pipes/ephemeral message buses. The actual storage happens where you can have control: the coordinator.
I like how @npub1gzu…a5ds framed it in their article:
> Selection among uncontrolled infrastructures is not sovereignty over them.
Nostr for identity and CVM for interaction already gets you close to what you’re describing, without heavy dependencies like DHTs or blockchains.

2026-06-30 19:34:10 CEST

Any message in a Cordn conversation now opens into a full info panel, the thread around it, who reacted and with what, and its delivery status, all in one place. ✨
Until now, message info lived behind a button buried in the overflow menu, and it only showed the raw event envelope. If you wanted to understand a message in context, what it was replying to, who had reacted, whether it had been edited, you had to piece it together yourself. The new panel brings all of that into a single view, with the full reply chain laid out as a proper thread.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/cbe4ccb41b47b89ae3e39e3064026efc7e1c25a0fe2c0ef7d0b9582964ca7ebe.mp4
While we were in there, we rethought how you interact with a message:
• The Info button now sits next to Reply and React on every message, so it is one tap away instead of hidden in a menu.
• From the panel you can jump straight back to any message in the chat, the one you're viewing or any other in the thread. On desktop the panel stays open beside the conversation; on mobile it closes so you land right where you need to be.
• The thread view indents replies by depth (and keeps deep conversations readable), so a long back-and-forth no longer collapses into a flat list.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/00d4c2003b54b150d86f45759121fc2da17f7eb9810b3f01deaee20950d49d11.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/b51dc3d4471194fb4e492d0bc6fc928171418c75c3bc43fb43930e12294b5fb0.png
Also in this release:
🐛 When a message you had replied to got deleted or edited, its reply preview kept showing the original text. It now reflects the current state, "This message was deleted" or the edited content, so the conversation reads honestly.
The complete list is available at https://cordn.net/chat/news
Aren't you using Cordn yet? Just start chatting at https://cordn.net/
If you like the project and want to see it grow, please consider contributing in any way you can. Every bit counts, report a bug, contribute with your expertise, send some sats. We are building this together in the open 💛

2026-06-30 10:55:12 CEST

Okay, the latest updates to the Cordn coordinator and web app have been a bit boring. We’ve been focusing on bug fixing and reliability. Now it’s time to get back to the fun stuff ahead! :)
Buckle up!

2026-06-29 21:18:39 CEST

Joining a group in Cordn is now as reliable as it should have always been. 🛠
If you ever left a group and asked to rejoin, you may have hit an annoying glitch: your join request wouldn't reach the admins until you sent it a second time (or hit "reset request state"). It was subtle, persistent, and it took us a proper bug hunt to pin down.
While we were in there, we cleaned up the rest of the join-request flow:
• You no longer see your own join request in your notifications after being re-added to a group where every member is an admin.
• Stale join-request notifications for groups you no longer administer are cleaned up automatically.
• An admin can now accept a join request from someone who is still technically in the group — they are cleanly removed and re-added instead of the accept silently failing.
Also in this release:
✨ Coordinators now display the name their server advertises when available, with your custom label still taking priority. A coordinator's page also shows its about text, website, and picture.
🔄 Sending a message no longer waits on an unrelated coordinator that is having trouble — only the group you are messaging waits for its own coordinator, so healthy groups stay snappy when another one is slow to reconnect.
🔄 The sidebar finishes loading sooner after sign-in: join requests and key packages no longer wait for every group subscription to finish opening.
🐛 The New conversation dialog and chat home now show exactly the same key-package list, so the two can no longer drift apart after a refresh.
🐛 The key packages settings page now stays in sync with the rest of the app — creating or removing a key package updates every list immediately.
The complete list is available at https://cordn.net/chat/news
Aren't you using Cordn yet? Just start chatting at https://cordn.net/
If you like the project and want to see it grow, please consider contributing in any way you can. Every bit counts, report a bug, contribute with your expertise, send some sats. We are building this together in the open 💛

2026-06-29 13:55:14 CEST

- reply

gm semi!

2026-06-29 10:17:18 CEST

Announcing a new specification for Cordn: sealed group payloads. 🔒
Are messages decryptable by the coordinator? No, they never were. MLS already encrypts your message with very fancy crypto. This new specification doesn't change that; it only reduces interpretability to the maximum.
Previously, the MLS wire framing still leaked the epoch number (a curious coordinator could watch epochs tick over). Spec/03 seals each payload under a key derived from your group's current MLS epoch secret, so the coordinator now just stores gibberish. It learns nothing. Not the content, not the epoch, not even the framing that says "this is MLS." Read the spec: https://github.com/Cordn-msg/cordn/blob/master/spec/03.md
A bonus consequence: since the routing group ID is now something the client supplies, groups could rotate their group ID from the coordinator's perspective, which also enhances privacy and reduces interpretability from the coordinator's point of view.
We upgraded the Cordn coordinator to version 0.3.x to implement this cleanly. We are rolling it out progressively in our web client, and it is opt-in for now:
• Old and new clients coexist transparently in the same group; sealed and plaintext messages mix seamlessly.
• You can enable it from any group's info page, under the 'advanced' dropdown.
• Once we are confident, sealed payloads will become the default.
We are testing this in the open, so feel free to enable it and break things. Found a bug? Let us know. 🐛
Also in this release, we have made some app improvements:
✨ Backup & recovery: export keys, group secrets, and coordinators; restore on a fresh device.
🐛 Some minor bug fixes.
🔄 Some minor changes.
The complete list is available at https://cordn.net/chat/news
Aren't you using Cordn yet? Just start chatting at https://cordn.net/
If you like the project and want to see it grow, please consider contributing in any way you can. Every bit counts, report a bug, contribute with your expertise, send some sats. We are building this together in the open 💛

2026-06-28 22:24:05 CEST

- reply

Yes, that’s true. I forgot that users don’t want to be free. Nostr relays also sound like a feature for power users to me, and it’s the same issue here. How do users choose their relays? How do they choose their coordinators?
We’re running our own for the community as the default in the app. But ideally, users who want true freedom and sovereignty should run their own to avoid depending on a third party.
Maybe we should add the default coordinator when users log in and just prompt them to get started. However, since the app is still being developed, we thought it best to focus first on power users.

2026-06-27 17:48:52 CEST

- reply

The thing is that users need a coordinator set up in order to start chatting. If we remove step 2, I feel users would be more confused since only power users would configure their own coordinators for now, and I don't feel comfortable setting up configurations for them. Well, we could indeed set the coordinator by default, but not publish a key package since that feels more intrusive, current step 2 does these two things. Configuring the default coordinator doesn't have any implications for the user. Then step 2 could simply be "let people find you," which could publish a key package. And step 3, "start chatting," would mean creating a group or starting a chat with already available people. What do you think?

2026-06-27 17:10:42 CEST

- reply

Step 2 is to set up the default coordinator and publish a key package (which allows others to chat with you) in it. This is done this way because users don’t need to use the default coordinator if they’re running their own for example. How would you abstract this away? I’d love to hear your design recommendations :)

2026-06-27 13:14:11 CEST

I don’t make the rules… At most, two or three people work on this in their spare time, with only one of them putting in a bit more effort. There’s no funding so far aside from community contributions. Driven by the vision of empowering people to have alternative, private, and sovereign communications, and, of course, love 💛
#nevent1q…gt7n

2026-06-26 18:12:43 CEST

🚀 New Cordn Web update live.
We smoothed out the coordinator and group-joining experience:
🔹 Coordinators are now saved automatically when you join a group or publish a key package — the separate "Save locally" step is gone, and joining a group can no longer silently change your default coordinator.
🔹 The New conversation dialog and the key-package directory now reflect coordinators you've joined the moment you join them — no manual save, no page refresh.
🔹 Stuck waiting on a join request? You can now hit "Request again" from the group page. Sent requests clear automatically once you're actually added.
🔹 Fixed: coordinators you just joined sometimes connected through the wrong relays.
The complete list of news at https://cordn.net/chat/news
Free and open source, as always 🫶
#nostr #cordn #opensource

2026-06-26 12:20:07 CEST

Great post :D
https://stacker.news/items/1513682

2026-06-26 11:56:21 CEST

- reply

Chinese elites too?

2026-06-26 11:55:43 CEST

- reply

GM!

2026-06-25 19:42:57 CEST

Great session today! Bug fixes and new features. Please check the https://cordn.net/chat/news for the full list of changes

2026-06-25 19:07:52 CEST

Yes, man! Great analysis 🤘
> Remember that the relay operator was defined as the scary vantage point because it sees the protocol-level events and the network layer in the same hands: what you do and where you are, at once. Cordn severs that convergence. [...] The party that can interpret the traffic cannot locate you, and the party that can locate you cannot interpret the traffic.
#naddr1qv…934r

2026-06-25 11:34:43 CEST

Oh wow, @npub1m4n…c2jl ! Thank you so much for such a fat zap! Really appreciate it :)
That will keep our public coordinator running for months 🫶

2026-06-24 23:06:03 CEST

- reply

What about Nymchat.app from @npub16jd…33sv ?

2026-06-24 16:56:36 CEST

📢 Cordn now has a News & updates feed, release notes, new features, and product updates, all in one place inside the chat app.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/eb8faaf66f96a1c5e01051708ddb398fed153e427e0b5f800de13f54700a6ded.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/933a73f4dc0ebf4fcf1f7be6761465cf0e9c65f5ae03a3beb9d869e31965f7aa.png
💛 Cordn is free and open source so we added a donation card as well and a 'Supporters' section. Tap Donate to send us a Lightning zap. The supporters list lives right there in the feed.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/382282fc90d01882cb61b918bc82750214e4f49e64184aea787c4c4c961b834f.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/49985acc100761a4440eb462097f04c616e23bdbcadd096f03bcd9f79843c9c8.png
This is just the beginning, follow along as Cordn keeps evolving.
🔗 https://cordn.net/chat/news
#Cordn #OpenSource #MLS #Privacy

2026-06-24 15:27:15 CEST

- reply

I'm using it, pretty good model tbh

2026-06-24 09:27:13 CEST

Good morning nostr. Ready to rock!

2026-06-23 17:41:43 CEST

Brother what in earth! This is powerful 🔥🤯
#nevent1q…7w22

2026-06-19 11:25:34 CEST

Hello Nostr! How's it going? Are you using Cordn already, or just pretending your comms are private?

2026-06-13 19:39:59 CEST

We broke it! Hahaha. The stress test group got corrupted, but this is good news, we identified why it happened and implemented some hardening strategies to avoid MLS state corruption. This is a win; now our app is more robust. We’re creating stress test v2, so please feel free to join and see if we can break it again! :)
https://cordn.net/chat/7960e471-22ad-40db-b0de-0d46fde708e8?m=eyJuYW1lIjoiU3RyZXNzIHRlc3QgdjIiLCJpY29uIjoi8J%2BMtCJ9
#nevent1q…z7u9

2026-06-11 17:28:15 CEST

New Cordn feature: Shareable group links 🔗
We've just added join requests for groups to the Cordn coordinator, the web client, and the CLI client. This means you can share a link so anyone who isn't yet a member can request to join a group.
Try it now: join our stress test group 👇
https://cordn.net/chat/b530f14c-fd6b-4023-8001-cebcdfbfb239?m=eyJuYW1lIjoiU3RyZXNzIFRlc3QiLCJpY29uIjoi8J%2BMsiJ9
Here's how it works: When a user request to join a group, a join request lands as a notification for the group admins. Any admin approves, the user receives an invitation and gets added, done. If the user doesn't have an account yet, they're prompted to log in and everything resolves transparently, no extra steps. It's the perfect onboarding tool. Share links out of band, drop them in public channels, simple and intuitive.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/f7eebc03e3f9350b36ae3454888c165ea12156405c9b3b7eb3e0d02615e15060.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/b01f5d4957d62b2929fdbec500034f0788bda070ac295906ae56f794d5583e70.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/269ce1174e108867f54df46694265112d2d41049ff8c20fb54b13d1c8bc53c44.png
Read the spec: https://github.com/Cordn-msg/cordn/blob/master/spec/applications/join-requests.md
This feature also kicked off a new section in the Cordn specs: application specs. Rather than extending the core spec for every new feature, app specs are separate documents for ongoing development, research, and enhancements. They keep the core spec stable while giving new ideas room to breathe and evolve.
https://github.com/Cordn-msg/cordn/tree/master/spec/applications
We're building Cordn as best we can, a project born out of love, with zero funding. If you like what we're doing, consider zapping me or contributing. Code, bug reports, ideas, everything helps.
Shoutout to @npub12w5…rrm3 for their first contribution to the web client, enhancing the login dialog. 🫶
Now go play. https://cordn.net is free, private, and needs no email, phone number, or KYC. Speak freely. No one can listen.

2026-06-10 18:20:00 CEST

Just pushed some updates to the Cordn web app. This time around, there are some minor UI/UX improvements.
- Added a new chat action button to start a conversation that lets you create a group or just start a chat with someone.
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/29d5c7212938897e3c02299b2a83db7ae339f1765d12e2363674fb95d0a00a83.png
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/7ed41c53109b7676b01c4d8115f6d1df66e8486316a4e2e569e06a4881bcc5bd.png
- Made the action icons a hamburger menu when the sidebar is collapsed (desktop).
https://npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss.blossom.band/fda411ba32357c81eb81487cd2811d8771e199641d58bc6fd5c9623e2df6fed0.png
- Improved loading states and other minor enhancements.
Enjoy!

2026-06-10 09:42:37 CEST

- reply

Thanks man! appreciated it! I'll add you to the dev group so you can share ideas, issues and other stuff and help to build this :)

2026-06-10 09:41:24 CEST

- reply

Great! thanks for testing

2026-06-10 00:25:58 CEST

- reply

Don't forget to refresh the page ;)

2026-06-10 00:25:06 CEST

- reply

Ups good catch seems like a bug in the upstream ts-mls that forces lifeTime for external key packages, and gzs kp is older than 15 days which is the default lifetime ts-mls sets. We will open a issue to them. In the meantime we patched our implementation and deployed a new version with it so the issue should be fixed. Please can you test again? Thanks for your patience 🫶

2026-06-09 22:14:09 CEST

- reply

Exactly! have you seen https://cordn.net ?

2026-06-09 21:13:00 CEST

Okay! That was indeed a great catch by @npub1gzu…a5ds . The issue was that before, new users joining a group with a long history were attempting to catch up on all the group’s previous messages.... This was incorrect because, due to MLS secrecy, all messages prior to the user’s joining are undecryptable for them, so it was unnecessarily fetching an entire message history, which created a significant load on the network (since the payload can be massive for groups with long histories). This was also wasteful.
Now, this has been fixed: new users joining a group only fetch from the epoch at which they joined, which is the point from which they can decrypt messages. I’ve updated the coordinator reference implementation, as well as the web and CLI clients.
As a side effect, I’ve also enhanced the group info page to include more details about the group’s state and other relevant information.
From now on, new users should be able to join old groups without any issues!
Thanks for your patience. We’ll continue working to improve the experience as much as possible :)

2026-06-09 18:52:06 CEST

- reply

Awesome!

2026-06-09 15:47:42 CEST

- reply

Hey! Cordn main developer here. Hope you don't mind me jumping into the conversation.
Well, what you're describing is exactly what led me to start working on Cordn. Before this, I was trying to implement Marmot and create my private chat app using it, but as you said, it was really unreliable to the point that it was driving me mad because I wasn't able to make it work reliably for groups of more than two people... Then I read the article gz wrote about private comms over public infrastructure and it all became clear. I also reused their ideas of an MLS coordinator over CVM, which is basically RPC over Nostr that allows for really easy deployment without needing to touch DNS, IPs, or anything similar. That was really what gave me hope that this could work, so I proceeded with it and created cordn.net, which is a web client implementing the protocol. So far, it's working great, even with large groups. MLS was designed to be used with coordinators, so we decided to go that path instead of fighting the protocol, which indeed made it reliable and more private than Marmot. Also, anyone can run their coordinator easily, etc. We're running one for bootstrapping.
So please, if you feel interested, just test it at https://cordn.net

2026-06-09 12:16:54 CEST

Marmot is not private, and neither is WN, at least in its current form; that’s why I started building Cordn.
#nevent1q…gmsj