Am 21.03.2013 um 05:08 schrieb Frank D <fdows...@gmail.com>: > With Twitter switching to the 1.1 API and shutting down 1.0, I've > upgraded Adium's support to work with it.
Yay! Thanks a lot. > […] > * I forked STTwitter on GitHub on my account, we could (and maybe > should) fork it on the Adium account. I can think of two reasons why it could be beneficial to fork it on the Adium account: 1. everyone on the team can easily modify it, 2. they might appreciate our official endorsement of the framework (especially with all the improvements you made). > 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. No objections > 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! Good idea! I'll try to help though I have to say I only use a very small part of the Twitter functionality. Am 21.03.2013 um 13:14 schrieb Moses Lei <b...@moseslei.net>: > 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 Seems like it's a bit large of a dependency for a service hardly anyone uses. Plus, someone would need to maintain it and I feel like we should ship services we are committed to maintaining (apart from those in lib purple). Cheers, Robbie
