I feel author has a pretty narrow view of the software one can write, I am still not sure what they mean by "app".
My first idea was that it could be an local application, as in win32/linux/macos binary with Qt. But then all those hoops to bypass limitations makes no sense - you make a config file and you are done, or you can discover other applications on same PC...
The other idea could be a an Android or iPhone app.. but then author started to talk about tailscale and I got confused - surely they are not running tailscale active _all the time_ on their phone?
So now I am maybe thinking author means a "web app", as in a page full of javascript. This explains a need for extreme hoop jumping - the browser sandbox is very strict. But then I can't understand why not do the discovery on backend, which has no restrictions?
1 comment
[ 5.0 ms ] story [ 15.0 ms ] threadMy first idea was that it could be an local application, as in win32/linux/macos binary with Qt. But then all those hoops to bypass limitations makes no sense - you make a config file and you are done, or you can discover other applications on same PC...
The other idea could be a an Android or iPhone app.. but then author started to talk about tailscale and I got confused - surely they are not running tailscale active _all the time_ on their phone?
So now I am maybe thinking author means a "web app", as in a page full of javascript. This explains a need for extreme hoop jumping - the browser sandbox is very strict. But then I can't understand why not do the discovery on backend, which has no restrictions?
this post has _a lot_ of background missing.