Besao

Cooking 🍳

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

Public Key

npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

Profile Code

nprofile1qqsqvrswzdwm6at2szucdykfqfytdpkk24vxcvvfetjr2zeg6flw30spp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdudl3zf5

Publishing to

Author Public Key

npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

Show more details

Last Notes

2026-07-17 09:30:54 UTC

- reply

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

2026-07-17 09:10:21 UTC

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 18:38:34 UTC

- 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 15:53:20 UTC

- 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 15:52:18 UTC

- 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 15:29:41 UTC

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 15:25:59 UTC

- reply

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

2026-07-16 15:24:27 UTC

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 14:36:25 UTC

- 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 08:36:32 UTC

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 11:03:25 UTC

- reply

GM!

2026-07-08 18:02:17 UTC

- reply

I type a lot already hahaha

2026-07-08 16:31:52 UTC

- 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 08:06:12 UTC

- 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 17:33:49 UTC

- reply

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

2026-07-06 08:02:21 UTC

- reply

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

2026-07-04 16:41:40 UTC

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 09:21:53 UTC

- 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 20:21:08 UTC

- 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 14:23:31 UTC

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 06:47:00 UTC

GM GM!

2026-07-03 06:43:37 UTC

- reply

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

2026-07-03 06:42:40 UTC

- reply

🫶

2026-07-02 19:14:44 UTC

- reply

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

2026-07-02 19:13:12 UTC

- reply

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

2026-07-02 19:12:03 UTC

- reply

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

2026-07-02 14:35:26 UTC

🔥 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-06-30 17:34:10 UTC

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-29 19:18:39 UTC

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-27 15:48:52 UTC

- 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 15:10:42 UTC

- 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 11:14:11 UTC

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 16:12:43 UTC

🚀 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 09:56:21 UTC

- reply

Chinese elites too?

2026-06-24 13:27:15 UTC

- reply

I'm using it, pretty good model tbh

2026-06-11 15:28:15 UTC

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 16:20:00 UTC

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 07:42:37 UTC

- 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 07:41:24 UTC

- reply

Great! thanks for testing

2026-06-09 22:25:58 UTC

- reply

Don't forget to refresh the page ;)

2026-06-09 22:25:06 UTC

- 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 20:14:09 UTC

- reply

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

2026-06-09 19:13:00 UTC

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 16:52:06 UTC

- reply

Awesome!

2026-06-09 13:47:42 UTC

- 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 10:16:54 UTC

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

2026-06-09 07:36:15 UTC

- reply

Just go to cordn.net, log in and create a key package, then I can add you there :)

2026-06-08 21:34:07 UTC

Latest updates from tonight session:
Search keywrds and sidebar polish: The sidebar search now supports `@me` as a keyword, expanding to the user's npub and all resolved profile names with OR semantics. Typing `@` triggers a keyboard‑navigable autocomplete dropdown.
https://image.nostr.build/8d90391b692568c3337b5b456415f38f7c181d7da1bb19105b0ca5c8490d99a4.png
Notification icons: Browser notifications now use the group's custom image, falling back to the favicon when none is set.
https://image.nostr.build/b0e4dd03d7683d0b1aa2940d6de959ae6ee66346ce7cb2c5fbe361a1c35cc855.png
Composer fixes and copy action: Textarea now shrinks correctly on clear and scrolls on overflow, using requestAnimationFrame‑driven effects. Copy‑to‑clipboard added to message dropdown.
https://image.nostr.build/5175935b3179a72eecd2f721e75aba2f1b4d5301efcf9de91809953798d95cbd.png

2026-06-08 20:18:45 UTC

- reply

Great idea 🤙

2026-06-08 20:18:17 UTC

- reply

