Twitter2irc

From ThorxWiki
(Difference between revisions)
Jump to: navigation, search
(seso)
m (improve lists)
 
(One intermediate revision by one user not shown)
Line 5: Line 5:
   
 
== bitlbee ==
 
== bitlbee ==
Pro: very well known
+
* Pro
Pro: multi-protocol, multi-account
+
** very well known
  +
** 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
  +
** 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
   
 
== minbif ==
 
== minbif ==
Pro: multi protocol. (multiaccount is unknown?)
+
* 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
Pro: loading full conversations on the fly
+
** 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: nice colouring of hashtags and @mention names
+
** 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
  +
  +
= TODO =
  +
* setup configuration
  +
* aspects of twitter
  +
** retweet
  +
** quoted retweet
  +
** view conversation
  +
** live search
  +
** twitter lists
  +
** following and unfollowing
  +
** private messaging
  +
** blocking
  +
* screenshots

Latest revision as of 17:25, 5 September 2012

Contents

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
Personal tools
Namespaces

Variants
Actions
Navigation
meta navigation
More thorx
Tools