[geoffeg]

I've considered hosting my own Nitter and Bibliogram instances but I have to wonder if that reduces their privacy veil a bit. Wouldn't the requests from those instances be coming from a single IP, thereby potentially allowing their respective services to still track you? (Sure, you're avoiding the analytics from those service's web front-ends or apps but that can probably mostly be achieved by disabling JS.) I've considered adding a VPN or TOR gateway between the nitter and bibliogram instances I host to make them harder to track.

[midasz]

For twitter to me, it's not even about privacy - the regular frontend without being logged in is unusable. My instances are hosted publicly but I don't advertise them. I guess if people fancy it they are free to check it out, but would prefer it not to end up on any lists: https://midas.rocks/

[perlgod]

I agree. If you're the only user of your instance, they can easily track you server-side by your IP address. You could mitigate this by routing your egress traffic (either from the individual device or network-wide, from your router) through a VPN.

[dvzk]

It’s really not that much extra work to automatically rotate VPS IPs or VPN relays on an hourly or daily interval. Since most Invidious/Nitter guides don’t recommend doing this I guess it’s not very common.

Just remember that you’re still technically trackable via behavioral, configuration, or latency fingerprinting. Anonymity is a full-time academic endeavor, not a shell script one-liner.