Here's a way to easily pull down the data without all of that extra gui stuff: https://api.twitter.com/1/statuses/user_timeline.xml?screen_name=googuns_prod&cou

Here's a way to easily pull down the data without all of that extra gui stuff: https://api.twitter.com/1/statuses/user_timeline.xml?screen_name=googuns_prod&count=200&trim_user=1 https://api.twitter.com/1/statuses/user_timeline.xml?screen_... The maximum is 200, but you can move down the line by using since_id or max_id optional parameters. 'xml' can be replaced with 'json' or 'rss' if you'd prefer a different format. Looking over the data briefly reveals the additonal fact that the 'source' field is populated with a link to Google. That, combined with the other accounts including one that outright says it's associated with google on its profile. So this is either google maybe doing some sort of recruiting thing, or somebody that wants us to think it's google for whatever reason. One guess is that the account name could mean Google User Notification Service. Additionally, the tweets are published at a (more or less, this is the web) regular interval. Always around the HH:M9:30, HH:M0:00, and HH:M4:30 and HH:M5:00 marks. As stbullard speculated (https://news.ycombinator.com/item?id=4697813 https://news.ycombinator.com/item?id=4697813), there could be two instances of whatever this is running, publishing every 5 minutes independently, with one instance having the code baf200000000 associated with it and another having the id of 2350000000. Note that the length of these two are different- the former is 12 while the latter is 10. This could mean a variety of things regarding the format in which the data is published, or variance in the data itself. It might be worth looking at the unique parts of the 235 ones as color. If anyone can pull these tweets down into a single file and share them that would be amazing.