search

Rishikant181 / Rettiwt-API

A CLI tool and an API for fetching data from Twitter for free!
https://rishikant181.github.io/Rettiwt-API/
MIT License
363 stars 34 forks source link

RettiwtError: NOT_FOUND Tweet Fetch #584

Closed MDCYT closed 1 month ago

MDCYT commented 1 month ago

When trying to obtain the data of a tweet it says that it does not exist even though it does, it has been tried with a lot of tweets but each one of the tested ones says that they do not exist, that only affects when obtaining information of a tweet, but it does not affect when obtaining the information of retweets of a tweet.

I am currently using an authenticated account

imagen

Rishikant181 commented 1 month ago
  1. Can you provide me with the ID of a tweet which throws this error?
  2. Does the same error occur when fetching the details of a tweet without logging in (i.e, not using an API_KEY)?
MDCYT commented 1 month ago

  2. Due to some issues I can't check that right now.

Rishikant181 commented 1 month ago

Strange, it's working as expected on my end. But, the endpoint has a history of causing this issue from time to time, since this endpoint is not exposed directly in the web-app (the web-app uses a different endpoint for fetching details of tweet and it's a wasteful one since it also fetches the replies of the tweets). As a fail-safe, I'll implement the same endpoint as the one used by the web-app.

MDCYT commented 1 month ago

Yeah, I think the problem is that Twitter is blocking some of the requests on that Endpoint, it decided to host a copy of my program on another hosting and it works without problems. It must be that Twitter detects that it is a bot and decides not to show it, I suppose, the problem occurs in Railway but not in Bot-hosting.net (Another hosting)

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Rishikant Sahu @.> Sent: Friday, August 9, 2024 12:37:23 AM To: Rishikant181/Rettiwt-API @.> Cc: José Ortiz @.>; Author @.> Subject: Re: [Rishikant181/Rettiwt-API] RettiwtError: NOT_FOUND Tweet Fetch (Issue #584)

Strange, it's working as expected on my end. But, the endpoint has a history of causing this issue from time to time, since this endpoint is not exposed directly in the web-app (the web-app uses a different endpoint for fetching details of tweet and it's a wasteful one since it also fetches the replies of the tweets). As a fail-safe, I'll implement the same endpoint as the one used by the web-app.

— Reply to this email directly, view it on GitHubhttps://github.com/Rishikant181/Rettiwt-API/issues/584#issuecomment-2277186225, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP72BGS2SRVT2KX6PCQF4BTZQRIRHAVCNFSM6AAAAABMF46J5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZXGE4DMMRSGU. You are receiving this because you authored the thread.Message ID: @.***>

Rishikant181 commented 1 month ago

Twitter detects that it is a bot

Probably this, since the particular endpoint is not even utilized by the Web-App. I'll be switching it to the same endpoint as the one used by Twitter.

Rishikant181 commented 1 month ago

the problem occurs in Railway but not in Bot-hosting.net

Something I've notices is that a lot endpoints work weird when hosted on services like Railway, Vercel, etc. AFAIK, cloud platforms like GCP work alright. It needs extensive testing though.

In the meantime, I'm switching over to alternative endpoints.

MDCYT commented 1 month ago

It may be possible that the tweet endpoint you use (Hidden) is blocked almost automatically if it detects hosting provider IPs, to avoid scraping bots.

Maybe that's why services like Vercel, Railway, Heroku, etc. are blocked, but services like the one you mention or Bot-Hosting (which I'm currently using)

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Rishikant Sahu @.> Sent: Monday, August 12, 2024 8:52:24 AM To: Rishikant181/Rettiwt-API @.> Cc: José Ortiz @.>; Mention @.> Subject: Re: [Rishikant181/Rettiwt-API] RettiwtError: NOT_FOUND Tweet Fetch (Issue #584)

the problem occurs in Railway but not in Bot-hosting.net

Something I've notices is that a lot endpoints work weird when hosted on services like Railway, Vercel, etc. AFAIK, cloud platforms like GCP work alright. It needs extensive testing though.

In the meantime, I'm switching over to alternative endpoints.

— Reply to this email directly, view it on GitHubhttps://github.com/Rishikant181/Rettiwt-API/issues/584#issuecomment-2284052254, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP72BGS75UT7X3M3A3MF6PDZRC4ZRAVCNFSM6AAAAABMF46J5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBUGA2TEMRVGQ. You are receiving this because you were mentioned.Message ID: @.***>

Rishikant181 commented 1 month ago

It may be possible that the tweet endpoint you use (Hidden)

Remember the debacle when Twitter/X forced people to login to see tweets, which broke the functionality of embedded tweets in websites? This (hidden) endpoint is that endpoint which was setup to make embedded tweets work. That's why it's blocked almost instantaneously if scraper activity is detected, since this endpoint is not meant for logged in users.