Thanks! If you find it interesting, join and I’ll add you to the Cordn dev group so you can help us build this, test, report, etc :)
Well, Cordn is a protocol, so you could be referring to developers who build on top of it or to actual users. If it’s the latter, the idea is that they can run their own coordinator for themselves, their community, etc. On the other hand, we are running the current default coordinator that the app offers for bootstrapping. In that sense we plan to provide a solid service and eventually offer a paid tier, but users can migrate at any point and hand off the group’s coordinator to their own. This ensures no lock‑in and a very low exit cost, host your own coordinator or move to a more convenient service. We think this is fair, and other coordinators can follow the same model, creating an ecosystem that can be sustainable in the long term while always allowing easy self hosting.
At the end of the day, all coordinators are the same by the protocol and learn very little from their users, so baseline privacy is already good even with a public coordinator service.
For devs, well keeping the protocol open and honest
Please join if you’re interested 🤙

2026-06-08 19:36:37 UTC

Hey everyone, what features would you like to see next in Cordn?
Here’s what we have in mind:
- richer content for chat messages (e.g., long‑form posts, calendar events, zaps, polls, and any other Nostr‑related integrations that makes sense)
- disappearing messages
- encrypted media uploads
- spec for multi‑device support, plus implementation
- a spec defining coordinator handoff and migration, plus its implementation
- local backup and restore options
Please share any other ideas you have, or simply let us know which items from the list you’d like to prioritize.

2026-06-08 18:44:02 UTC

- reply

I've been patching some stuff related to welcomes. Please feel free to send me a message or to anyone. I could also invite you to the dev group if you want to help us build this :)

2026-06-06 20:31:44 UTC

Also, we just pushed some updates. We added drafts, so if you navigate between groups while writing a message, the draft is persisted so you don’t lose it. We also introduced rendering of system messages as requested recently, actions like adding members, removing members, editing group metadata, etc., are now rendered. Additionally, there are a few minor tweaks. Let me know if you find any issues 🚀
https://image.nostr.build/3247851fdddce7f0bed5c097c8636d8dde148b7a396f2fb4eb8d18aefd5ba24f.png
#nevent1q…rj5t

2026-06-06 20:24:17 UTC

This is great! Cordn is already deployable and self‑hostable; it doesn’t rely on IPs, DNS, or anything similar. It’s still in beta, we just started the project a few weeks ago, but it works and is a fantastic option 🫶 You can just visit https://cordn.net and use it. You won't need a phone number, email or nothing similar, just a nostr key that you can even generate on the fly.
#nevent1q…r6mu

2026-06-03 15:00:04 UTC

BTW, if you have any suggestions to improve Cordn or any feedback, we can invite you to the Cordn dev group, which is available on Cordn. Yes, we use our protocol to host the dev channel, and it works. Few...

2026-06-03 14:40:28 UTC

Little update to the Cordn web app: the profile page now shows a “Start Chat” button, allowing you to start a chat directly. You can share your profile page with anyone to let them connect with you, or make it public so people can see how to chat with you.
Mine is https://cordn.net/p/npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss let's have a chat there! :)
Additionally, we added a QR code button in the sidebar, making it easy to share your profile page in person and start chatting.
Little pieces for a great experience 🚀
https://image.nostr.build/1144050c1a682d4b3d7bad88cd80fcabf8d282e5924c012b278c51f3b555bfe4.png
https://image.nostr.build/bf85f8ead48ef0bd4b5592320a49152f5c8b206409a18fa19bd845f8e2b63d3b.png
https://image.nostr.build/f7eb519f3550d182cf7e5292b9328dfbc1ede70ef256c6df73d147b34edeb6ff.png

2026-05-31 09:16:59 UTC

CordnCordnCordnCordn, I was pushing some new goodies, mostly maintenance and polish. The next iterations will bring very cool features 🔥

2026-05-27 15:23:56 UTC

Just pushed some changes to https://cordn.net
Browser Attention & Reconnect Status
- Chat attention service: centralized browser-level unread tracking including dynamic tab-title message counts, browser notifications for new messages, and mobile sidebar attention indicators.
- Reconnect status tracking: new service to display real-time coordinator connection states in the chat UI.
- Key-package tracking refactor: groups now store `joinedWithKeyPackageRef` directly instead of marking packages as consumed, simplifying lifecycle management.
- `ChatGroupListItem` component: extracted reusable list item for consistent group rendering across sidebar and main views.
- Message UX improvements: added touch actions for mobile, improved text wrapping, and reaction tooltips showing reactor names.
- Welcome notifications: enabled periodic background refetching to keep pending welcomes up to date.

