2 ms·
Take a look at some public nitter instances if this is a problem you regularly run into: https://github.com/zedeus/nitter/wiki/Instances https://github.com/zede
by danShumway 5y ago
Take a look at some public nitter instances if this is a problem you regularly run into: https://github.com/zedeus/nitter/wiki/Instances https://github.com/zedeus/nitter/wiki/Instances
Nitter allows viewing threads like these without logging in or even enabling Javascript. For example, this post's thread can be viewed at both https://twitr.gq/joelburgess/status/1428008043556622336 https://twitr.gq/joelburgess/status/1428008043556622336 and https://nitter.42l.fr/joelburgess/status/1428008043556622336 https://nitter.42l.fr/joelburgess/status/1428008043556622336.
Nitter has donation links on both Patreon (https://www.patreon.com/nitter https://www.patreon.com/nitter) and Liberapay (https://liberapay.com/zedeus https://liberapay.com/zedeus). Unfortunately, there isn't a way to donate to public instances that I'm aware of, but the software itself is worth supporting.
- dredmorbius 5y agoNitter is wonderful, but has limitations: - It still tends to include too much per-tweet overhead in presentation. - It limits the length of the full thread presented. - Individual nodes frequently go down and/or are rate-limited by Twitter. (I'm on about my 3rd principle instance at this point. It's begun timing out / getting rate-limited in the past week.) Threadreader solves all of these issues for long Twitter threads, and is the preferred option in this case IMO.