Modify

#286 closed enhancement (wontfix)

xfire support

Reported by: bender647 yahoo.com Owned by:
Priority: pony Milestone:
Component: BitlBee Version: 1.0.3
Keywords: xfire Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description

A lot of my gamer friends are getting hooked on xfire IM. There appears to be an open source xfire library under development for a Jabber to xfire gateway at http://xfirelib.sphene.net/wiki/show/XFireGateway. It would be great if bitlbee supported xfire directly.

Attachments (0)

Change History (12)

comment:1 Changed at 2007-05-21T01:44:06Z by bender647 yahoo.com

Working xfire plugin for gaim, version 0.5.8 may be relevant (version 6 rewritten to Gaim 2.0 API):

https://sourceforge.net/projects/gfire/

comment:2 Changed at 2007-11-05T09:43:32Z by Jochem

I'd love xfire support too.

comment:3 Changed at 2007-12-04T00:06:37Z by wilmer

Milestone: 2.0

comment:4 Changed at 2009-01-06T05:55:07Z by lucash

I wish bitlbee supported xfire

comment:5 Changed at 2009-05-05T06:32:58Z by NaiveMonarch

Old ticket, but I figured I'd add my support for the xfire protocol, I'm so sick of pidgin.

comment:6 Changed at 2009-06-30T17:26:06Z by me@…

I'm going to attempt this, I found gfire's source and used it to write a Ruby XFire class, so I have a bit of experience with the protocol (and the C++ source to gfire is a plus).

Right now I'm using pidgin :P

comment:7 Changed at 2010-06-07T02:06:05Z by anonymous

Any luck with your attempts me@...? I'd really like to see support for this too!

comment:8 Changed at 2010-06-07T15:57:31Z by wilmer

If you use the BitlBee libpurple branch you should be able to use the gfire module mentioned above without any changes.

comment:9 in reply to:  8 Changed at 2010-11-11T15:50:58Z by anonymous

Replying to wilmer:

If you use the BitlBee libpurple branch you should be able to use the gfire module mentioned above without any changes.

how so?

comment:10 Changed at 2011-04-27T12:34:01Z by info+bitlbee@…

any progress to this?

comment:12 Changed at 2014-07-07T13:17:51Z by dx

Resolution: wontfix
Status: newclosed

Closing all protocol request tickets.

For most of the requested protocols, it's likely we won't have time and/or interest to implement them, and some tickets have stayed open here for years when they have libpurple implementations, or even as third party plugins. Implementing protocols in the core is far from a priority nowadays, although I hope we can make it easier to write third party plugins. As always, anyone who is interested in implementing bitlbee plugins for these can do so, and we're willing to help (join irc!)

In this particular case, there is a libpurple implementation, see ​http://wiki.bitlbee.org/HowtoPurple

Modify Ticket

Action
as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.