Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sending knocks in response to intents from other apps #49

Open
jp-bennett opened this issue Dec 5, 2016 · 2 comments
Open

Sending knocks in response to intents from other apps #49

jp-bennett opened this issue Dec 5, 2016 · 2 comments

Comments

@jp-bennett
Copy link
Owner

Need to add intent handling and some sort of restriction system, so intents aren't just blindly accepted. A simple solution would be to just mark each knock as allowing or not allowing remote trigger. Potentially also store what apps are allowed to start Fwknop2 via intents, and prompt the user when a new app attempts to initiate.

@TheCraiggers
Copy link

I'd also love this. I'm looking to use Tasker to fire off SPA packets. Besides intents, is there another possibility that currently works?

@wilhelmgoering
Copy link

+1

in the mean time, Termux, shell alias or script with fwknop CLI version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants