You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are scraping tweets by a certain query on a regular basis and storing the results into a database. Recently we found a rather small number of tweets not matching our query we pass to the twitterscraper in any way neither being a response to a relevant post. These tweets look like sponsored posts that possibly were not filtered out correctly.
However, while we have been running the twitterscraper every day for ~9 months since now and scraped nearly 5000 tweets, there were only ca. 16 unmatching tweets in our database, so the problem appears to occur highly sporadically. Some, but not all of tweets are also available in a backup from 2020-08-01, so the problem might be a bit older but still persists.
The text was updated successfully, but these errors were encountered:
We are scraping tweets by a certain query on a regular basis and storing the results into a database. Recently we found a rather small number of tweets not matching our query we pass to the twitterscraper in any way neither being a response to a relevant post. These tweets look like sponsored posts that possibly were not filtered out correctly.
However, while we have been running the twitterscraper every day for ~9 months since now and scraped nearly 5000 tweets, there were only ca. 16 unmatching tweets in our database, so the problem appears to occur highly sporadically. Some, but not all of tweets are also available in a backup from 2020-08-01, so the problem might be a bit older but still persists.
The text was updated successfully, but these errors were encountered: