Due to the UK’s Online Safety Act implemented earlier this year, accessing my Bluesky DM’s now means I need to allow a third-party service to scan my face, ID, or bank card. Understandably, that gives me the willies. So I can either simply never look at my messages again, whip out the likeness of Norman Reedus, OR I can log on via a VPN. However, the days of this vastly preferable third option may be numbered.
US states Wisconsin and Michigan have already proposed VPN crackdown bills aiming to close off this workaround—and the UK may be looking to follow suit. Online privacy nonprofit the Electronic Frontier Foundation recently criticised this strategy, taking aim at Wisconsin’s bill in particular, saying that blocking the use of VPNs is “going to be a disaster for everyone.”
As apex32 pointed out, it isn’t about logging, it’s about your ISP either ratting you out or outright blocking the domains and IP blocks of major providers and that’s why I said you can setup your own. Ofc even hosting one yourself your ISP can probably still determine you’re using a VPN through traffic analysis even if you’re using TCP 443 to blend in but it makes it harder.
My point is that setting up your own, you have a second ISP for the VPN endpoint. Traffic from/to that endpoint is traceable to the operator of that VPN, but now that operator is you, rather than a major provider.
The no-logging feature of the major ISPs provides anonymity by leaving them unable to correlate traffic on the endpoint to an actual person. That feature is the core function of a VPN, but it is not something that you can setup for yourself.
So what do you propose? Just not using a VPN? If you’re that worried you can run a second public VPN on top of your private one. The point of the private one is to avoid ISPs outright blocking known major providers.