Dart client daemon for desktop (at_daemon)

[XavierChanth]

Is your feature request related to a problem? Please describe. Browser support; preventing local secondary cache duplication.

Describe the solution you'd like A desktop application or daemon that exposes the atProtocol locally through one or more of the following:

• REST API
• GraphQL API
• Secure websockets

Features:

• The daemon app could perform some sort of local handshake with the requesting app, and requires human input to accept or deny the requesting application.
  • You could also trust a hostname / application to avoid having to do this every time.
• The daemon could live in the tray, as a full gui application, or both.
• All onboarding of keys would happen within the daemon app.
• Built in developer tooling:
  • Gui developer client for viewing & modifying keys
  • View Local secondary Logs (and toggle level)
• More TBD

Describe alternatives you've considered See #606

Additional context See #606

[XavierChanth]

An MVP was completed in PR 42, I will continue work on this in PR 43.

[XavierChanth]

@gkc shall we lower the number of SPs for PR 44?

[gkc]

sgtm

[XavierChanth]

@gkc @cconstab do we need at_daemon if we have API no ports?

[gkc]

@XavierChanth I don't follow ... how does "API no ports" address the problems which led to this feature request?

Browser support; preventing local secondary cache duplication.

[XavierChanth]

@XavierChanth I don't follow ... how does "API no ports" address the problems which led to this feature request?

Browser support; preventing local secondary cache duplication.

Right, fundamentally different goals.