2/ If you've been following me for a while, you probably know my broad course trajectory. It's not terribly unique. In agreement with Herbert Simon, I want to design tools that better allocate our limited attention, the very stuff which determines our lives.
-
-
Show this thread
-
3/ You've also probably seen hints at the vision that's in my head. But, translating that will take time and a course heading is not enough. So, the first thing I want to do — my first objective — is, > To make Twitter data more accessible to researchers.
Show this thread -
4/ If you follow me, there is a good chance you're into statistics, machine learning, or data science. But, if you're an academic working in isolation, you may not have time to experiment with the twitter API and set up the infrastructure for collection.
Show this thread -
5/ I want to build a simple interface so you can do that part quickly and on an ad hoc basis. I want to lower the barriers of entry, so that we can get more eyeballs on the problem.
Show this thread -
6/ To that end, my first key result will be developing, $ brittlewit sample | gzip > tweets.jsonl.gz This is the lowest hanging fruit.
Show this thread -
7/ The next key result will be developing, $ brittlewit filter --track="keywords,..." and, $ brittlewit filter --follow="handle1,handle2,..."
Show this thread -
8/ There are plenty of libraries that do this in [your favorite language] but they are designed for app building more than for researcher needs. I'll keep adding next steps to this thread as I go.
Show this thread -
9/ A very, very, rough draft is good to go! (Please star and follow on
@github if you're interested!) https://github.com/jbn/brittlewit pic.twitter.com/DO21eA9FH8
Show this thread
End of conversation
New conversation -
-
-
And that's why I follow you!



-
Thanks! Stay tuned!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.