Home | Notifications | New Note | Local | Federated | Search | Logout
Note Detail
Reply to @dlakelan@mastodon.sdf.org
dave@dthompson@toot.cat (2026-10-19 23:04:00)
@dlakelan The tl;dr is that OCapN is a secure RPC protocol. It's notable in that it uses the capability security model and is naturally asynchronous. Does this help?
---Reply---
Daniel Lakeland@dlakelan@mastodon.sdf.org (2026-10-19 23:11:07)
@dthompson
It does help, makes it clear its a pretty general tech. What's the theory for where its supposed to be applied? Like, if it were mature and fully usable right now, what would be a decent example application you'd expect someone to want to build with it?
Reply
---Replies---
dave@dthompson@toot.cat (2026-10-20 00:12:56)
@dlakelan I think OCapN fits in great with anything that you would consider to be part of the "control plane", where message order and integrity is critical. It is great fit for social programs like chat or anything ActivityPub is used for today, and even games with modest realtime requirements (not a twitchy FPS). OCapN would not be a good fit for use cases where it's fine if messages come in out of order or not at all, like in the aforementioned twitchy FPS case or realtime audio/video streaming (though it would be fantastic for all the other needs of such programs).