11–15 of 15 posts
If you make a Rayhunter, think twice before enabling its smartphone notification feature. The documentation doesn't directly warn, but presumably the notifications leak the fact that you use Rayhunter, and they go through centralized services. (With notifications being practically easier for some parties to check centrally, than how the device appears to the various cellular network towers.) As situations sometimes b…
using a different tool, "Marlin". The article has some technical details.
If you make a Rayhunter, think twice before enabling its smartphone notification feature. The documentation doesn't directly warn, but presumably the notifications leak the fact that you use Rayhunter, and they go through centralized services. (With notifications being practically easier for some parties to check centrally, than how the device appears to the various cellular network towers.) As situations sometimes b…
If you make a Rayhunter, think twice before enabling its smartphone notification feature. The documentation doesn't directly warn, but presumably the notifications leak the fact that you use Rayhunter, and they go through centralized services. (With notifications being practically easier for some parties to check centrally, than how the device appears to the various cellular network towers.) As situations sometimes b…
Not that I imagine most people would change it, but notably ntfy means that notifications don't have to go through centralized services. (As you can set what ntfy URL you want to use, including to your own server)
Then it looks like you can probably just do the communication between server and app using HTTP(S), though the app either needs to keep a connection open or poll frequently (with entirely new TCP and possibly TLS connection negotiation each poll time):
`ntfy` is impressive, but there's a lot of implementation to it that could have vulns, there's substantial server config to do, the app-side UX polish isn't great, and the connection method is inefficient. But it might not obviously leak to some centralized thing outside your control (unlike if you do iOS push notifications the normal way).
Earlier quoted context omitted.
Not that I imagine most people would change it, but notably ntfy means that notifications don't have to go through centralized services. (As you can set what ntfy URL you want to use, including to your own server)
I guess if you set up an `ntfy` server, and you also run the `ntfy` app on iOS, then the `ntfy` app can do a local notification on the iOS device (without going through Apple APN servers)? Then it looks like you can probably just do the communication between server and app using HTTP(S), though the app either needs to keep a connection open or poll frequently (with entirely new TCP and possibly TLS connection negotia…