Twitter in Adium

[Frank D]

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

[Thijs Alkemade]

Post by Frank D
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].
* 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 938 bytes
Desc: not available
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20130321/356e7cf4/attachment.bin>

[Moses Lei]

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

Post by Thijs Alkemade

Post by Frank D
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].
* 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20130321/4d2ff0bf/attachment.html>

[Robert Vehse]

Post by Frank D
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.

Post by Frank D
[?]
* 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).

Post by Frank D
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

Post by Frank D
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.

Post by Frank D
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

[Anon]

Post by Frank D
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
Both seem immature in code quality and completion. I decided to go
with the cleaner STTwitter[1] rather than the synchronous FHSTwitterEngine[2].

Let me tell you that I know the guy who wrote FHSTwitterEngine. He's 16.
He wrote FHSTwitterEngine in 5 hours.

[Evan D. Schoenberg, M.D.]

Post by Anon

Post by Frank D
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
Both seem immature in code quality and completion. I decided to go
with the cleaner STTwitter[1] rather than the synchronous FHSTwitterEngine[2].

Let me tell you that I know the guy who wrote FHSTwitterEngine. He's 16.
He wrote FHSTwitterEngine in 5 hours.

That's awesome that he is 16, coding, and contributing to open source.

-Evan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20130404/30f71f2a/attachment.html>