2026-05-27 08:48:08 UTC

- reply

Every single word is slop lies

2026-05-27 08:30:02 UTC

Wake up, check cordn.net, catch up on messages, everything’s still working. Life is good 🧘🏼‍♀️ Good morning!

2026-05-26 15:13:37 UTC

- reply

That was from an early version; there are no relays now, as they were never needed for configuration. Was just for power users

2026-05-26 13:48:50 UTC

- reply

Thanks you 🫶

2026-05-26 08:44:45 UTC

- reply

The code is open source, everything is done client side, coordinators cannot read messages even if they want

2026-05-26 07:25:43 UTC

So far, so good. The release of https://cordn.net went great, new people are joining, activity is increasing, and everything is holding up nicely. We’ve received good feedback, though there are still a few things to polish.
Life is great, and I’m very proud of this. Bringing private, permissionless communications into an increasingly less private, aggressive, and permissioned world feels truly powerful 🔥

2026-05-26 07:21:02 UTC

- reply

Thanks Doc ♥

2026-05-25 19:15:56 UTC

Hey nostr, do you want private communications?
#nevent1q…e7l4

2026-05-25 17:42:41 UTC

Testing this is as easy as:
1. Open https://cordn.net/chat
2. Log in and follow the recommended setup; it will add the default coordinator we are running and create a key package.
3. Start chatting.
If you’d like to be added to the Cordn Dev chat, please let me know and I can add you.
https://image.nostr.build/5bc547902d6d86213cf9a306c95be1d5f389139d2e6fdfe3937817dd3697cddd.png
#nevent1q…my58

2026-05-25 17:04:27 UTC

