18+/"sensitive" tweets no longer available

[kaijudude]

Any 18+ Tweet that could be viewed before can't be any longer, did some update age restrict them? If so, then how do I switch it off?

[markcellus]

I believe this may not be due to a Nitter change. There's been a change Twitter has made that places 18+ content behind an age verification check. Since there's no way they can verify that users (that consume content from their API) are of appropriate age, they just dont include them.

[kaijudude]

I believe this may not be due to a Nitter change. There's been a change Twitter has made that places 18+ content behind an age verification check. Since there's no way they can verify that users (that consume content from their API) are of appropriate age, they just dont include them.
Well crap, that sucks. Hope they can find a way around it.

[gentlecolts]

I believe this may not be due to a Nitter change. There's been a change Twitter has made that places 18+ content behind an age verification check. Since there's no way they can verify that users (that consume content from their API) are of appropriate age, they just dont include them.

I can't believe that that's entirely correct, I still see some thumbnailing services, such as vxtwitter, fxtwitter, still functioning in this case. That said, I also note it started occurring on nitter.net itself a few days ago while it only seemingly just started hitting some mirror sites, so I suppose it's possible that it's a slow rollout, but it's still also possible these other sites are doing something that nitter isn't

[AlyoshaVasilieva]

IIRC based on some warnings I've seen when using yt-dlp plus other stuff:

• The new graphql API won't show 18+ tweets to guest users (aka nitter)
• the old api that's getting shut down does, but only in some regions

Edit: nitter.net uses more graphql endpoints than most instances because it's running a dev version

[crockpoot]

Will the workaround be added to the browser instances?

[ultrajae]

IIRC based on some warnings I've seen when using yt-dlp plus other stuff:

• The new graphql API won't show 18+ tweets to guest users (aka nitter)
• the old api that's getting shut down does, but only in some regions

Edit: nitter.net uses more graphql endpoints than most instances because it's running a dev version

Idk,.
It seems like Twitter's API has changed

I haven't found one instance that works now.
I tried many of those not updated.

[PrivacyDevel]

IIRC based on some warnings I've seen when using yt-dlp plus other stuff:

• The new graphql API won't show 18+ tweets to guest users (aka nitter)
• the old api that's getting shut down does, but only in some regions

Edit: nitter.net uses more graphql endpoints than most instances because it's running a dev version

Idk,. It seems like Twitter's API has changed

I haven't found one instance that works now. I tried many of those not updated.

That is definitely the case. I tried them all and a few unofficial ones. And some of the ones I tested have not been updated in months.

Mine has my workaround already applied and works tho.
https://nitter.privacydev.net/

[roryyamm]

How does the workaround… work? Whose credentials are used?

[PrivacyDevel]

How does the workaround… work? Whose credentials are used?

The administrator of the respective instance needs to create a Twitter account, sign in and then put their session information into Nitter's configuration file. This session information will then basically be shared for all users. It's the instance's Twitter account, if you will.

As an end user, you shouldn't need to do anything.

[roryyamm]

Won't that lead to severe rate limiting, though?

[PrivacyDevel]

Won't that lead to severe rate limiting, though?

It seems like that does indeed happen sometimes. But for the most part it seems like it's actually working fairly well for my instance. But I am not yet aware of any other satisfying workaround for that problem. Forcing a user to login and get tracked is not really a satisfying solution for me.

I see the following general solutions for this problem, personally:

1. rate limit the end users to make it so that the instance works more reliably overall
2. create more accounts and make the server juggle between different accounts / sessions as needed
3. maybe try to cache things more aggressively
4. a combination of those options that I just listed

[crockpoot]

Luckily, the workaround works but it's unfortunately very slow.

[ultrajae]

indeed, slow. probably rate limited already I guess unfortunately.

I am waiting so far 5 minutes for a vid clip to play. gonna have to give up

At least the tweet comes up tho,
A+ on effort

TYVM

[roryyamm]

Forcing a user to login and get tracked is not really a satisfying solution for me.

What about a voluntary system - ask for a login to increase the rate limit, but fall back on a set account if no login is provided?

I use Nitter mostly for its RSS feeds. Since I have a lot of NSFW accounts as feeds, some of whom tweet frequently, the frequency by which I ask for tweets is probably a major reason why the instance is so slow. If I could somehow pass my own credentials when fetching those RSS feeds, even if it meant I was tracked, I'd do it if that meant a faster or more reliable system with less caching for all.

Perhaps users willing to forgo the non-tracking nature could put a query string at the end of the URL for the RSS feed, containing the exact ct0, auth_token and csrf-token, and the server could use those credentials instead of its own if all are present.