The Deckboard server utilizes a websocket listener that has a static access key known to the app. As a result of this, any device running Deckboard can connect to any Deckboard server, pull the config, and act as a trusted client.
Fortunately the app itself has very limited privileges, and can only execute shortcuts (not add/modify them, or see what they do) so impact is reasonably limited. Nonetheless, an authenticated session and possible support for TLS (initial handshake) and WSS (ongoing communication) would be great additions.
Note that TLS support without authentication is not very useful since any client can connect and be trusted, and authentication without TLS support is similarly limited in value since the initial handshake can be intercepted by any listener on the network.
If neither of these are possible/would be considered, it would be ideal to be able to configure Deckboard server to only accept connections via local USB rather than a forced binding to a network interface and requirement for the user to block it in their firewall.
Thank you for your time, and very useful app!