android

> Can you expand on this further? Wouldn’t this just be exposing myself to the same vulnerabilities as OP? Yeah I wouldn't do this personally, I just mentioned it as the simplest option. Unless it's meant to be a public service, I always try to at least hide it from automated scanners. > If I use nginx as a reverse proxy, would I be mitigating the risk? If the reverse proxy performs additional authentication before allowing traffic to pass onto the service it's protecting, then yes, it would. One of my more elegant solutions has been to forward a port to nginx and configure it to require TLS client certificate verification. I generated and installed a certificate on each of my devices. It's seamless for me in day to day usage, but any uninvited visitors would be denied entry by the reverse proxy. However support for client certificates is

https://github.com/home-assistant/android/issues/42 > We have no interest in maintaining a branch of the app that doesn't depend on any proprietary services. Developers explain why they wouldn't (naming issues, and "the point of the android app vs just using a browser is to have the location tracking, which requires google services") and then the thread was closed. And then I stopped following the issue and begrudgingly installed from Play store (I'm not de-googled, because like the GP mentioned, it's very hard to do even if you think you have done it, so in some cases I don't even try). There are a LOT of locked threads in their github issues on the same topic. The F-Droid version appears to be a build of the appropriate repo, and the description says "This is the minimal flavor that does not have location tracking or notifications" (so