4 ms·
> When a resource is changed by one client or server, all other clients and servers update. This reminds me a little bit of a project I started some years ago:
by jkarneges 7y ago
> When a resource is changed by one client or server, all other clients and servers update.
This reminds me a little bit of a project I started some years ago: http://liveresource.org/ http://liveresource.org/
It wasn't nearly as fancy as Braid. Just a way to get a URL's current content and then listen for changes. Kinda like Firebase, but for the web. Didn't get much traction though.
- Arathorn 7y agoThe team behind matrix.org had one prior to Matrix very similar to this too (albeit longpolling) called Glow. It was basically simple & stupid pubsub on top of HTTP: you could GET an arbitrary url, and whenever anyone PUT stuff within that url tree your GET would return. It worked well enough to build a pretty massive instant messaging platform on top of it, but the lack of schema and lack of intelligent query language got a bit frustrating. Some of the ideas made it into Matrix though. Braid looks cool; we've hoped someone would layer OT or CRDT semantics on top of Matrix but it hasn't really happened yet (unless you count Matrix itself as a set of add-only monotonic DAG CRDTs, which I guess it is). Eitherway, perhaps going in at a lower level like Braid has legs; time will tell :)
- toomim 7y agoThis is very interesting! Thank you for posting it. You have clearly thought the problem through, and we'd love to get you more involved in the consensus process.