Open-Source API for offline
The handy API in its current form does not allow us to run the API offline.
For tech savvy users that know how to override DNS we should be able to run the API locally.
This gives the handy more flexability as if the handy servers were to ever shut down, they would become an expensive paperweight.
Comments: 5
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
11 May, '25
User 123abcThe fact that this feature does not yet exist is the only reason I have not purchased one.
I'll be happy to pay $200+ when it can behave as if I actually own the device and it's ability to operate. -
28 May, '25
HandyAlexander AdminWe are planning to add local server support this year. We cannot release the whole tech stack for complete local hosting, but we will allow you to connect to a WSS URL of your choosing that runs a certificate that we will provide. The communication will be using the public part of our protobuf communication.
https://gitlab.com/sweettechas/platform/handy-public-rpc/-/tree/main/public/proto?ref_type=heads -
31 May, '25
VladTheImplierThat's not really what I was asking for. I would like a fully self-hostable solution that doesn't depend on a single point of failure or become a paperweight if handyapi becomes defunct. Whether it's a full server or a desktop app, I don't really care what it looks like, just that we don't have to depend on the API.
If I ever go somewhere I know I don't have internet, at least I can still make my handy work on an isolated wifi network, or just on my laptop. -
06 Jul, '25
JasonVladTheImplier, and also not anyone upvoting your suggestion. Literally no one needs the planned feature, but they can't really ignore the most requested feature since device release anymore.
So what's the strat? Half-ass something semi related to what people want hoping it will silence the community that is asking for it?
Or just to have an generic "We've implemented *insert feature not really related to the topic*, please check the documentation of *insert feature not really related to the topic*" message to send to people when referencing offline wifi usage?
Disgusting. -
10 Jul, '25
fpiwHonestly, just a way to communicate with the Handy and a way to implement buffering/streaming scripts (which currently is impossible using the bluetooth API) would be plenty. We can build the rest ourselves. Sounds good to me, and this would already be much better than the options we currently have (I for one do not want to broadcast what porn I watch and when to a 3rd party every time I use the device. *Especially* to a smaller 3rd party with less manpower).
But the "certificate that we will provide" part is a bit concerning. If it is a certificate with an expiration date, that doesn't change anything about the situation if Handy were to shut down the servers some day. And I don't really see what the benefit of this would be to either the user or to Ohdoki, it's not like there should be a security nor reputation risk here, at least if the API is sensibly designed. So I'm not sure what the upside would be, why Ohdoki would want the ability to presumably ban applications as needed.