Besao

When you cannot find the words, say it with a GIF :)

Trust me boy we won't stop

Sovereignty means not relying on infra controlled by others

Let's go! We keep evolving

LFG! Themes are awesome

Wooop woop!!

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

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 :)

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

Boom! This is out! Fresh out of the oven. Publishing on

has been a breeze so far.

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.

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

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

Looking forward to it!

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

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.

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.

Multi-device is here 💻📱💻

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.

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

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

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!

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

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!

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

GM GM!

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

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.

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.

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.

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 💛

Buckle up! Great new features are on the way 🚀

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.

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.

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 💛

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!

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 💛

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 💛

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 💛

🚀 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

Great post :D

https://stacker.news/items/1513682

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

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.

Loading quoted post…

nostr:naddr1qvzqqqr4gupzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy88wumn8ghj7mn0wvhxcmmv9uqrzurjd9mxzar9943k7mtdw4hxjcmpw35k7mnn94hhvetj94c82cnvd93j66twveexzum5wf6kxar4wfjs5w934r

Oh wow,

! Thank you so much for such a fat zap! Really appreciate it :) That will keep our public coordinator running for months 🫶

📢 Cordn now has a News & updates feed, release notes, new features, and product updates, all in one place inside the chat app.

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

This is just the beginning, follow along as Cordn keeps evolving.

🔗 https://cordn.net/chat/news

#Cordn #OpenSource #MLS #Privacy

Good morning nostr. Ready to rock!

Brother what in earth! This is powerful 🔥🤯

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

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

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.

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

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.

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.

• Made the action icons a hamburger menu when the sidebar is collapsed (desktop).

• Improved loading states and other minor enhancements.

Enjoy!