Lyfhael
anyone facing this issue?
I've got a candidate fix in my fork if you want to try that before I raise a pull request.
Doesn't work for me either
I got a true fix in my fork. They changed some things not only with X-Client-UUID but also the Request-Parameters and even the Response-Format. So it had to be rebuilt https://github.com/NietzscheKadse/XeetEntfernierer
This too doesnt work lol.
Worked for me and a friend, are you sure you are following the instructions? They are not the same as with this project. You have to go to your Replies-Tab on your X-Profile and then select the correct request (It HAS to be "UserTweetsAndReplies?v...."
https://imgur.com/a/f7dvNTe
If it really doesn't work, can you open an Issue in my fork and post the exact Error?
@NietzscheKadse thanks! It's working. But I had to update the var random_resource to use the one github provided on the first query.
@NietzscheKadse thanks! It's working. But I had to update the
var random_resourceto use the one github provided on the first query.
Thanks for that feedback! I will implement some small fixes over the weekend (i.e. solving the problem where it just skips some tweets when deleting), so I will look into that issue with random_resource too.
@NietzscheKadse @mateuspontes Didn't work for me either, but Idk how to update the var random_resource
@jattak47 Switch to the Replies tab, and open the console to get the headers.
The URL for UserTweetsAndReplies is something like this:
Request URL:
https://x.com/i/api/graphql/XXXXXXXXXXXXXXXXXXXXXX/UserTweetsAndReplies?variables=
The XXXX above is the "random_resource" variable value to use.
This too doesnt work lol.
Worked for me and a friend, are you sure you are following the instructions? They are not the same as with this project. You have to go to your Replies-Tab on your X-Profile and then select the correct request (It HAS to be "UserTweetsAndReplies?v...."
https://imgur.com/a/f7dvNTe
If it really doesn't work, can you open an Issue in my fork and post the exact Error?
wow this actually worked! tysm!!
This too doesnt work lol.
Worked for me and a friend, are you sure you are following the instructions? They are not the same as with this project. You have to go to your Replies-Tab on your X-Profile and then select the correct request (It HAS to be "UserTweetsAndReplies?v...."
https://imgur.com/a/f7dvNTe
If it really doesn't work, can you open an Issue in my fork and post the exact Error?
I'm still getting the same error even when pulling the variables from the user tweets and replies section. Unsure of what's up here
This too doesnt work lol.
Worked for me and a friend, are you sure you are following the instructions? They are not the same as with this project. You have to go to your Replies-Tab on your X-Profile and then select the correct request (It HAS to be "UserTweetsAndReplies?v...."
https://imgur.com/a/f7dvNTe
If it really doesn't work, can you open an Issue in my fork and post the exact Error?
I recorded the authorization, client_tid and random_resource from the "UserTweetsAndReplies?v...." request (while on the Replies tab of my profile) ... Now instead of getting a 404, I the following 400 error:
(fetch_tweets) Network response was not ok, status: 400, retrying in 20 seconds VM615:145 {"errors":[{"message":"The following features cannot be null: payments_enabled","extensions":
Am I overlooking something or did X change things around again? Thanks
*** Edit/Update ***
In addition to the above, I was able to get NietzscheKadse's fork working by adding the following:
Append this to the features strings:
payments_enabled%22%3Afalse%7D
Add these parameters:
fieldToggles = &fieldToggles=%7B%22withArticleRichContentState%22%3Afalse%7D;
extensions = &extensions=%7B%22persistedQuery%22%3A%7B%22version%22%3A1%2C%22sha256Hash%22%3A%22b6ec8cdea6cd23fbb8078b0a7a1d888e6a9fa5df9d1cd15f3547db63f3e7eab9%22%7D%7D;
Update the final URL:
const final_url = ${base_url}${variable}${feature}${fieldToggles}${extensions};
Full disclosure:
I know very little about what I’m doing 😅
ChatGPT helped
It’s working now (as of June 24, 2025)
Someone more experienced should definitely vet this before putting it into production.
