We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Until we can verify that an account is legit, I think they should not be able to trigger external notifications to anyone but themselves.
Even if we catch them quickly, they are typically able to get elgg.org to send emails to users on their behalf.
I could see this being a good default policy for Elgg out of the box, too.
Question is: what is the criteria for determining when the user is trusted for sending notifications?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Until we can verify that an account is legit, I think they should not be able to trigger external notifications to anyone but themselves.
Even if we catch them quickly, they are typically able to get elgg.org to send emails to users on their behalf.
I could see this being a good default policy for Elgg out of the box, too.
Question is: what is the criteria for determining when the user is trusted for sending notifications?
The text was updated successfully, but these errors were encountered: