I added some sleeps to the code with random waiting time values. In this case, for each action of deleting/unlike tweets, and for each time it searches for new tweets to check which actions to perform, I put a longer time in this wait, 30 seconds plus 0-30 randomized seconds, and for each cleaning action I put 3 seconds plus 0 - 10 random seconds.

In my case, which had almost 50k likes to clear (2009 until today), this prevented rate limit warnings which, after about 10, meant I spent around 24 hours without being able to clear any, or even perform actions without the bot.

The process takes longer, but it prevents you from getting any warning, so in the end, it ends up being much less time without the stops.

Additionally, I added an option to like some tweets. What was happening, before discovering this repo, I used services, when they were free, tweetdelet and so on, it turns out that, despite disappearing for me, the likes were still there, result, I had 50k likes as if they had no likes , heart deleted, but when another user opened my account, the like existed. In these cases, I changed the dislike function to first like the tweet, move on and, 3 waves after searching, remove the like. It worked ok.

And, because I'm a boring person, I also ended up adding a counter of how many actions he's already performed. I would also add an ETA, since it is possible to know in advance how many are theoretically left and, with the counter, know how many were made and the time elapsed.
Despite the randomness introduced, for large numbers of actions, there is a probabilistic average of expected times to complete.

Could you add these features to the repository? I believe that your code can be much more usable because it is free and with practically no real problems compared to existing services

Worked on about 40 likes, now just getting this for over a day now. =(

Getting the following error

line 2
var ua = navigator.userAgentData.brands.map(brand =>"${brand.brand}";v="${brand.version}").join(', ');

Since the twitter data we get also contains a like.js file with all our liked tweets, could we get the code to read from an archive imported here? Would be super helpful for unliking tweets made by someone who has since blocked you. The structure of like.js is quite simple:

"like" : {
      "tweetId" : "0000000000000000000",
      "fullText" : "Example text",
      "expandedUrl" : "https://twitter.com/i/web/status/0000000000000000000"
    }

Just grab the tweet ID, jam it into a POST statement to unlike, and that should work. This could also be a way to work around the issue of liked tweets not loading. Plus it should also allow for unliking tweets made by people who blocked you. That issue seems to be a result of quickly unliking many tweets. It's as if the API of the site itself refuses to load any liked tweets for a long period of time. For a while, due to my wiping several thousand tweets out, my account was not loading any other tweets or replies, so my profile looked completely empty. This remained for several days until finally one day it started showing more tweets that I could delete.