CMCDragonkai

Would this only be completed if you've also pushed this up to Polykey-CLI? I don't think a new version is updated yet? @brian.botha

Nice! I want to point out that we do have some notion of "time destructuring". https://github.com/MatrixAI/MatrixAI-Graph/issues/42 https://github.com/MatrixAI/MatrixAI-Graph/issues/43 - this is the right one.

If websockets conversations is possible MatrixAI/js-ws#2 is possible, then push flows from PK can push all the way pass the program boundary and send events out, by initiating calls to...

Some notes from the experiments in PKE. Every domain object exposes 2 kinds of things: 1. Pull-methods 2. Reactive Properties The pull methods are any method call that returns a...

Regarding your ideas on parallelising the request process. Just beware of a couple of things: 1. Third party IdPs may change their UI - so it's best to rely on...

We have observed Observables to be the functional synthesis of all kinds of push-structures, whether they are callbacks, event emitters, pub/sub, streaming, observer pattern. I believe they are currently the...

Interaction between pull and push. 1. Pull methods are called to perform side-effects or anything. These may result in errors. Errors are always returned to the caller via exceptions or...

   Some ideas here that still need to be summarised. Best events architecture is being iterated on in js-quic, and will then be summarised for usage in other...

Should new issues be created in PK-CLI for such integration/acceptance testing? It's not enough to be done on the PK library - you may do it with @CryptoTotalWar.

I think in general tasks need to be checked for any weird errors. The latest staging version still comes up with things like this: ``` WARN:polykey.PolykeyAgent.task v0pi41vb17do01e9e5btfbaadtc:Failed - Reason: ErrorUtilsUndefinedBehaviour...