Twitter2irc
From ThorxWiki
(Difference between revisions)
m (+ todo list) |
m (improve lists) |
||
| Line 5: | Line 5: | ||
== bitlbee == |
== bitlbee == |
||
| − | Pro: very well known |
+ | * Pro |
| − | Pro: multi-protocol, multi-account |
+ | ** very well known |
| − | Con: relies heavily on a command channel, rather than IRCisms |
+ | ** multi-protocol, multi-account |
| + | * Con |
||
| + | ** relies heavily on a command channel with its own commands, rather than IRCisms |
||
== tircd == |
== tircd == |
||
| − | Pro: displays users "real names" on @mentions (also a con: increases verbositude) |
+ | * Pro |
| − | Pro: relies heavily on "natural" IRCisms (invite, kick, /msg, etc) |
+ | ** displays users "real names" on @mentions (also a con: increases verbositude) |
| − | Con: not a general IM solution. twitter/identica only |
+ | ** relies heavily on "natural" IRCisms (invite, kick, /msg, etc) |
| + | * Con |
||
| + | ** not a general IM solution. twitter/identica only |
||
== minbif == |
== minbif == |
||
| − | Pro: multi protocol. (multiaccount is unknown/assumed?) |
+ | * Pro |
| − | Con: libpurple has heavy dependancies in debian at least (X crap!! :( |
+ | ** multi protocol. (multiaccount is unknown/assumed?) |
| + | * Con |
||
| + | ** libpurple has heavy dependancies in debian at least (X crap!! :( |
||
== twirssi == |
== twirssi == |
||
| − | Con: chews the CPU |
+ | * Con |
| − | 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) |
+ | ** chews the CPU |
| − | Con: is not a general IM solution. twitter/identica only |
+ | ** uses an irssi window, but otherwise appears unrelated to any interface settings from irssi. (ie, colours, logging, etc, all have to be setup anew) |
| − | Con: twirssi specific solution only. |
+ | ** is not a general IM solution. twitter/identica only |
| − | Pro: loading full conversations on the fly |
+ | ** twirssi specific solution only. |
| − | Pro: nice colouring of hashtags and @mention names |
+ | * Pro |
| + | ** loading full conversations on the fly |
||
| + | ** nice colouring of hashtags and @mention names |
||
= TODO = |
= TODO = |
||
Latest revision as of 17:25, 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.
[edit] bitlbee
- Pro
- very well known
- multi-protocol, multi-account
- Con
- relies heavily on a command channel with its own commands, rather than IRCisms
[edit] tircd
- Pro
- displays users "real names" on @mentions (also a con: increases verbositude)
- relies heavily on "natural" IRCisms (invite, kick, /msg, etc)
- Con
- not a general IM solution. twitter/identica only
[edit] minbif
- Pro
- multi protocol. (multiaccount is unknown/assumed?)
- Con
- libpurple has heavy dependancies in debian at least (X crap!! :(
[edit] twirssi
- Con
- chews the CPU
- uses an irssi window, but otherwise appears unrelated to any interface settings from irssi. (ie, colours, logging, etc, all have to be setup anew)
- is not a general IM solution. twitter/identica only
- twirssi specific solution only.
- Pro
- loading full conversations on the fly
- nice colouring of hashtags and @mention names
[edit] TODO
- setup configuration
- aspects of twitter
- retweet
- quoted retweet
- view conversation
- live search
- twitter lists
- following and unfollowing
- private messaging
- blocking
- screenshots
