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.

Thanks for the filter! I've been kind of looking for one and had already assumed Twitter would randomise the IDs and page layout so that setting up a static filter would be impossible. But apparently it's not!

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.

Amusingly opening a private window avoids that. I speculate they left that loophole so that people who get into slapfights and block each other can still view each others' tweets.

Opening a private window clears cookies, which typically resets these kinds of things.

Delete all Twitter cookies. If you’re not logged in you don’t need them. The wall disappears for awhile.

Up until the Ukraine war started, this worked for a few days and then I’d get the login wall. Delete cookies again, buy a few more days. Since the war started though they seem to be acknowledging a lot of non-logged-in people need to see tweets and I haven’t seen the login wall since.

Just block Twitter from setting cookies and you won't need to keep manually deleting them.

I also see this loginwall sometimes when trying to click through to related images or tweets. The workaround I've found is to open the click in a new tab. It seems if there is no browser history, twitter is less aggressive about throwing up the login wall

I browse it with an incognito window.