3 ms·
You will probably also want to add `--no-logs-no-support` (don't mind the FUD-y argument name) to the scripted invocation of `tailscaled` here: https://github.c
by Lammy 2mo ago
You will probably also want to add `--no-logs-no-support` (don't mind the FUD-y argument name) to the scripted invocation of `tailscaled` here: https://github.com/victoria-riley-barnett/koreader-tailscale/blob/993642a/bin/start_tailscale.sh#L23 https://github.com/victoria-riley-barnett/koreader-tailscale...
Otherwise Tailscale (the company) will be collecting your behavioral metadata every time you use your Kindle (what other hosts it connects to, on what ports, connection open and close timestamps, etc): https://tailscale.com/docs/features/logging#opt-out-of-client-logging https://tailscale.com/docs/features/logging#opt-out-of-clien...
Yes obviously the actual connection contents are encrypted, but ”just metadata” tells a whole heck of a lot about you: https://kieranhealy.org/blog/archives/2013/06/09/using-metadata-to-find-paul-revere/ https://kieranhealy.org/blog/archives/2013/06/09/using-metad...
- imrozim 2mo agoIf metadata loging is a concern, worth mentioning you can self host the co ordinates server with the headscale instead. cuts tailscale is out of loop entirely rather than just opting out of what claim to collect.
- madeforhnyo 2mo agoI think this is a client flag, not a server one.
- imrozim 2mo agoWasn't talking about the client flag, agreed that's seperate headscale replaces the coordination server itself the part is tailscale inc actually runs and sees the connection through that's the server side pice