@pea IN OTHER WORDS: let's say you want a distributed programming environment. And actually, you want to open it up to the entire internet! Except you don't trust the whole internet. But you want to be able to make cool things and hand out access! But you don't want to run out of memory for all the garbage sitting around. And you want to be able to make programming this system not resemble "callback hell" and have it be efficient!
CapTP does *all those things*.
@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!