Besao

Cooking 🍳

Public Key

npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

Profile Code

nprofile1qqsqvrswzdwm6at2szucdykfqfytdpkk24vxcvvfetjr2zeg6flw30spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5ex2225

Publishing to

Author Public Key

npub1qc8quy6ah46k4q9es6fvjqjgk6rdv42cdsccnjhyx59j35n7azlq7ntwss

Show more details

Last Notes

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 🤙