This topic is probably too complex to address well in tweets, but here it goes anyway...
-
-
Replying to @RichFelker @_K_E_L_S_E_Y
1. For now, the logging/surveillance infrastructure on VPS providers is likely tailored for servers not VPN'd clients.
1 reply 0 retweets 2 likes -
Replying to @RichFelker @_K_E_L_S_E_Y
2. By using commercial VPN inet service, you identify as "intentionally hiding". Using VPN-to-VPS looks like "work from home".
2 replies 0 retweets 5 likes -
Replying to @RichFelker @_K_E_L_S_E_Y
3. You said DO/AWS, but you can choose a VPS instead in a jurisdiction with stronger privacy laws...
2 replies 0 retweets 6 likes -
Replying to @RichFelker @_K_E_L_S_E_Y
4. Most of this is about mitigating privacy invasion & dragnet surveillance, not targeted attacks; no VPN addresses latter.
1 reply 0 retweets 2 likes -
Replying to @RichFelker @_K_E_L_S_E_Y
5. VPS providers are a competitive market; privacy invasion of customers would hurt them badly if it came out.
1 reply 0 retweets 2 likes
(The main reason we need regulation to stop privacy invasion by ISPs is that they're local monopolies, not competitive.)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.