You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've taken a look at this, and there are two key problems:
Joule exists only in the browser context, so there's not a way to have a link clicked in another context communicate with Joule, unlike native apps that can register a custom URI handler. This would require Joule to have a native component, as outlined in Consider native app companion #106.
The current lndconnect format doesn't distinguish between the REST and gRPC APIs (and based on the examples, assumes gRPC) but Joule needs to use the REST API due to browser limitations (Which could also be solved with a native app.)
I'm all in favor of being compatible with this URI format, but I think it would require a native application on my end.
Description of the Feature or Idea
I think it would be cool if Joule supported lndconnect (or some format for passing auth info)
With this we (Zap) can host a "Connect to Joule" type of button offering much cleaner onboarding UX for users.
Existing Example(s) of Feature
User downloads Zap and Joule. Syncs to the chain and opens channels in Zap, clicks "Connect to Joule" and is authed into Joule.
The text was updated successfully, but these errors were encountered: