Message Processing
From:
Michael JasonSmith
Date:
Jul 17 02:44 UTC
Short link
I am currently working on rewriting the code that determines if a person can
post to a group or not, and it turns out that my estimates of how many checks
are required were a little shy of the mark: there are eight checks, excluding
moderation, not six. The current list is as follows.
1. The first check is to see if the group restricts who can post. Support
groups, for example, allow anyone to post.
2. If there are restrictions, check if the user is a member of the system. This
requires people who post using the Web interface to log in first.
3. Check if the user is a member of the group.
4. Check if the user has valid email addresses (we do not want people without
verified email addresses to post).
5. Check if the user is a posting member. Not all members of a group can post:
announcement groups often restrict who can post.
6. Check if the posting limits been hit. This restricts "me too" posts
clogging up the system. Participation coaches and (in the new code)
administrators are not subject to this restriction.
7. Check if the user been specifically blocked from posting. There is no user
interface for this, as moderation takes care of most of the use case for
this feature.
8. Check if all the required user-properties for the site and the group have
been set. The required properties for a site are set at a global level,
while individual groups can require particular user-properties to be set.