codejoust

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/]

Was looking for some backgrojnd and found an overview presentation [pdf]: http://netlipse.eu/media/77918/11nwm-bratislava-lex-pepping-...

We're using Tropo.com, pretty easy. Otherwise it's just mysql/mysqli/php/apache. Pretty straight forward.

Something similar with syntax hilighting and sounds can be found at http://codetyper.tk/

How meta? A poll to ask about the number of polls.

One good thing about polls is they do bring a good discussion and a nice demographic insight, when they are not overused.

How about using something like BSON to reduce overhead? (and writing it in C would help). http://bsonspec.org/

Running wordpress and PHP, nonetheless. Wordpress isn't light on resources.

1: You can turn off location data.

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.

Try using another database: I've implemented optional support for ipinfodb.com, however, the code is fairly modular to add another service.

http://codejoust.github.com/session.js/ipinfodb_demo.html

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.

Official demo: http://codejoust.github.com/session.js/

I believe the earlier comments have merit, thus I've renamed the library.

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.

Google provides it as an extra for the JSAPI, no telling how long it will last, though.

I liked the idea, and had already needed parts of such a library, so I put together some stuff and made a free/open-source version.

https://github.com/codejoust/visitor.js

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.

Winning: http://chattanooga.jpg.to/ It works pretty well, although there are some oddball results.

How about running the facebook javascript in a sandbox? Such as proxying the document.createElement and document.getElements* methods for the initial script while breaking it for everything else?

Totally agree with boredom is a choice. My parents don't believe in boredom... if you say you're bored, there's always housework, books to read, things to do. It's just a question of what you want to do.

I still do the same for almost all CRTs. I'm pretty young though. The most annoying was waiting for the ACT to start while hearing a loud super high-pitch electronic whine went on every five seconds.

My var story was a little harder scoping issue where a variable held the information for a pending call. It would asynchronously process the call, then mark the call as completed. Well, if there were more than one call going through, the callback was only getting one record, causing it to repeat the call about five times before I caught it and fixed the scoping.