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

A way to notify crunchers of polls and updates (an opt-in email notification). #255

Open
Weber462 opened this issue Dec 28, 2022 · 10 comments

Comments

@Weber462
Copy link

Weber462 commented Dec 28, 2022

Is there an easy way to implement some sort of opt-in notification of polls/updates etc. I feel a lot of crunchers might be running headless servers. I believe this will increase polling participation and help with wallet updates

@Weber462
Copy link
Author

Weber462 commented Jan 6, 2023

“The right way to handle it would be a core config file entry such as enablepollemailnotification=1 that would default to 0 (false). This entry could also be changed via the GUI just like the staking checkbox, etc.”
“The question is the best way to actually implement the notification. Needs to be an operating system level mailto:...”

@Weber462
Copy link
Author

Weber462 commented Jan 6, 2023

“The beacon structures on the blockchain and the BOINC statistics handled by the scrapers do NOT contain the email or any other PII associated with the CPID. However, the wallet node that is linked to the CPID does possess a valid email, as this must be provided for the wallet to validate the CPID and go into researcher (cruncher) mode. We could use this email to have the local wallet node send an email notification on receipt of a valid new poll contract. This would at least notify crunchers.“

@div72
Copy link
Member

div72 commented Jan 6, 2023

Having a config key to send e-mail is out of scope for the wallet in my opinion. All important discussions are made in this repo beforehand, so why not use this repo instead?

@barton2526
Copy link
Member

This just seems like feature bloat. Why can't a third party offer this service?

@Weber462
Copy link
Author

Weber462 commented Jan 6, 2023

Is there one? I tried to look but couldn't find any. It would be nice if wallet could somehow send email/notification. I would think it would be most reliable/accurate. As long as it doesn't affect wallet negatively and you need to opt in, I don't think it would be too bloaty. I just know it would be a feature that I would find extremely useful. More importantly, could help with community involvement.

@jamescowens
Copy link
Member

Most (99.9%+) people running headless are running Linux. Linux has sendmail functionality. Unfortunately, most people don't even bother to configure it for even the most basic forwarding/sending.

@iFoggz
Copy link
Member

iFoggz commented Jan 6, 2023

No reason the wallet can't curl the gridcoin website mail server with the email address if new poll detected or poll about to expire and they haven't voted. The mail server could then locally send via a noreply to the said email address of cpid or custom notification email address. This would also pass spam related detections as well.

@jamescowens
Copy link
Member

I like that idea. You want to give coding that a shot? I still think the curl send itself should be controlled by a config entry and also have a GUI tickbox.

@jamescowens
Copy link
Member

By the way, @iFoggz, since the email would be sent to a centralized Gridcoin service (the Gridcoin website mail server), and even though it would be encrypted, this represents someone sending potential confidential information (their email). I think this means that if we implement this functionality, clicking the checkbox should present a warning that their email will be sent to the Gridcoin web server email service for notification. The email will not be retained.

@Weber462
Copy link
Author

Were there any updates on this function?

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

5 participants