Title: Actions
<a name="Actions-Filters(tests)"></a>
#### Filters (tests)

<table>
<tr><th> Syntax </th><th> Description </th><th> Example </th><th> Note </th></tr>
<tr><td> @_username_ </td><td> Selects messages sent by a particular user </td><td> @rhirsch </td><td> </td></tr>
<tr><td> any </td><td> Selects all messages regardless of their characteristics </td><td> any </td><td> </td></tr>
<tr><td> /_regex_/ </td><td> Selects messages if body matches a regular expression </td><td>
/exception/ </td><td> </td></tr>
<tr><td> "_string_" </td><td> Selects messages if body contains the case insensitive
string </td><td> "sales order" </td><td> </td></tr>
<tr><td> \#_tag_ </td><td> Selects the messages containing the tag. </td><td> \#project gumbo </td><td>
Note the tag could be in the message as a hash code or created by the user
directly as a tag </td></tr>
<tr><td> to = @_username_ </td><td> Selects the messages that were sent to a particular
user </td><td> to = @rhirsch </td><td> </td></tr>
<tr><td> to = (@_username1_, @_username2_) </td><td> Selects the messages that were sent
to multiple users. </td><td> to = (@rhirsch, @m) </td><td> List should be comma separated </td></tr>
<tr><td> to <> @_username_ </td><td> Selects the messages that were not sent to a
particular user </td><td> to <> @rhirsch </td><td> </td></tr>
<tr><td> not(_exp_) </td><td> Selects the messages in which the expression evaluates to
false </td><td> not("sales order" ) </td><td> </td></tr>
<tr><td> _exp1_ \</td><td> _exp2_ </td><td> Selects the messages in which either expression is
true </td><td> "sales order" \</td><td> "profit" </td><td> </td></tr>
<tr><td> _exp1_ & _exp2_ </td><td> Selects the messages in which both expressions are true
</td><td> "sales order" & "profit" </td><td> </td></tr>
<tr><td> _number_% </td><td> Returns messages based on the percentage. </td><td> 44% </td><td> For
example, the 45% will be true 45% of the time. </td></tr>
</table>

<a name="Actions-Hooks(messagesgeneratedonsystemevents)"></a>
#### Hooks (messages generated on system events)

<table>
<tr><th> Syntax </th><th> Description </th><th> Notes </th></tr>
<tr><td> login </td><td> Selects the messages generated on user login. </td><td> </td></tr>
<tr><td> follow </td><td> Selects the messages generated when a user follows you. </td><td> %f
expands to follower nickname </td></tr>
<tr><td> unfollow </td><td> Selects the messages generated when a user unfollows you. </td><td> %f
expands to ex-follower nickname </td></tr>
<tr><td> profile </td><td> Selects the messages generated when your profile is changed. </td><td>
</td></tr>
<tr><td> every _number_ mins </td><td> Generates messages at regular intervals and selects
them. </td><td> The message is not saved\- too noisy, plus two identical tests
never refer to the same event </td></tr>
</table>

{info:title=User, followers' and public timelines}
Messages generated by events can be used in the actions test expression,
since the event cause is attached to them. Messages generated by events
appear by default in the user's timeline, but not in follower's timeline.
The message can be resent to followers using the existing *resend* action,
or suppressed from user's own timeline by means of the *filter* action. Any
and all saved messages appear in the public timeline (this could be
addressed by these messages being private by default in the future). {info}
\|

<a name="Actions-Actions(performances)"></a>
#### Actions (performances)

<table>
<tr><th> Syntax </th><th> Description </th><th> Example </th><th> Note </th></tr>
<tr><td> filter </td><td> Filter the message out and don't put it in your mailbox </td><td> filter
</td><td> </td></tr>
<tr><td> resend </td><td> Resend the message to all your followers regardless of their
characteristics </td><td> resend </td><td> It will only be put in your followers timeline
if it is not already there. </td></tr>
  
  
status=%s | Enter HTTP POST data on a new line; %s expands to original
message, %u expands to user nickname, %i expands to image URL, %w expands
to user's full (mnemonic: _w_ hole) name (first + last) |
<tr><td> mailto: _email_ </td><td> Send the body of the message to the email recipient </td><td>
{noformat}
</tr>
mailto:wille.coyote@acme.com

    | atom: _url://_ \\
    rss: _url://_ | Posts the new entries from Atom/RSS feed | atom:[http://twitter.com/statuses/user_timeline/esmeproject.atom]
 | Bots can also post to Apache ESME, but polling from Apache ESME is more
secure and robust |
    | scala | Interprets the text of a message as Scala code and returns back
the result | action which interprets the text of a message as Scala \\
    code and returns back the result | Details [here |Scala Action]
 |
    
    h4. Examples for assembling tests and actions
    
    || Test || Action || Description || Similar to ||
    | follow | mailto: _mail_ | Sends mail when followed by any user | Twitter
sends messages on follow |
    | unfollow | mailto: _mail_ | Sends mail when unfollowed by a user |
Qwitter helps track who is unfollowing you |
    | profile | http:// _server_ | Sends HTTP POST when the profile is changed
| @chinposin on Twitter tracks your avatar change to chinposin.com |
    | every 5 mins | rss:[http://blog.esme.us/feed/rss]
 | Updates new posts from the ESME blog | twitterfeed posts your blog
titles to Twitter |
    | login | resend | Notifies your followers when you log in | Yammer
notifies when a user logs in for the first time |
    | \#twitter & @me | [http://user:password@twitter.com/statuses/update.xml]
 \\
    status=%s | Posts all messages tagged _\#twitter_ to Twitter | Identi.ca
integrates with Twitter by reposting messages |
    | \#bot \| @bot | [http://localhost:8080/api/send_msg]
 \\
    token=XXX&message=%u said: %s | Reposts customized message to the same ESME
instance, possibly with a different user's credentials | twitterbots helps
you retweet automatically |
    
    {warning:title=Too permissive action tests}
    Be careful, tests for the actions might apply to more messages than you
think. For example, the tag filter applies not only to your messages, but
also ones from people you're following. In the action above which posts to
Twitter, if you forget to restrict the author, you might flood the twitter
timeline with messages you didn't intend to post. {warning} \|
    
    h4. Additional Links
    
    There are many lists of ad-hoc Twitter third-party tools, some of which
might be assembled in ESME using actions.
    * [http://tweeternet.com/]
    * [http://www.squidoo.com/twitterextensions]