🔥Today is the day 🔥
I’m excited to introduce Cordn (https://cordn.net). This is my take on private, accessible communication for everyone.
https://image.nostr.build/2facfc7651d9b65883bdc1c5012983c46c6714901c03f4cdbc2aa9df28899e78.png
Cordn is a small protocol built on two solid foundations: @npub1dvm…3jdm and MLS. MLS is already emerging as an internet standard, and it handles the cryptographic heavy lifting. It provides quite strong security guarantees, including post-compromise forward and backward secrecy. It is also highly scalable, handling large groups efficiently without the overhead that double-ratchet protocols like Signal carry.
https://image.nostr.build/48f6484a15bf96007937bb366a789f71e87361a0e3c8976528a84ae92d203ebe.png
That power comes with a requirement. MLS needs tight coordination between group members. All the secrets that let you participate are computed locally, and without strict message ordering, an out-of-order message can cause your state to drift. You could silently fork yourself out of a group without ever noticing.
That is exactly why Cordn is built around the concept of coordinators, or delivery services, as the MLS specification calls them. A coordinator have very little responsability: it keeps messages in order. It cannot see who is participating. It cannot read messages. It cannot see IP addresses. It just orders messages and delivers them.
Cordn uses one coordinator per group. This keeps state simple and avoids the consistency problems and race conditions that come from splitting a group across multiple coordinators. The upside is that Cordn is fully open source, and deploying your own coordinator is effortless. Switching between coordinators is straightforward too, thanks to ContextVM.
You can run a coordinator behind a firewall or NAT. No static IP, no domain, no DNS required. Just run the existing coordinator implementation on any device and it becomes accessible. Using ContextVM was a deliberate choice. It makes deployment trivial, and it strengthens privacy because Cordn traffic is fully encrypted and blends into broader ContextVM traffic. An external observer learns nothing useful. They cannot tell that Cordn is being used, let alone who is using it or which groups exist. Running your coordinator would be the equivalent of running a Discord server or a Signal server, but in a very easy way, fully private and open source.
Coordinators handle three things: message ordering, storing and delivering encrypted blobs, and acting as a key package directory. That's it.
Spinning one up takes a single command:
'docker run --rm ghcr.io/cordn-msg/cordn:latest'
Because coordinators are intentionally minimal, migrating between them is clean. If your group’s coordinator goes offline, you can move to another one and carry on. The rule is simple: one coordinator per group at a time. Migration is not fully implemented yet, but it is coming soon, along with multi-device support.
Today I am announcing both the coordinator and a web client, now live at https://cordn.net. There is also a CLI client available in the main repo; it is primarily intended for testing, but it is fully usable and interoperable with the web client.
The web client is already quite capable. It is early, and there are still rough edges, but the experience is quite solid. I spent the weekend stress-testing it with groups of around ten people, plus smaller groups and individual chats. It held up well, which gives me the confidence to release it.
Cordn is also a protocol. It draws inspiration from @npub1mar…r6m9 around user identities, group metadata, and Nostr envelopes for group messages. Kudos to the Marmot team for pushing boundaries. The protocol defines coordinator roles, transport conventions, group metadata, identity conventions, and Nostr message envelopes. If you are curious and want to build on it, the spec and code are at https://github.com/Cordn-msg/cordn. There is also a larger text about the why behind Cordn at https://cordn.net/why if you are einterested.
That is Cordn in a nutshell: private messaging you can own, sovereign, and accessible to everyone.
To lower the barrier to entry, we are running a public coordinator so you can get started without hosting anything yourself. It is completely free and will stay that way until everything is stable. After that, we will figure out how to pay the bills. The important part is that a fully sovereign experience is always available. You can run your own coordinator for yourself, you agent swarm, your friends, your family, or your community, you own it. We are running ours on an inexpensive VPS from @npub1lnv…7vjj , and you can easily do the same.
We also plan to release deployments for Umbrel and Start9 soon. If you have experience packaging apps for those platforms, your help would be deeply appreciated. Cordn is fully open source, and every contribution matters. We are building this for love and freedom.
I cannot close without thanking @npub1gzu…a5ds and the @npub1dvm…3jdm team. They provided the inspiration and the core technology that made Cordn possible. It began with a ContextVM project called cvm-mls, which planted the seed for everything here. gz also opened my eyes with his article “Private communications, over public infrastructure” and pointed me to the cvm-mls repo. None of this would exist without them. Thank you so much.
Without further ado, you can reach me here on Nostr and, of course, on Cordn. Do not hesitate to ask anything. We also have a Cordn dev group you are totally invited to join, so let me know and we will add you.
https://image.nostr.build/e163e8a79e89cf0a74effd4fe33c02fa6e18ff906c0edc53e770d89cf40ba65f.png
Reference
RFC9420: https://datatracker.ietf.org/doc/rfc9420/
#naddr1qv…8mr0

2026-05-25 07:30:51 UTC

- reply

Hehe wait for it! will be out soon

2026-05-24 20:44:55 UTC

- reply

Now or never

2026-05-24 15:04:06 UTC

- reply

👋

2026-05-24 15:01:42 UTC

Tomorrow 🎇
#nevent1q…3dwj

2026-05-23 21:25:01 UTC

- reply

MLS is well suited for large groups. Marmot uses MLS, but that doesn’t mean it scales in the same way, since some of the protocol’s conventions are shifted. Specifically, MLS requires strong coordination among all group members. This means that things like out-of-order messages, degraded network states, and similar issues break MLS. That’s why MLS deployments typically require a coordinator or delivery service to ensure group messages follow the strict ordering MLS demands.
Marmot, however, uses Nostr relays as both a dissemination layer and storage. Since there’s no delivery service or nothing ensuring that all members receive messages in the same order, all the coordination MLS requires must be handled client-side by each participant. Each participant must reach the same state to maintain group integrity. This means the complexity of keeping everyone on the same page scales with the group size.
For example, a group of two usually works without issues. A group of three requires that each member consistently lands in the same state, which is manageable under good hygiene and network conditions, meaning all relays in a set are online at all times, with no race conditions (e.g., one relay going offline while others don’t, you know classic nostr race conditions). But still three members can work under good conditions. But as you add more people, each new member increases the complexity of keeping everyone synchronized.
Anyway, sorry for the length 😅 I tried to explain myself as clearly as possible.
But in summary, MLS scales well for large groups but requires coordination. Without coordination, these scalability assumptions break down. I reached these conclusions after reading @npub1gzu…a5ds ’s article on private communications over public infrastructure, as well as discussions with him. It was very helpful indeed
I hope this clarifies things! Please don’t hesitate to ask if you have any questions, these are complex technical details :)

