Overdone jokes aside, I realized that I use Trowl too much, and I invested too much time in the app, to just toss it aside when Twitter decided to finally turn off version 1 of its API. That said, it\u00e2\u20ac\u2122s not a trivial process.<\/p>\n
Technical Details<\/strong><\/font><\/p>\n If you\u00e2\u20ac\u2122re interested, Trowl was originally built on requesting XML responses from Twitter. This was primarily because, at the time, .NET was best suited for parsing XML documents more than anything else. With the switch to API 1.1, Twitter completely dropped the ability to request XML responses, in favor of JSON. Luckily, .NET has become more fluent with JSON recently \u00e2\u20ac\u201c but it still meant going back through all my calls to Twitter and replacing the XML-based response\/parse logic with JSON-based response\/parse logic.<\/font><\/p>\n The Status of 0.8<\/strong><\/font><\/p>\n Okay, so, I\u00e2\u20ac\u2122m making this version 0.8 because I\u00e2\u20ac\u2122m essentially changing the entire foundation that Trowl is based on. There aren\u00e2\u20ac\u2122t any new features here, but it\u00e2\u20ac\u2122s a big enough infrastructure change that I felt justified in bumping up the version to 0.8.<\/font><\/font><\/p>\n I\u00e2\u20ac\u2122ve converted almost everything over to API 1.1 except the following:<\/font><\/font><\/p>\n\n