local backend could itself pair and communicate with selene, this would provide access to all the services without pairing
Advantages:
Only pair once, manage all your devices as one
Spoof personal info in selene (location, email...)
Local backend knows real info
Hide number of devices you own from selene
Can implement opt-in behavior and share data with mycroft
For this to be useful the selene ui changes should be handled by local backend, effectively we would be using mycroft home to manage our local backend instance like if it was a mycroft device
local backend could itself pair and communicate with selene, this would provide access to all the services without pairing
Advantages:
For this to be useful the selene ui changes should be handled by local backend, effectively we would be using mycroft home to manage our local backend instance like if it was a mycroft device
https://github.com/OpenVoiceOS/selene_api
The text was updated successfully, but these errors were encountered: