Friday, 9. January 2009
The main problem with using twitterfeed is that you have to trust it with your twitter credentials. I didn't see any reason not to trust it but given the recent spate of twitter hacking many people will be understandably reluctant. One option would be to set up a separate twitter account just for twitterfeed and let that account do the publishing. The drawback to that is that you would need to get your followers to follow that new account too. Hopefully twitterfeed will adopt something like OAuth in the near future so they don't need your credentials. Ideally twitter will someday introduce a third party application approval mechanism similar to the one Flickr provides.
Once you've decided how to handle the twitter credentials, enter the URL for any RSS or Atom feed –
http://www.splatdot.com/rss.xml for example – and then you can control to some extent what, when and how get published from the feed.
- Update frequency Tells twitterfeed how often to poll the RSS feed for updates – from every 30 minutes to once every 24 hours.
- Post up to: The number of new entries from the RSS feed to post. This can be set from 1 to 5. If there are more new items than that in the feed they will not be posted to twitter. Ever.
- Include…: Specify whether to include the title, the description or both.
- Include item link: Include a link to the item along with the text. I can't really think of a situation where you would not want to send the link but somebody must have or this wouldn't be an option.
- Post new items based on: Publication date or GUID.
- Prefix each tweet with: This option lets you add some static text to the beginning of each tweet. I haven't tried it but you should also be able to use this to either send the tweet with “@user” or “d user”. If you set up a second account you could have it direct tweet your main accoount with a feed you don't want your followers to see.
- Filter by keywords: If you set up filter keywords only items from the feed that match one of the keywords will be posted.