- Took updates as frequently as I wanted
- Could handle multiple RSS feeds to multiple Twitter accounts (ie: could be configured)
- Didn't require handing out my Twitter password (not that this is always a bad thing)
- Didn't have a bunch of dependencies (activerecord, mysqlite, etc...)
- Preferably written in ruby
$ twitterss twitterss.ymltwitterss.yml might look something like this:
legalnews: rss: http://www.avvo.com/news.rss login: avvolegalnews password: secret cnn_money_top_stories: rss: http://rss.cnn.com/rss/money_topstories.rss login: money_news password: secret max: 5 cnn_money_markets: rss: http://rss.cnn.com/rss/money_markets.rss login: money_news password: secret max: 3This config would make twitterss pull items from the CNN Money Top Stories and the CNN Money Markets feeds and push them the the money_news Twitter account. It would also pull from the Avvo Legal News feed and push to avvolegalnews. Example result: To make sure it doesn't post the same link twice, it keeps a list of each link it posts for each config entry in a local file (<USER_HOME>/.twitterss_history).