Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dont send emails for status-node updates #8

Open
imaginator opened this issue Jan 15, 2013 · 3 comments
Open

Dont send emails for status-node updates #8

imaginator opened this issue Jan 15, 2013 · 3 comments
Milestone

Comments

@imaginator
Copy link
Member

@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:
[email protected]
13:52 (13 minutes ago)
to me
Hello [email protected],
[email protected] posted on channel [email protected]:
? Listening to: Keep On Walking - Scouting for Girls (http://goo.gl/bJnJy) ?

@lloydwatkin
Copy link
Member

In which case I'll turn this off until fixed
On 15 Jan 2013 13:09, "Reginald dude" [email protected] 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:
[email protected]
13:52 (13 minutes ago)
to me
Hello [email protected],
[email protected] posted on channel [email protected]:
? 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
Copy link
Member Author

  • 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
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants