201 | | Adding support for sending out/receiving alerts via Twitter & [BluePrintMessagingModule#Micro-Syntax mining] a hashtag for potential value. |
202 | | |
203 | | Status: [http://tropo.com Tropo] has been integrated for a basic Twitter bot support |
204 | | |
| 201 | Adding support for sending out/receiving alerts via Twitter & [BluePrintMessagingModule#Micro-Syntax mining] a hashtag for potential value: |
| 202 | * store tweets from 1 or more hastags e.g. #eqnz #canterburyquake to build up a local repo of all relevant tweets |
| 203 | * be able to reply/retweet to these messages e.g. provide an official response |
| 204 | * provide analytics on things like - who are the most active users and retweeters e.g. which to target for sending out messages and who is most likely to retweet |
| 205 | * if possible try and cluster similar/identical tweets to reduce the amount of noise - making it faster and simpler to monitor what is going on. As well as automatic clustering, it would be nice to provide users the ability to manually drag a tweet to an existing cluster so that it is removed from the master timeline (so as to simplify the timeline viewed by the user) |
| 206 | * be able to link tickets/actions to specific tweet |
| 207 | * it should be possible to automatically load a hashtag that is included in all outgoing messages e.g. we would have setup #eqnz to be included in all outgoing tweets. this may change during the event e.g. the Ministry of Civil Defence Emergency Management started with #CanterburyQuake but this was soon shortened and overtaken by #eqnz as being shorter and more useable. |
| 208 | |
| 209 | ==== Status ==== |
| 210 | * [http://tropo.com Tropo] has been integrated for a basic Twitter bot support. |
| 211 | * OAuth support has been added using [http://github.com/joshthecoder/tweepy Tweepy] |
| 212 | |
| 213 | ==== ToDo ==== |
| 214 | * {{{msg.send_tweet_by_pe_id}}} using tweepy |
| 215 | * Hashtag harvesting |
| 216 | |
| 217 | ==== Links ==== |