Twitter API access is a bit of a chore for the uninitiated so I will probably create a howto for it, but in general the APIs that are interesting already have a Python package associated with them. Twitter itself uses an oauth scheme in order for you to gain access. Others require a registration and they provide you with a unique key. Some are open and simply require that you know the URL.
There are a variety of API calls that I use. There are no limits to web, command line, or API access. The login restriction is a bit of a bother - you get one account and it's got full permissions for the system, so you can only share your work with very trusted associates. 500 meg is enough space for about two million tweets or four million lines of IRC logs - the limit is a barrier to datacenter users, but not to someone doing studies of Twitter, IRC, or any other human generated, time stamped data. Only two of those that appear to matter are the 500 meg a day cap on data and the lack of individual userids. Splunk has a free version of their system but it has a variety of limitations. The transforms I publish use either local resources or third party APIs and the only limits are those imposed by the API providers themselves. You get very limited access to the Maltego community transform server and you have to solve a captcha every three days in order to continue using the system. If that's too steep for you the following will work: Maltego costs $650 and the minimum Splunk license is $5,000. I am new to Python, but it seems to be the language to use for the set of problems I enjoy solving. Python is the favored tool of the guys from Paterva, Splunk is written in it as well as many of the free Splunkbase apps, and the Natural Language Tool Kit project uses it, too. The other tool I use heavily is Splunk, which is an enterprise grade datacenter logging application. This repository is a collection of things I have written for use with Paterva's Maltego OSINT & forensics application.
0 kommentar(er)
