Twitter2irc
From ThorxWiki
(Difference between revisions)
m (seso) |
(seso) |
||
Line 1: | Line 1: | ||
+ | {{TOCright}} |
||
notes for a review of different twitter<->IRC gateways. |
notes for a review of different twitter<->IRC gateways. |
||
Line 4: | Line 5: | ||
== bitlbee == |
== bitlbee == |
||
+ | Pro: very well known |
||
+ | Pro: multi-protocol, multi-account |
||
== tircd == |
== tircd == |
||
+ | Pro: displays users "real names" on @mentions (also a con: increases verbositude) |
||
== minbif == |
== minbif == |
||
+ | Pro: multi protocol. (multiaccount is unknown?) |
||
Con: libpurple has heavy dependancies in debian at least (X crap!! :( |
Con: libpurple has heavy dependancies in debian at least (X crap!! :( |
||
== twirssi == |
== twirssi == |
||
Con: chews the CPU |
Con: chews the CPU |
||
+ | Con: uses an irssi window, but otherwise appears unrelated to any interface settings from irssi. (ie, colours, logging, etc, all have to be setup anew) |
||
+ | Pro: loading full conversations on the fly |
||
+ | Pro: nice colouring of hashtags and @mention names |
Revision as of 14:55, 5 September 2012
|
notes for a review of different twitter<->IRC gateways.
Pros and cons of each, plus what each does that the others do not.
bitlbee
Pro: very well known Pro: multi-protocol, multi-account
tircd
Pro: displays users "real names" on @mentions (also a con: increases verbositude)
minbif
Pro: multi protocol. (multiaccount is unknown?) Con: libpurple has heavy dependancies in debian at least (X crap!! :(
twirssi
Con: chews the CPU Con: uses an irssi window, but otherwise appears unrelated to any interface settings from irssi. (ie, colours, logging, etc, all have to be setup anew) Pro: loading full conversations on the fly Pro: nice colouring of hashtags and @mention names