Suggestion: Communication < Notification

GregoryGHarding
Archived posts: 630
Joined: Apr 16, 2017

Suggestion: Communication < Notification

by GregoryGHarding · · Post #18502

the way you currently notify customers of a account change or parameter they have configured is to send emails. but the primary use for emails is for communication not notification, im suggesting you move your notification system to use a notification service, like pushbullet or something similar. it might help by take some spike loads off your email server when sending out mass emails, and also make for an easier and plainer way to receive notifications from prohashing.
CSZiggy avatar
CSZiggy
Archived posts: 627
Joined: Jan 31, 2018

Re: Suggestion: Communication < Notification

by CSZiggy · · Post #18515

OK so not the pool sending out mass Emails on subjects, this is for when people setup their own notifications. Like dropping hashrate below X value, or I or someone changed a wallet or payout was altered Email.

Does the system send out the emails as they are triggered? Or does it wait and send them enmasse once every 6 hours or something that it would cause a slowdown? I get if you had 10K accounts and you need to email them all, but in an hour, how many notifications are being sent out?


Never got any of those, never altered any of my settings/wallets payout infos since after the notifications were put in, I forgot about them even being on there.