Option to use Tor onion address instead of twitter.com #581

New issue

Open

opened 2022-03-19 16:50:29 -04:00 by termermc · 3 comments

termermc commented

2022-03-19 16:50:29 -04:00

(Migrated from github.com)

Twitter provides a Tor hidden service now. See below.

https://twitter3e4tixl4xyajtrzo62zg5vztmjuricljdp2c5kshju4avyoid.onion

This functions the same way the normal address does, but is over Tor. I imagine it also is exempt from the normal rate limiting because there's no easy way for Twitter to differentiate between clients. I tried to setup Nitter to use the address by changing api's URL to https://api.twitter3e4tixl4xyajtrzo62zg5vztmjuricljdp2c5kshju4avyoid.onion in src/consts.nim and using the Tor HTTP proxy as the application proxy in nitter.conf, but when I started the application I was met with the following output:

fetching token failed: Unable to detect compressed data format
fetching token failed: Unable to detect compressed data format
fetching token failed: Unable to detect compressed data format
fetching token failed: Unable to detect compressed data format

After attempting to visit any pages, I was hit with RateLimitError: rate limited, which I think is inaccurate because fetching the token failed. Accessing normal api.twitter.com using the Tor HTTP proxy works, so I'm assuming that the error here is a failure to deal with the hidden service.

My request is to add support for the hidden service. It could possibly be achieved with help from this package. In the meantime, I'm going to look into why it can't connect via the Tor HTTP proxy.

Twitter provides a Tor hidden service now. See below. `https://twitter3e4tixl4xyajtrzo62zg5vztmjuricljdp2c5kshju4avyoid.onion` This functions the same way the normal address does, but is over Tor. I imagine it also is exempt from the normal rate limiting because there's no easy way for Twitter to differentiate between clients. I tried to setup Nitter to use the address by changing `api`'s URL to `https://api.twitter3e4tixl4xyajtrzo62zg5vztmjuricljdp2c5kshju4avyoid.onion` in `src/consts.nim` and using the Tor HTTP proxy as the application proxy in `nitter.conf`, but when I started the application I was met with the following output: ``` fetching token failed: Unable to detect compressed data format fetching token failed: Unable to detect compressed data format fetching token failed: Unable to detect compressed data format fetching token failed: Unable to detect compressed data format ``` After attempting to visit any pages, I was hit with `RateLimitError: rate limited`, which I think is inaccurate because fetching the token failed. Accessing normal `api.twitter.com` using the Tor HTTP proxy works, so I'm assuming that the error here is a failure to deal with the hidden service. My request is to add support for the hidden service. It could possibly be achieved with help from [this](https://github.com/FedericoCeratto/nim-tor) package. In the meantime, I'm going to look into why it can't connect via the Tor HTTP proxy.

👍 3

zedeus commented

2022-11-27 10:21:40 -05:00

(Migrated from github.com)

This might be due to missing gzip compression in the Tor HTTP proxy.

termermc commented

2022-11-28 02:21:50 -05:00

(Migrated from github.com)

I'm not particularly familiar with HTTP proxies so I'm not sure. Do you have any experience with this?

Fritz66 commented

2025-05-03 12:28:30 -04:00

(Migrated from github.com)