Decide and update who gets notified of comments and also possibly review publication policy #78
Labels
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
IndieWeb
Infrastructure
Launch Critical
Marketing
Needs documentation
Post-Launch
status
Abandoned
status
Blocked
status
Deploy
status
Doing
status
Done
status
In Review
status
Needs Clarification
status
Test
status
To Do
type
Bug
type
Task
type
User Story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: geo/geo-coop#78
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@joshua_davis i deleted the three identical spam comments in Russian that were just left on the site despite our spam protections.
I was notified along with quite a few other people as it is currently configured to notify everyone with the role of manager
Comment notifications can be configured to notify people in a role or just specific e-mail addresses, but also possibly not so many people should have the manager role? (Block placement, configuration of stuff like who gets notified about comments, user management, etc.)
Also reminder that the current policy is that everything is published right away, but we can change that so that comments are moderated, and are only published after someone reviews.
Just deleted two more russian spam comments, so I think we'll need to
have me approve them before they get posted.
I cannot change anybody's roles right now. I can only disable their
account all together. This is a high-priority issue, as waaaaay too many
people have the manager role now. Comment notifications should go to
editors@geo..., or just myself, Ajowa, and Jim, if that's how it has to
be configured.
mentioned in issue #81
mentioned in commit
9a0f2e22e6@joshua_davis oh i forgot to mention that you can change user roles now, to make the list of who should be manager (everything you can do), who should be editor (edit or create any content), who should be contributor (can create their own content and edit it), who should be blogger (can only create and edit their own blog posts).
@joshua_davis are you comfortable changing the user roles from manager to a less privileged role, or do you need help understanding the permissions?
I'm comfortable doing it.
closed
marked this issue as related to #82
@joshua_davis @FreeScholar the other matter that came up here (https://gitlab.com/agaric/sites/geo/issues/78#note_225791909), that the Russion spam comments evading the honeypot spam trap on the site fairly regularly, has now been addressed with a change in permissions to allow only authenticated users to bypass commenting. Note that given the decision in #82 no regular visitors will in fact become authenticated users.