Why not keep MGTwitterEngine for StatusNet/Laconica? As far as I know, it still works, yes, since they are still on some variant of API 1.0?
Moses On Thu, Mar 21, 2013 at 4:56 AM, Thijs Alkemade <m...@thijsalkema.de> wrote: > On Thu, Mar 21, 2013 at 12:08:48AM -0400, Frank D wrote: > > With Twitter switching to the 1.1 API and shutting down 1.0, I've > > upgraded Adium's support to work with it. > > > > Since MGTwitterEngine hasn't been updated in over two years I went > > looking for a newer framework and found one listed on Twitter's dev > > site and I also found another one on GitHub. Both seem immature in > > code quality and completion. I decided to go with the cleaner > > STTwitter[1] rather than the synchronous FHSTwitterEngine[2]. > > > > Notes about STTwitter: > > * It supports xAuth, but Twitter says that the Adium > > account/application can't login through xAuth. > > * My biggest complaint about it is that the creator's commit messages > > which are mostly "misc". > > * I forked STTwitter on GitHub on my account, we could (and maybe > > should) fork it on the Adium account. > > > > I've also disabled Laconica/StatusNet support as it doesn't look like > > many people use it in Adium and upgrading the framework to support it > > would be more work. > > > > I've got the changes committed in both 1.7 and 1.6 and will transplant > > back to 1.5.7 after a little testing has been done. Let's find those > > regressions! > > > > 1: https://github.com/nst/STTwitter > > 2: https://github.com/fhsjaagshs/FHSTwitterEngine > > > > -- > > Frank > > > > Another downside buildbot just pointed out: this is assuming the modern > Objective-C runtime (it assumes automatically generated ivars for > properties), which is not available in 32-bit mode. > > I have not checked how much effort it would be to fix that (probably > relatively straightforward), but if it does come down to having to drop > 32-bit builds then I don't think we should release it with 1.5.7. > > Thijs >
