Nicholas Kolba

LGTM @robmoffat - though I missed the first 1/2 of the meeting. Would it be useful to take a couple of the use cases and map out how it would...

@RandallDang-Citi the electron-fdc3 client doesn't currently use these endpoints. Definitely many good potential uses though (such as creating a richer search experience).

@sgd2z @rikoe @kriswest **note** Multiple Channel membership breaks `DesktopAgent.addContextListener` (there is no way in this API to indicate what channel a context came over) The intention was to allow apps...

thanks @ColinEberhardt ! I've created a separate issue for the devtools menu issue. This needs to be solved by rendering the menu in its own window so that it can't...

@robmoffat ++ need for more dev tooling including example/hackable apps and things like visualization of the interop state (the bus) Re: splitting out logic into FDC3 and "Electron" (what we...

most of this is addressed with PR #82 . Will need to verify the routing with instance identifier arg.

@kriswest I think clear rules and criteria would make sense since other companies have multiple entries, there are other vendor specific implementations listed, and other entries make marketing claims. Not...

@kriswest @robmoffat is there any update on this? Happy to make tweaks to the categories, but I'd like to know what the consensus is.

thanks @kriswest, these ideas make sense to have for the community page in general. What does it mean for this PR?

Completely agree with @rikoe here. If the goal is to avoid circular workflows in your implementation. Seems like the best place to this would be behind the scenes in the...