2026-05-23 21:06:17 UTC

- reply

Oh yes, Simplex has been a great reference, as well as Signal, but we finally went with MLS since it is indeed the most portable, open, and scalable solution from our point of view.

2026-05-23 10:40:15 UTC

- reply

No, they have been a great inspiration, and we are reusing some of their concepts. However, the motivation to start this project was directly the frustration of making Marmot work for groups of more than two people

2026-05-23 10:11:58 UTC

- reply

CC @npub1gzu…a5ds

2026-05-23 10:09:35 UTC

I’ve been quietly working heads down on a new approach to truly private messaging over Nostr. It uses cryptographic MLS guarantees, with Nostr serving as the transport layer, identity layer, and envelope semantics for group messages, everything ephemeral and blended into the traffic.
This is almost ready! I’ll release it on Monday after polishing a few bugs to make it as solid as possible. Just sharing because I'm so excited to release this. Mark your calendars! 🚀

2026-05-20 08:12:51 UTC

- reply

hehe you know that's true 🤘

2026-05-20 07:55:36 UTC

GM!!

2026-05-19 09:57:23 UTC

Hello nostr! GM have been heads down working on cool stuff. I think I'll release something really cool soon. Stay tuned! Also on-chain zaps are retarded

2026-05-17 09:30:46 UTC

- reply

It’s been a bit of a shitshow lately. It’s incredible how so many people just applaud with their ears for following bad practices that we’ve been fighting against for years (for good reasons). Well, Nostr is for enemies as well, right?...

2026-05-17 09:27:41 UTC

- reply

Good luck redeeming these zaps, and be careful not to doxx all of yourself along the way. Also keep an eye on your back when you step onto the street.

2026-05-17 09:24:42 UTC

- reply

Hahaha.... Good luck

2026-05-12 11:18:13 UTC

GMM!

2026-05-11 14:41:18 UTC

- reply

Woohoooo! 🤯

2026-05-11 09:32:46 UTC

GM Nostr! ready to rock!

2026-05-09 10:05:11 UTC

- reply

U🤡

2026-05-09 10:04:00 UTC

- reply

Hey! Besao here! Working on freedom and privacy tech

2026-05-09 09:58:35 UTC

- reply

In the long term blue team wins

2026-05-09 09:47:05 UTC

Good morning, nooooooostr. I can’t hold it much longer. I really want to show what I’m working on. I just need a bit more time to get it to a point where I’m comfortable with it, and then we’ll have a prototype! 🔥🔥
Advancing private messaging over Nostr 🥷🏼
#dev #grownostr

2026-05-09 09:43:21 UTC

- reply

No lies detected

2026-05-08 09:45:00 UTC

GM!

2026-05-05 15:06:13 UTC

This article is both revealing and inspiring, and I’m actually working on something related 👀
#naddr1qv…y226

2026-05-05 14:59:16 UTC

- reply

GM mahole!

2026-05-05 14:58:11 UTC

Hello!! Anybody there?
#grownostr

2026-05-04 08:26:28 UTC

GM! Let's get this week started!

2026-04-24 14:04:44 UTC

I'm inspired. Loads of work to do.

2026-04-22 21:17:19 UTC

Hey nostr! Cooking cool stuff. Developing. Cooking. Ready to rock. You all know what I'm talking about. Definitely not a bot 🤙