Dont send emails for status-node updates

[imaginator]

@lloydwatkin publishes what he is listening to his ./status node and this is sending out emails. We should probably only alert for the ./posts node.
EG:
team@buddycloud.com
13:52 (13 minutes ago)
to me
Hello simon@buddycloud.org,
lloyd@buddycloud.org posted on channel lloyd@buddycloud.org:
? Listening to: Keep On Walking - Scouting for Girls (http://goo.gl/bJnJy) ?

[lloydwatkin]

In which case I'll turn this off until fixed
On 15 Jan 2013 13:09, "Reginald dude" notifications@github.com wrote:

@lloydwatkin https://github.com/lloydwatkin publishes what he is
listening to his ./status node and this is sending out emails. We should
probably only alert for the ./posts node.
EG:
team@buddycloud.com
13:52 (13 minutes ago)
to me
Hello simon@buddycloud.org,
lloyd@buddycloud.org posted on channel lloyd@buddycloud.org:
? Listening to: Keep On Walking - Scouting for Girls (http://goo.gl/bJnJy)
?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8.

[imaginator]

• Very odd - I saw a pusher notification for "Pythoning all day" and yet I don't see it appearing here in your channel. Does that mean you stopped pythoning all day and retracted the post?
• 5 minutes Nope. However I did change my status message (/status node), which isn't displayed by the new webclient and may be considered as a post by the pusher :)
• 3 minutes Oh. We should fix that. I happend to be sitting next to a webclient expert and a pusher expert.

[lloydwatkin]

I think this should be set up as a preference rather than an outright ban on /status node. This means that later on if we decide to add /blog node or similar then we can turn that on/off too as required.