|
|
|
|
|
by makeworld
1529 days ago
|
|
There are a few options: - Switch to an alternate Twitter frontend like nitter.net. There are extensions that can redirect to this automatically as well. - Block Twitter from setting any cookies. This will prevent loginwalls. - Add this custom uBlock Origin filter: twitter.com##+js(cookie-remover, guest_id)
Personally I use the last two options, and sometimes use Nitter, especially on mobile. |
|
I've mostly been using the Fritter app for now for whenever I want to read some tweet. So far, I like it very much: Native performance with no nag screens and no engagement bullshit, just tweets and replies. The only problem is the often replies don't load. My suspicion is Twitter is doing some shady stuff with the API again.