If we're building an API/GUI for this, we might as well build an interface for custom commands or IFTTT type of things. What if you could
respond to certain commands with information outside of the APRS spec?
set up scheduled objects without running arNetSked?
turn lights on and off at your house?
etc.
If we're building an API/GUI for this, we might as well build an interface for custom commands or IFTTT type of things. What if you could
- respond to certain commands with information outside of the APRS spec?
- set up scheduled objects without running arNetSked?
- turn lights on and off at your house?
- etc.
I think most of these are outside of the current spec because they are based on pulling data from the API and using it in another system.
arNetSked replacement needs some more thought on how to 1) implement scheduling and b) plug in to the rest of it (see #21).
I think most of these are outside of the current spec because they are based on pulling data from the API and using it in another system.
arNetSked replacement needs some more thought on how to 1) implement scheduling and b) plug in to the rest of it (see #21).
Need to remember that I'm building an API. So "plugins" will be new interfaces for the API, and others will be able to design their own interfaces to the API that may not be part of this project.
Simplest "native" plugins would be Flask pages that add an API interface? What about backend stuff like #53?
Need to remember that I'm building an API. So "plugins" will be new interfaces for the API, and others will be able to design their own interfaces to the API that may not be part of this project.
Simplest "native" plugins would be Flask pages that add an API interface? What about backend stuff like #53?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If we're building an API/GUI for this, we might as well build an interface for custom commands or IFTTT type of things. What if you could
I think most of these are outside of the current spec because they are based on pulling data from the API and using it in another system.
arNetSked replacement needs some more thought on how to 1) implement scheduling and b) plug in to the rest of it (see #21).
Need to remember that I'm building an API. So "plugins" will be new interfaces for the API, and others will be able to design their own interfaces to the API that may not be part of this project.
Simplest "native" plugins would be Flask pages that add an API interface? What about backend stuff like #53?
See also: https://aprsd.readthedocs.io/en/latest/readme.html
APRSD is focused on IS, but need to read more of the details to see how flexible it is.