It looks like within the past 8 months or so that Facebook has changed to format of their data dumps to not truncate messages, as their previous data dumps were previously structured as one giant messages.htm file which would be difficult to parse and seems like it had missing data for certain cases.
I built a elasticsearch importer for fb messages and a simple web frontend that did this pretty well for many many megabytes of messages. Wouldn't mind cleaning it up if people were interested in using it. [edit: will upload here later: https://github.com/iainnash/messenger-explorer/]
2: None of this is being stored, beyond a cookie. Of course, you can call back to the server with that data, but the server has your IP address, which is where the location data came from.
I added in support for http://ipinfodb.com/ (see bottom of README) which might be better than Google's api, although you need to register for an API key.
You might want to give that a shot.
I thought about doing that. I've used a lot of coffeescript in the past, but I just didn't see it being a big advantage here.
The biggest issue with using CoffeeScript here is that I wanted control over the syntax as I wanted to have less code.
CoffeeScript (generated) really creates more code than what it's worth.
No. And the recently-posted paid visitor.js site does have a few advantages, most being that this is using pure javascript, while they have the server side doing most of the heavy lifting.
I built a open-source version similar to this library for my own use using javascript browser checks and the google jsapi geocoding. It's on github at https://github.com/codejoust/visitor.js.
I've done a considerable amount of work in subprocess. It's API isn't amazing, but it does have quite a few great features and once you spend a little time with it really isn't too bad. Some of the piping features, along with shell arguments work quite well.
