[Kequc]

I followed it the whole way through until I got to the diagram of the way Moot handles channels compared to static channels. What does the diagram illustrate? It seems to be that the Moot version doesn't have central input. But it would all need to be filtered through something central, otherwise it is completely possible to miss a location the payload was intended to be delivered to.

[courtneycouch0]

That central location is Redis pub/sub. Multiple publishers publish to Redis and many JSON-RPC instances listen and then process the notifications to distribute.

The diagram is more meant to illustrate that the notifications don't just blanket deliver to all subscribers rather than be an exactly technically accurate.

[mmmooo]

Realistically, it sounds like the 2nd diagram should have the middle section of the first diagram. As in, a single message/circle, gets "split" (or more accurately dup'd) and somewhat simultaneously delivered to the start of every 'channel'. The way it is now makes the appearance that a message isn't sent down a channel where the logic gate will not eventually deliver it. But that doesn't seem to be the case.

[JLehtinen]

Yeah, yeah, I know: I'm just a graphic designer without a deep knowledge of the technology... But what happens in the diagram is still pretty close to what you describe, to be fair: messages duped and delivered simultaneously. Absolute accuracy would have made for a pretty complex illustration. Point taken anyway, I'll try harder next time!

Btw, did you notice it has blue heads? I thought those were cool.

[Kequc]

Why are they blue do they not understand the diagram they are being used in either?