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
Yes, yet another bug in Twitter's search. This time, it involves invalid usernames that look like domains. For example, https://twitter.com/search?q=from:archiveteam.org returns various Tweets containing links to archiveteam.org, which contradicts the search documentation (hidden behind "operators" on search-home). An account with the username archiveteam.org does not exist, so that search should not return any results. In fact, such an account can't exist: Twitter usernames must match [A-Za-z0-9_]{1,15} per Twitter's help page.
Because this unexpectedly produces tweets e.g. on snscrape twitter-user archiveteam.org, snscrape should directly block such invalid usernames.
The text was updated successfully, but these errors were encountered:
Yes, yet another bug in Twitter's search. This time, it involves invalid usernames that look like domains. For example, https://twitter.com/search?q=from:archiveteam.org returns various Tweets containing links to archiveteam.org, which contradicts the search documentation (hidden behind "operators" on search-home). An account with the username
archiveteam.org
does not exist, so that search should not return any results. In fact, such an account can't exist: Twitter usernames must match[A-Za-z0-9_]{1,15}
per Twitter's help page.Because this unexpectedly produces tweets e.g. on
snscrape twitter-user archiveteam.org
, snscrape should directly block such invalid usernames.The text was updated successfully, but these errors were encountered: