Monthly Archives: May 2009

Notes on Spinn3r’s Datacenter Migration to Softlayer 2

About two weeks ago we completed a pretty big project to migrate Spinn3r’s operations from ServerBeach over to Softlayer. The entire project, from start to finish, too just over one month. I’m also proud to note that not a single customer noticed any downtime or any issue with our migration. It cost a bit more [...]

Papers using Spinn3r Data from ICWSM 2009 0

Additional papers based on the Spinn3r/ICWSM dataset have been published. It seems I have a lot of reading to do! Flash Floods and Ripples: The Spread of Media Content through the Blogosphere This paper is based on the Spinn3r data set (ICWSM 2009), which consists of web feeds collected during a two month period in [...]

Spinn3r talk from ICWSM 2009 0

Here are the slides from my talk at ICWSM 2009. The talk went really well I think. Lots of great questions from the audience. The winning paper, “Flash Floods and Ripples: The Spread of Media Content through the Blogosphere”, was very good and I’m excited to read it in full when I get a few [...]

Spinn3r 3.0: New Features, New Architecture, New APIs – More Goodness 0

I’m proud to announce that we have just released Spinn3r 3.0 after more than a year of development. This has been quite a lot of work based on feedback from our customer base and ships with some really awesome functionality. Most of this time has been spent on architecture but a good deal has been [...]

Using Spinn3r to Track Swine Flu 0

Want to track Swine Flu outbreaks? Just use Spinn3r! Courtney Corley and Jorge Reyes are two University of North Texas graduate students who have been using Spinn3r under our research program to mine data about the recent Swine Flu outbreak. The Denton Record-Chronicle has the story: “We’re looking at what people write in blogs, Web [...]

Unreliable VPN Code to Detect Bugs by Fuzzing. 0

I had an interesting idea today to find bugs in networking code. Design a VPN that deliberately introduces network packet corruption. One could introduce a tunable to corrupt a certain % of packets. For example, you could bring up a MySQL master/slave on your ethernet network and then launch the VPN to transfer the replication [...]