TweetSweep — bulk delete for X

Old Tweets Still Showing Up in Someone Else's Replies After I Deleted Them

A refresher on deleted posts appearing in reply threads of the people you show up in, how long they'll stick around before disappearing, and if there's anything you can do about it.

On the left, disordered stacks of social post cards lie scattered and interlocked around a broken chain link; on the right, neat stacks of social post cards sit beside a single intact chain link.

Why Are Your Deleted Tweets In Replies?

X, for instance, will delete a tweet you post from your profile and search results and no longer show it in the timeline of people following you. However, if that tweet is in reply to another user's tweet the thread of conversation does not completely fold. The other person's response remains, and in the space your post occupied, X occasionally offers a placeholder: a grayed-out line saying "This tweet has been deleted" or -- in some views -- your words are still there, albeit truncated. It isn't a bug — that's simply how X interprets threaded conversations when one person deletes their part. It places the importance of keeping the thread readable rather than hiding every trace of the deleted post.

The same goes for cached versions too i.e you will see only partial view of site. Although the server is still running your tweet has been deleted, but if you had someone else view this thread before deleting that full text could show in their browser or app cache for hours or days. Quote tweets that referenced your deleted tweet will remain on the web version of Twitter, showing your initial Tweet collapsed within each quote. It deleted your post from your own timeline, but it did not retroactively erase it from every context in which it was displayed or cited.

The duration of visibility for deleted mentions

X's Response to Deleted Tweets in Replies Basis Your Twitter Visibility as a Predictive Tactic Over on the other person's profile, the placeholder would remain indefinitely in a direct reply thread — it becomes part of thread history. The real content of the post you deleted, however, usually vanishes from live view within a few minutes of being deleted (although the text may hang around in the quoted preview for up to 24 hours). Deleted tweets can linger for days or weeks (depending on the refresh cycle) on third-party aggregation sites that archive X posts, like Nitter instances or syndicated feed readers.

X´s own search index may react otherwise. Tweet posts can take some days to be completely wiped from the search system even after you delete a tweet. If someone were to use the search operator "from:username" with your handle during that window, the deleted post will still show up in results and they can then open the thread and see you in reply context again. That was a caching delay, not a recovery mechanism, but you can have your old post accessed in someone's reply chain for up to a week after it is deleted.

What You Can Do About It

If your deleted tweet is in a reply thread to someone else that other people are not seeing and you want it totally gone, you really have nowhere else to turn. Hence, the other persons reply you cannot delete — that is theirs. You can request the person who commented to edit or delete their reply and remove that entire subthread. A ridiculous demand quite frankly, and it does not even make sense because this is rarely possible because the defendant doesn't know his victims or he/she/they might not want to call attention to themselves. The better option for such situations would be to utilize the support system of X with the help of which a thread could be reported if the context is harmful (like harassment or doxxing) but reporting a thread because your deleted post shows up in it in extremely rare cases; threads are removed.

The safest action is to take away the other person's ability to locate and view the thread in context. You have 3 tweets on the next two when your wrote is why this reply block that they contain your tweet. It does not erase the thread from their cache or within the reach of third-party archives, The blocking simply means that you are going to prevent them to see the thread when they log in on X. Blocking also does not remove knowledge the blockee already had of the original post. If you want to manage this kind of situation proactively, a bulk delete tool like TweetSweep could help by allowing you create a rule for deleting any reply after a specific date, as that would reduce the number of potential threads where your posts are kept inside someone else's reply chain.

The Permanence of Third Party Caches and Archives

Third-party services like archive. org, Google cache and specialized X scrapers which do not depend on X's deletion signal By removing a tweet, X sends a removal notice to search engines & API partners but not every service respects this. Google can take weeks to wipe its cache, and some archiving sites never remove the content in the first place. In case someone had the time to run it on a Wayback Machine or used an Archiver like I do, you'll probably still find a copy of the thread with your post as it stood before you deleted your account. These copies are beyond X's control and will persist, irrespective of any actions you take on the platform.

This type of archival will only be avoided if you delete the post before it is archived. The minute you actually archive it, it's permanent. If you are now dealing with a tweet that was released long ago and is still visible in some third-party cache, you can request its removal from Google through the search engine's outdated content removal tool—using URL of that cached page. For archive. org adheres to a policy in which you may submit a removal request, but they are not obligated to process your removal request for whatever reason. This is exactly why the best approach is to simply purge old replies as part of your regular clean-up process rather than waiting for engagement from a specific thread.

How to Prevent Future Appearances

If you want to ensure that your deleted tweets will not start appearing in people replies, you have to adjust your deletion practice. Deleting individual tweets as they pile up is insufficient, yet the threads remain in reply. Don — use a bulk deletion tool for all your tweetsRepliesCategorizing a tweet as a reply to someoneBuild in rules: automatically delete your replies older than X days. It contains your footprint in other people's threads. As another example — to establish a rule that deletes all your replies older than 90 days. This means that, even if someone replies to one of your old posts, it will not include your original message for very long.

You should also avoid interacting with accounts you do not own. In other words, every reply you make starts a thread that somebody else owns. Having less of those threads means less chances for your deleted posts to pop up in another persons reply chain. Also, it is advisable to set your account private before you start a big delete session. A private account will hide all your current replies from anyone who doesn't follow you, but it won't evade the posts from showing up in the replies of accounts who already followed both you and the replied-to person. You can expose the account to public once cleanup is done.

Ready to clear your timeline?

Pick the days you want gone and TweetSweep clears them from your X account — posts, replies, and reposts. Your first 10 deletions are free.

Sign in with X