Hacker News Reader

I wouldn’t post encrypted comm to Twitter because I‘d suspect they keep tight logs on my IP. A random blog probably wouldn’t.

View on HN

WordPress logs all comment IP addresses forever.

That's what proxies are for.

I guess you‘d need a MITM SSL proxy to mask your originating IP? That seems to be a bit complicated for this usecase, if Twitter uses certificate pinning?

EDIT: I see now that I had a misconception here. There's no need for a MITM proxy in this case.

Why would you need the MITM part? Just use Tor, VPN or a forwarding proxy to tunnel all your traffic through an IP you can't be connected with.

They (used to?) block most Tor nodes and popular VPNs. But I just found out they launched an onion service last year!

If you have to worry about that, then the encrypted communication is just theater.

Reply on news.ycombinator.com