-
Notifications
You must be signed in to change notification settings - Fork 0
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
Need a notification system for notable events #93
Comments
I propose we take inspiration from Phil Windley's blog post on Notifications. |
With this commit and the few preceding it, we received a couple of email notifications of notable events. Still needs some finessing, but it basically works now. |
These are the steps that a participant must follow to receive notifications of relationship events:
*the format to save them in is as follows:
where |
Notice that I am working very hard here to not become yet another administrative system. It would be easy, and easier for the user, if we just signed up for a paid plan with mailjet and had the byname system send the email messages. But the principle is that we are providing a hosting service for picos which are owned by participants. Furthermore, all byname does is raise |
Initial plan is to have a way to send an email notification that something interesting has happened wrt a participant's pico.
Strategy is to have each byname app identify such events and raise a
byname_notification:status
event on the pico's event bus.If the participant has installed an app that reacts to that event, it could then send an email message, or take some other action, under the participant's control.
There is a module,
com.mailjet.sdk
that can be installed/configured to actually send an email message, using an account established by the participant.The text was updated successfully, but these errors were encountered: