Twitter2irc
(seso) |
m (+ todo list) |
||
| Line 7: | Line 7: | ||
Pro: very well known |
Pro: very well known |
||
Pro: multi-protocol, multi-account |
Pro: multi-protocol, multi-account |
||
| + | Con: relies heavily on a command channel, rather than IRCisms |
||
== tircd == |
== tircd == |
||
Pro: displays users "real names" on @mentions (also a con: increases verbositude) |
Pro: displays users "real names" on @mentions (also a con: increases verbositude) |
||
| + | Pro: 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?) |
+ | Pro: multi protocol. (multiaccount is unknown/assumed?) |
Con: libpurple has heavy dependancies in debian at least (X crap!! :( |
Con: libpurple has heavy dependancies in debian at least (X crap!! :( |
||
| Line 18: | Line 21: | ||
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) |
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) |
||
| + | Con: is not a general IM solution. twitter/identica only |
||
| + | Con: twirssi specific solution only. |
||
Pro: loading full conversations on the fly |
Pro: loading full conversations on the fly |
||
Pro: nice colouring of hashtags and @mention names |
Pro: nice colouring of hashtags and @mention names |
||
| + | |||
| + | = TODO = |
||
| + | * setup configuration |
||
| + | * aspects of twitter |
||
| + | ** retweet |
||
| + | ** quoted retweet |
||
| + | ** view conversation |
||
| + | ** live search |
||
| + | ** twitter lists |
||
| + | ** following and unfollowing |
||
| + | ** private messaging |
||
| + | ** blocking |
||
| + | * screenshots |
||
Revision as of 16:29, 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 Con: relies heavily on a command channel, rather than IRCisms
tircd
Pro: displays users "real names" on @mentions (also a con: increases verbositude) Pro: relies heavily on "natural" IRCisms (invite, kick, /msg, etc) Con: not a general IM solution. twitter/identica only
minbif
Pro: multi protocol. (multiaccount is unknown/assumed?) 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) Con: is not a general IM solution. twitter/identica only Con: twirssi specific solution only. Pro: loading full conversations on the fly Pro: nice colouring of hashtags and @mention names
TODO
- setup configuration
- aspects of twitter
- retweet
- quoted retweet
- view conversation
- live search
- twitter lists
- following and unfollowing
- private messaging
- blocking
- screenshots
