Still don’t know why I’d need a vpn. My country doesn’t go after individuals pirating (yet). That’s the only reason, as far as I understand, to have a vpn for pirating. So until they start to take come after individuals, I’m gonna save my money.
I think it’s the older way around. There are really only 3 or 4 countries where using a VPN to pirate is needed. I’m just willing to bet you live in one of those countries.
VPNs don’t prevent tracking, they just make sure the tracking is done through a secure tunnel.
The extra hop adds a significant barrier for the website in knowing the actual source IP. The fake source IP is likely used by many other users, and the user you are trying to track can easily rotate VPN IPs.
Adtech relies on the OpenRTB 2.5/2.6 spec for tracking, you would have removed 1 identifier out of a hundred (one that isn’t really used anyway given SSAI is so popular). In addition to that, cookie expiry timers are typically set to 365 days meaning you’re VPN would need to enabled at all times to not invalidate multi-hop. WebStorage API based trackers tend to be indefinite.
EDIT: If anyone is looking for more specifics about WHY IP addresses and multi-hop don’t matter, the spec includes a mention:
BEST PRACTICE: Proper device IP detection in mobile is not straightforward. Typically it involves starting
at the left of the x-forwarded-for header, skipping private carrier networks (e.g., 10.x.x.x or
192.x.x.x), and possibly scanning for known carrier IP ranges. Exchanges are urged to research and
implement this feature carefully when presenting device IP values to bidders.
The issue is that mobile is so prevalent and mobile networks rely so extensively on CG-NAT that even with XFF headers, there’s no good way to tell if you are going to get an IP address that actually matters. You could potentially put in a lot of auction time trying to figure that out and still just end up with a private address that’s unusable. So, aside from the devicetype and the geo object which is used for geo targets and fencing, the device object isn’t useful in tracking. Instead adtech uses the user object. This object should contain all your GDPR specifics, any EIDs, 1st party cookie IDs, etc. Even if those change, there usually exists backend mapping that allows for vendors to correlate different user IDs as being the same user ultimately.
Still don’t know why I’d need a vpn. My country doesn’t go after individuals pirating (yet). That’s the only reason, as far as I understand, to have a vpn for pirating. So until they start to take come after individuals, I’m gonna save my money.
It’s a general rule, there are exceptions. I’d think it would be obvious why a VPN is needed for some even if you don’t need it.
I think it’s the older way around. There are really only 3 or 4 countries where using a VPN to pirate is needed. I’m just willing to bet you live in one of those countries.
You want a tray of cookies for that original line?
Oatmeal please. If you want to be anonymous on the internet, use TOR not a VPN.
Torrenting over TOR. Fantastic idea. You clearly know what you’re talking about.
Use cases are important.
Wanna torrent anonymously and don’t wanna pay for a VPN? Get into I2P
If you want to download at dial-up speeds for most of your stuff.
It’s still new so that’s expected, as more and more people start using it, the speeds will get better automatically.
There’s also private trackers, you won’t need a VPN if you get your torrents from them.
Also VPN makes you rather anonymous. The sites won’t track you and sometimes the trackers on public torrent files are notorious for tracking.
That is not true, the sites do still track you. VPNs don’t prevent tracking, they just make sure the tracking is done through a secure tunnel.
The extra hop adds a significant barrier for the website in knowing the actual source IP. The fake source IP is likely used by many other users, and the user you are trying to track can easily rotate VPN IPs.
Its one less identifier for them to use.
Adtech relies on the OpenRTB 2.5/2.6 spec for tracking, you would have removed 1 identifier out of a hundred (one that isn’t really used anyway given SSAI is so popular). In addition to that, cookie expiry timers are typically set to 365 days meaning you’re VPN would need to enabled at all times to not invalidate multi-hop. WebStorage API based trackers tend to be indefinite.
ORTB spec: https://www.iab.com/wp-content/uploads/2016/03/OpenRTB-API-Specification-Version-2-5-FINAL.pdf
EDIT: If anyone is looking for more specifics about WHY IP addresses and multi-hop don’t matter, the spec includes a mention:
The issue is that mobile is so prevalent and mobile networks rely so extensively on CG-NAT that even with XFF headers, there’s no good way to tell if you are going to get an IP address that actually matters. You could potentially put in a lot of auction time trying to figure that out and still just end up with a private address that’s unusable. So, aside from the devicetype and the geo object which is used for geo targets and fencing, the device object isn’t useful in tracking. Instead adtech uses the user object. This object should contain all your GDPR specifics, any EIDs, 1st party cookie IDs, etc. Even if those change, there usually exists backend mapping that allows for vendors to correlate different user IDs as being the same user ultimately.