RSS links for Twitter lists no longer working #961

Closed
opened 2023-07-20 18:00:28 -04:00 by jaswinder77 · 8 comments
jaswinder77 commented 2023-07-20 18:00:28 -04:00 (Migrated from github.com)

Earlier, for any twitter list https://twitter.com/i/lists/1234567890123456789 ,

there was a corresponding rss feed with the link https://nitter.net/i/lists/1234567890123456789/rss .

Is there a likelihood of that thing returning soon ?

Earlier, for any twitter list https://twitter.com/i/lists/1234567890123456789 , there was a corresponding rss feed with the link https://nitter.net/i/lists/1234567890123456789/rss . Is there a likelihood of that thing returning soon ?
zedeus commented 2023-07-20 18:03:52 -04:00 (Migrated from github.com)

It works just fine: https://nitter.net/i/lists/53645372
Do you have an example that doesn't work?

It works just fine: https://nitter.net/i/lists/53645372 Do you have an example that doesn't work?
Mr-Freewan commented 2023-07-20 18:19:01 -04:00 (Migrated from github.com)

Not this topic, but...hmm, just now, for example (any host):
https://nitter.nohost.network/elonmusk - tweets timeline is not available (no items found)
https://nitter.nohost.network/elonmusk/with_replies - with replies is available

Not this topic, but...hmm, just now, for example (any host): https://nitter.nohost.network/elonmusk - tweets timeline is not available (no items found) https://nitter.nohost.network/elonmusk/with_replies - with replies is available
avasilic commented 2023-07-20 18:31:04 -04:00 (Migrated from github.com)

I'm having the same issue as @Mr-Freewan . I got an alert from my monitoring platform just an hour ago. Version 2023.07.10-0bc3c15. Same error, no errors in logs, docker reports as healthy.

Edit 1: I've just restarted the container and got BadClientError: Bad client even before the Starting Nitter at .... message.

I'm having the same issue as @Mr-Freewan . I got an alert from my monitoring platform just an hour ago. Version [2023.07.10-0bc3c15](https://github.com/zedeus/nitter/commit/0bc3c15). Same error, no errors in logs, docker reports as healthy. Edit 1: I've just restarted the container and got `BadClientError: Bad client` even before the `Starting Nitter at ....` message.
ImTheDeveloper commented 2023-07-21 01:40:32 -04:00 (Migrated from github.com)

https://twitter.com/i/api/graphql/3JNH4e9dq1BifLxAa3UMWg/UserWithProfileTweetsQueryV2 will return:

{
   "data": {
       "user_result": {
           "result": {
               "timeline_response": {
                   "id": "VGltZWxpbmU6CgBdAAAAAFIvaMAA",
                   "timeline": {
                       "instructions": [
                           {
                               "__typename": "TimelineClearCache"
                           },
                           {
                               "__typename": "TimelineTerminateTimeline",
                               "direction": "TopAndBottom"
                           }
                       ],
                       "metadata": {
                           "scribeConfig": {
                               "page": "profileBestHighlights"
                           }
                       }
                   }
               }
           }
       }
   }
}

Same user with https://twitter.com/i/api/graphql/8IS8MaO-2EN6GZZZb8jF0g/UserWithProfileTweetsAndRepliesQueryV2 provides full response and tweets.

{
    "data": {
        "user_result": {
            "result": {
                "timeline_response": {
                    "id": "VGltZWxpbmU6CgBeAAAAAFIvaMAA",
                    "timeline": {
                        "instructions": [
                            {
                                "__typename": "TimelineClearCache"
                            },
                            {
                                "__typename": "TimelineAddEntries",
                                "entries": [
                                    {
                                        "entryId": "tweet-1668154996372697089",
                                        "sortIndex": "1682262476449644544",
                                        "content": {
                                            "__typename": "TimelineTimelineItem",
                                            "content": {
                                                "__typename": "TimelineTweet",
                                                "tweetResult": {
                                                    "result": {
                                                        "__typename": "Tweet",
                                                        
                                                        etc....
https://twitter.com/i/api/graphql/3JNH4e9dq1BifLxAa3UMWg/UserWithProfileTweetsQueryV2 will return: ``` { "data": { "user_result": { "result": { "timeline_response": { "id": "VGltZWxpbmU6CgBdAAAAAFIvaMAA", "timeline": { "instructions": [ { "__typename": "TimelineClearCache" }, { "__typename": "TimelineTerminateTimeline", "direction": "TopAndBottom" } ], "metadata": { "scribeConfig": { "page": "profileBestHighlights" } } } } } } } } ``` Same user with https://twitter.com/i/api/graphql/8IS8MaO-2EN6GZZZb8jF0g/UserWithProfileTweetsAndRepliesQueryV2 provides full response and tweets. ``` { "data": { "user_result": { "result": { "timeline_response": { "id": "VGltZWxpbmU6CgBeAAAAAFIvaMAA", "timeline": { "instructions": [ { "__typename": "TimelineClearCache" }, { "__typename": "TimelineAddEntries", "entries": [ { "entryId": "tweet-1668154996372697089", "sortIndex": "1682262476449644544", "content": { "__typename": "TimelineTimelineItem", "content": { "__typename": "TimelineTweet", "tweetResult": { "result": { "__typename": "Tweet", etc.... ```
NicoBerlo commented 2023-07-21 06:35:39 -04:00 (Migrated from github.com)

It works just fine: https://nitter.net/i/lists/53645372 Do you have an example that doesn't work?

Old tweets show up in random order :
Rer_a

This account is updated many times a day normally :)

> It works just fine: https://nitter.net/i/lists/53645372 Do you have an example that doesn't work? Old tweets show up in random order : [Rer_a](https://nitter.net/rer_a) This account is updated many times a day normally :)
oystermon commented 2023-07-21 18:28:40 -04:00 (Migrated from github.com)

I have the same thing (jumbled up main tweets page), but I realised the tweets and replies page is in the right chronological order..

EDIT: Just updated my docker container and now it's in chronological order again.

I have the same thing (jumbled up main tweets page), but I realised the tweets and replies page is in the right chronological order.. EDIT: Just updated my docker container and now it's in chronological order again.
jaswinder77 commented 2023-07-22 01:45:29 -04:00 (Migrated from github.com)

Do you have an example that doesn't work?

This one shows me a "Forbidden 403" error:

https://nitter.net/i/lists/1663728475965100032/rss

> Do you have an example that doesn't work? This one shows me a "Forbidden 403" error: https://nitter.net/i/lists/1663728475965100032/rss
zedeus commented 2023-07-23 22:31:07 -04:00 (Migrated from github.com)

The issues described here are no longer relevant. The 403 error is on purpose, please use another instance for now.

The issues described here are no longer relevant. The 403 error is on purpose, please use another instance for now.
This discussion has been locked. Commenting is limited to contributors.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PAS/nitter#961
No description provided.