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
It would be nice to have deep linking for Kap, mainly for oauth purposes, or anything else we can think of. My main use-case would be for plugin oauth. Some services like Dropbox don't accept apps if the oauth happens in a "web view". They need it to happen in the user's browser. A way to get around that without having a server running, is to set the callback url to be a deep link to Kap, which can then receive the code. After that we'll need some kind of API for Kap to forward that code to the right plugin (and add that to the plugin docs).
If not able to deep link directly (some services require a https url), we might set up a dummy Now deployment that explains that it will open the app and deep link from there (similar to how Slack does it)
The text was updated successfully, but these errors were encountered:
yes, I would love to build a plugin for Kap for my how to video site https://relay.how and deep links would be good. Where do I go to get started to make a plugin? I didn't see info on the front page
Feature Request: deep linking
It would be nice to have deep linking for Kap, mainly for oauth purposes, or anything else we can think of. My main use-case would be for plugin oauth. Some services like Dropbox don't accept apps if the oauth happens in a "web view". They need it to happen in the user's browser. A way to get around that without having a server running, is to set the callback url to be a deep link to Kap, which can then receive the code. After that we'll need some kind of API for Kap to forward that code to the right plugin (and add that to the plugin docs).
If not able to deep link directly (some services require a https url), we might set up a dummy Now deployment that explains that it will open the app and deep link from there (similar to how Slack does it)
The text was updated successfully, but these errors were encountered: