eionrobb at gmail.com
Mon Jan 5 20:25:34 UTC 2009
>> one solution would be to just switch to the Pidgin Facebook plugin,
>> since it implements its own HTTP stack and gets us completely away
>> from whatever weird internals are messing this up. It' s a pretty easy
>> switch, and as far as I know it's feature equivalent. It's sad to me
>> to see my rather elegant (if I say so myself) Facebook implementation
>> get trashed...but that's no reason not to do it.
> I don't think switching to Pidgin is a great move, since we implement nicer
> the "protocol", as well as the extra benefits of the Info window, etc. It's
> an option, of course, and the interaction between Safari and Facebook is
> really annoying.
Just thought I'd jump in and say "hi".
Is it worth giving the libpurple Facebook plugin a shot, even as just
a seperate plugin -- similar to how you guys gave the msn-pecan a go?
>From what I'm told, there are a lot of issues/feature requests on your
bug tracker that could be closed just by switching over.
I completely agree that the Adium plugin code is a lot more elegant,
but the libpurple plugin has had a lot of TLC by Mark Doliner and
Casey Ho and is on-par with a lot of the other protocols now (If you
consider that a good thing ;) ).
It might make more sense to consolidate our efforts instead of working
on two seperate protocol implementations... both of our sets of users
would probably benefit from the merge.
Anyway, that's my thoughts. I'm happy to work with you guys in making
an AdiumLibpurplePlugin wrapper if you like?
More information about the Adium-devl