@pea Ok, tl;dr on CapTP as promised: Stands for "Capability Transport Protocol", allows for secure distributed programming across "mutually suspicious" systems efficiently, with distributed garbage collection and a highly efficient promise resolution system!
This is fast, powerful, and efficient enough to do something as advanced as distributed virtual worlds despite a potentially hostile network!
@pea You might want this for all sorts of things. But a really, really hard use case is distributed social worlds, where all that stuff has to be efficient and it has to be easy for users to program in!
Here's the best part: CapTP was designed with exactly that use case in mind. Its origin is from Electric Communities Habitat!
@pea CapTP, the concept, has been implemented a number of times since Electric Communities, so it's more like a family of protocols with some shared fundamentals than a single protocol right now. But maybe there will be a Common Lisp / Scheme-like unification effort soon.
@cwebber is there a page/reference about capTP? i'm curious/interested
@robey There are a number of pages, but I'm going to ack here that I don't think any of them are super easy to understand for a newcomer:
I am also documenting my journey here: https://groups.google.com/forum/#!topic/cap-talk/xWv2-J62g-I
@cwebber thanks! the captain link is actually quite readable! (tho it may help that i've been writing distsys for a couple of decades)
@cwebber hahahaha as someone who's always wanted to write a distributed mud, you can't imagine my crushing disappointment that the author never wrote this page: http://www.erights.org/elib/capability/ode/ode-game.html
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!