A simple request is sufficient, I'm only a moderator, but I'm happy to accommodate a request :)
CameronDev
joined 2 years ago
Privacy policies are only as good as your ability to legally enforce them. And without a name or address, you'll struggle to do that against a github account. Even a lawyers name would be a start.
Cloudflare may know their identity, but thats still a gamble.
The simple answer is self-host (or dont host it online at all) if you really care about keeping your data safe. Otherwise, use a provider with a published name and address, and if they leak your data, use the legal system to resolve it.
With no published owner information, YS consider it a honeypot.
As you've described it, and from what I have read, its very similar to how tailscale negotiates its connections.
Does seem to be unique to Plex though.
I get how that could work, but what services actually do that? Homeassistant can, but that needs to be setup explicitly for it to work.
How does that work? Do they do something like what tailscale does to negotiate the connection? Can you point me to any doco for how that works?
I dont know that that is true. With cloudflare tunnels, their server.x.y.z will resolve to a cloudlfare IP address, which then tunnels it to their server? The traffic has to hit the cloudflare server, it can't short circuit that connection? Am I missing something?
I would assume yes, it goes out to cloudflare and back in. You want to setup an internal DNS server on your network, and resolve your servers address to its local one. That way when your outside your network, you use the tunnel, and inside it goes direct.
What are the ramifications of letting an old domain that was used for email go back into the market?
-
You can't receive those emails anymore.
-
Someone else can.
Seems like its been pinned there somehow, despite being 2 days old. Happens when logged out as well.
view more: next ›
That could be a tricky one to detect, lots of people (including OP) have accounts on different servers.