Mike Fair

It's cool how being a "user" of event systems can be so different an experience than "making the events." :) _or float off into the abyss, but are not really...

Two more useful "match types" just to note them: 1. Match on Clear -- Instead of matching when signal are 1(HIGH); this matches on signals that are 0(LOW) 2. Match...

I reread through this thread, and one thing I see that's different between our thoughts is what a "signal" is... My take is that a "signal" is like a light...

Yes, but that example doesn't really demonstrate the coordination of signals across multiple tasks or testing for multiple signals at once (either one, some, or all of many signals a...

> WaitForAny is a little unclear as to how you would test for truthiness. WaitForAny and WaitForAll were kind of implementation specific to the fact I used a bitField. The...

@haadcode I'll take a crack at pitching in on this one; PouchDB is part of the CouchDB family. PouchDB runs entirely in JavaScript on the browser. It speaks the Couch...

ping! :) @haadcode perhaps I'm misreading this, but it seems like this code is taking data out of PouchDB (via the changes feed) and putting into/onto the OrbitDB channels... Which...

If you used Pouch as a "backend" for Orbit, how do replications coming into the PouchDB from the Couch World "push up" into OrbitDB changes? Perhaps this is a case...

Here's a thought; each party participating on the OrbitDB creates an object in the DB for their peerid. The replicate their _changes feed and update their current SEQUENCE number on...

It's best to think of it more like "replication via OrbitDB" than "Syncing with OrbitDB". The main reason for the central CouchDB is because an app can't p2p replicate with...