github
Advanced Search
  • Home
  • Pricing and Signup
  • Explore GitHub
  • Blog
  • Login

nelhage / barnowl-twitter

  • Admin
  • Watch Unwatch
  • Fork
  • Your Fork
  • Pull Request
  • Download Source
    • 3
    • 2
  • Source
  • Commits
  • Network (2)
  • Issues (0)
  • Downloads (0)
  • Wiki (1)
  • Graphs
  • Branch: master

click here to add a description

click here to add a homepage

  • Branches (1)
    • master ✓
  • Tags (0)
Sending Request…
Enable Donations

Pledgie Donations

Once activated, we'll place the following badge in your repository's detail box:
Pledgie_example
This service is courtesy of Pledgie.

Twitter Support for BarnOwl — Read more

  cancel

  cancel
  • Private
  • Read-Only
  • HTTP Read-Only

This URL has Read+Write access

Restore lost handle_message hook. 
Brian Sniffen (author)
Sun Jan 31 14:49:51 -0800 2010
nelhage (committer)
Mon Feb 01 11:20:18 -0800 2010
commit  6249a76da85cd85f5b75675e1eae1ac3623c1bae
tree    60d3da1a8377f698164ad15256209c232b36ad78
parent  bdb7c26d64ccd06dfcef4095251035ec3dd823e4
barnowl-twitter /
name age
history
message
file .gitignore Mon Sep 14 19:39:28 -0700 2009 .gitignore: Add perl build products. [nelhage]
file .hgignore Fri Jan 11 10:16:18 -0800 2008 initial import [nelhage]
file Makefile.PL Fri Jan 11 10:17:01 -0800 2008 deps [nelhage]
file README Sat Oct 10 15:43:05 -0700 2009 Typo in README [nelhage]
directory lib/ Mon Feb 01 11:20:18 -0800 2010 Restore lost handle_message hook. This was acc... [Brian Sniffen]
file twitter.example Fri Jul 04 11:06:07 -0700 2008 twitter.example: Trailing commas are not valid ... [nelhage]
README
NAME
  Twitter.par - Twitter support for BarnOwl

DESCRIPTION
  The Twitter module implements Twitter support for BarnOwl. It also
  supports automatic mirroring of some subset of Zephyrs you send to
  Twitter.

SYNOPSIS
  (1) Configure your Twitter credentials in ~/.owl/twitter in the
  following format:
----------8<----------cut here----------8<----------
{
 "user":"nelhage",
 "password":"sekrit"
}
----------8<----------end cut ----------8<----------
  (2) Copy Twitter.par into ~/.owl/modules/
  (3) Run ":reload-module Twitter" inside BarnOwl
  (4) Start receiving tweets in BarnOwl!
      You can send tweets with the ":twitter" command.

MIRRORING ZEPHYRS TO TWITTER
  If you set the twitter:class, twitter:instance, and twitter:opcode
  BarnOwl variables, BarnOwl will resend zephyrs matching those fields
  as tweets coming from you.

  By default, these default to -c $YOUR_USERNAME -i status -O twitter.
  Setting twitter:opcode to "" will cause "normal" (i.e. no opcode)
  messages to that class/instance to be mirrored. A value of '*' works
  as a "match-anything" wildcard for any of the fields.

POLLING
  Twitter.par polls for normal messages once a minute, and direct
  messages every other minute. To disable polling, you can unset the
  'twitter:poll' variable in BarnOwl.

IDENTI.CA SUPPORT
  Twitter.par supports other Twitter-compatible microblogging services,
  like identi.ca. To enable this, set the 'service' parameter in your
  config hash to the API URL of your service. You may also need to set
  'apihost' and 'apirealm'. See Net::Twitter or your blogging service's
  documentation for more information.

MULTIPLE ACCOUNTS

  Twitter.par also supports using multiple Twitter and
  Twitter-compatible microblogging accounts from the same instance.
  To enable this, add additional hashes to your ~/.owl/twitter file as
  a JSON list, e.g.
----------8<----------cut here----------8<----------
[
  {
   "account_nickname": "twitter",
   "user": "nelhage",
   "password": "sekrit",
   "default": true,
   "publish_tweets": true
  },
  {
   "account_nickname": "identica",
   "service": "http://identi.ca/api",
   "user": "nelhage",
   "password": "sekriter",
   "publish_tweets": true
  }
  {
   "account_nickname": "sipb",
   "user": "sipb",
   "password":"m0ars3krit",
   "poll_for_tweets": false,
   "poll_for_dms": false,
  }
]
----------8<----------end cut ----------8<----------

Outgoing tweets sent via ":twitter" without an explicit sender, or
mirrored from zephyr, go to every account with "publish_tweets" set.

Outgoing direct messages and @-replies without an explicit sender come
from whichever account has "default" set. If no account has "default",
the first account is assumed to have "default" set. It is an error to
have more than one account with "default" set to true.

There are several account-specific parameters that control the
behavior of Twitter.par when using multiple accounts:

* account_nickname (string, required if multiple accounts are in use)
    Specify a short name by which you can refer to the account, eg.
    "identica" (eg. :twitter-direct nelhage identica would send a
    direct message to @nelhage on identi.ca from your account
    nicknamed "identica").

* default (boolean, default false)
    If true, @-replies or direct messages you send without specifying
    an account will be sent using this account.  If no account has
    this parameter, such messages will be sent using the first account
    listed.

* poll_for_tweets (boolean, default true)
    If true, tweets sent by users this account follows will be
    displayed in your BarnOwl message list.

* poll_for_dms (boolean, default true)
    If true, direct messages sent to this account will be displayed in
    your BarnOwl message list.

* publish_tweets (boolean, default false)
    If true, tweets you send without specifying an account (either
    with the :twitter command or mirrored from a zephyr class) will be
    published to this account.

    If only one account is specified, it defaults to publish_tweets =
    true.

* show_mentions (boolean, default true)
    If true, BarnOwl will show all tweets that mention this account's
    username, regardless of whether or not this account is following
    the sender. Has no effect if poll_for_tweets is false.
Blog | Support | Training | Contact | API | Status | Twitter | Help | Security
© 2010 GitHub Inc. All rights reserved. | Terms of Service | Privacy Policy
Powered by the Dedicated Servers and
Cloud Computing of Rackspace Hosting®
Dedicated Server