Your timeline in each country contains the 3200 most recent tweets/retweets you produced. It appears though that on an ongoing basis your timeline in each country is constructed by the respective local servers. Periodically though (once per week) Twitter synchronizes all local servers between them. Nevertheless, most of the time – 6 days out of 7 – what you see is how the local server sees your account.
This means that if you created your profile in the United States and most of your followers are from the US then US servers (home) are going to crawl your account very frequently, say every 4 seconds. Also, if you are from US but have some active followers in Japan that trigger update requests about your profile, then Japanese servers will crawl your account every 4 seconds as well. Countries where you have no followers (exotic) and trigger few requests on your account appear to crawl the respective client profile less often, at a frequency not higher than once every 20 minutes. If a country is exotic with respect to an account but the accounts’ popularity increases there, as result of the surge in update requests such exotic country will turn into home and its servers will start crawling the account very frequently as well. The minimum amount of followers/interactions required for an exotic country to become home is not clear though.
But how does this affect hidden tweets? The main consequence of this difference in crawling frequency is that if an account is constantly retweeting new tweets and undoing them, local servers (home) will catch these retweets and count them as more recent posts (even if they are deleted afterwards). If an account receives about 3000 or so temporary retweets in 24h then any tweets posted before these retweets were received will be archived by local servers. Servers in exotic countries, on the other hand, that crawl your profile less frequently will miss most of the temporary retweets and catch, say, only 200 out of the 3000 you received in the last 24h. Hence why your most recent tweets will not be archived, because the post volume will never hit 3200 in the eyes of exotic servers.
Example: Client 1 is from India and has 2 accounts, @myparodyindia1 (audience demographics 80% US, 10% Asian, India included) and @clothesparody2 (audience demographics: 100% US, Canada, UK, Australia & <1% Asia, India ). Both accounts receive temporary retweets which are undone after a while but the tweets of @myparodyindia1 have been archived both in India and US. The recent tweets of @clothesparody2, on the other hand, have been archived in US but are visible in India (which is an exotic country with respect to this account).
The whitelist feature allows for users to keep certain retweets on their profile permanently so that they do not get deleted at every unretweet cycle.
To whitelist a retweet will require the tweet’s ID. You can find the tweet ID by clicking on the tweet and it will be the sequence of numbers at the end of the web address (shown above). Make sure that at this point you have not retweeted the tweet yet. Now copy the 18-digit number, sign in on spamcleaner.co website and paste it into the given box labeled insert tweet id (shown below).
After you paste the number, click on “add to retweet whitelist.” Now you can go back to twitter to retweet that tweet and it will never be unretweeted from your timeline.
Protection refers to the Spamcleaner feature located at the bottom of the user panel. It was created to help users delete unauthorized tweets posted from their accounts in periods of inactivity.
The feature is intended to be activated when you’re not using Twitter (because sleeping, in class, on vacation etc) but have your account available on Tweetdeck/Hootsuite for peers to retweet from it.
Now and then the common Tdeck/Hootsuite password is leaked to unaffiliated third parties (hackers) who can use it to mass retweet their own accounts or, worse, to make offensive/false statements on your behalf that can alienate followers and damage your reputation.
Because retweets are cleaned by spamcleaner, unauthorized tweets would normally remain on the timeline until the user deletes them. And if the user is offline for one reason or another while this happens, such unauthorized tweets can stay up for hours, even days triggering hostile attacks from nonfollowers and followers alike. With protection, on the other hand, unauthorized tweets would stay up for at most 10 minutes and the damage can be negligible.
To activate protection you have to set a time interval for which you want it to be on. The image below shows how to set protection for the next 4h (from 5am to 9am). You first set the starting time, to do so click on the from field, a calendar will appear with hours displayed on the right. Pick a time and do the same with the to field (end time). Now click on activate protection and you should see a green notification saying that the date range has been saved.
Now that protection has been activated all tweets posted in the saved time range will be deleted right after being posted. If you want to tweet before the saved end time (9am in the above example), all you have to do is click on the turn off protection button and new tweets won’t be deleted anymore.
The scope of this blog will be not only to keep users up to date with the latest Spamcleaner developments but also to provide actionable insights on how to empower you as a Twitter user.
It is no secret that right now our priority group are high-end profiles with a solid following (>100k) and a high volume of interactions. On Twitter, as elsewhere, giving is the secret to getting ahead. An intensive exchange of shares (retweets) can lead though to a dilution of one’s presence in their own timeline which is, in turn, perceived as spam by followers. This is where spamcleaner comes into play. You can clean retweets every 5-10 minutes to pave the way for hundreds of exchanges per day and a higher growth per retweet.
In addition to that, we added new features to delete tweets posted in a to-be-defined timeframe (Version 1.1). This allows users of platforms like Tweetdeck and Hootsuite to limit the amount of unauthorized tweets posted from their accounts in case the common Hootsuite/Tweetdeck account they are using is compromised when they are away.
A new version (1.2) will be released the first week of January. For suggestions use the comment section below.