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. Notification icons: Browser notifications now use the group's custom image, falling back to the favicon when none is set. 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.

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.

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 🚀 View quoted note →

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. View quoted note →

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...

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 🚀

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

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.

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

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 🔥

Hey nostr, do you want private communications? View quoted note →

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. View quoted note →

🔥Today is the day 🔥 I’m excited to introduce Cordn (https://cordn.net). This is my take on private, accessible communication for everyone. Cordn is a small protocol built on two solid foundations: @ContextVM 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. 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 @marmot 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 @LNVPS.net , 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 @Gzuuus and the @ContextVM 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. Reference RFC9420:

IETF Datatracker

RFC 9420: The Messaging Layer Security (MLS) Protocol

Messaging applications are increasingly making use of end-to-end security mechanisms to ensure that messages are only accessible to the communicati...

View article →

Tomorrow 🎇 View quoted note →

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! 🚀

GM!!

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

GMM!

GM Nostr! ready to rock!