I've seem concerns about Paradock's access to IP addresses.
When self-hosting a web service, you will need a web server or a reverse proxy to handle requests. These proxies can be configured to log IP addresses to a file, which many sites already do for moderation (i.e. finding potential ban evasion accounts). Without logging, a server will still need your IP to initiate a TCP or UDP socket connection.
Another trusted third-party with access to your IP is unlikely to cause harm, especially with the many websites and servers that a person has connected to in their lifetime.
Worst case, IP addresses can narrow down a location, but the approximation is usually not exact enough to doxx someone's address or city. This is especially true with Dynamic IPs, mobile data, VPNs, proxies, etc.
When self-hosting a web service, you will need a web server or a reverse proxy to handle requests. These proxies can be configured to log IP addresses to a file, which many sites already do for moderation (i.e. finding potential ban evasion accounts). Without logging, a server will still need your IP to initiate a TCP or UDP socket connection.
Another trusted third-party with access to your IP is unlikely to cause harm, especially with the many websites and servers that a person has connected to in their lifetime.
Worst case, IP addresses can narrow down a location, but the approximation is usually not exact enough to doxx someone's address or city. This is especially true with Dynamic IPs, mobile data, VPNs, proxies, etc.
Comments
-
-
-
Most websites already have access to or have logged your IP address for moderation purposes. In most scenarios, the IP's geographic data is not 100% exact, especially if it is of a web proxy, VPN, etc. -
He has it logged by his web server. Any server-client connection requires the IP addresses of both parties to take place.
-
"like 99% of websites already have your IP and it doesn't matter because its not accurate enough to find you with"