…ed some new properties. Not tested yet, just keeping track of my work.

…Boolean parameters get sent along properly in TwitterOperations. Some trace statements.

…et an int.

…erOperation (not really sure why the interface even existed before if it wasn't being used there).

Started a Twitter Streaming operation handler. This would use the Twitter Streaming API as opposed to the REST API. Basically lets you get notified rather than polling. For now it'll grab the appropriate data and convert into objects, but it needs to actually do something with them so it's not ready for use yet. For some reason Twitter will randomly return a 401 Unauthorized most of the time, and then spontaneously work. I cannot figure out why this happens. When it does happen, a keychain powered login box appears, but nothing works. There's no indication if this is on my end or Twitter's end. I've also tried using their OAUTH generator to get a curl command straight from them -- this has the same weirdness. Unless it starts magically working perfectly, I'm not sure the streaming API can be trusted...

… objects that returns a StreamingObject that has a type and one of the objects (most often a Twitter Status). New Twitter Streaming Event that has strongly-typed streamObject. TwitterStreamingOperation actually dispatches a Twitter Streaming Event when it has new data (once for each piece of data, not necessarily each chunk of progress).

This seems pretty stable right now, but there are a lot of data types and so far I've only seen "friends" and status messages come through.

Also, the "Count" parameter isn't available on User streams, so catching up via the streaming API seems impossible at this point. Sigh.

…n 200. Some other checking.

…hen suddenly stopped working. Nothing seemed to fix it except changing to https. Not sure if that's a placebo or if it actually fixed it.

Updated API