"CVR" == Chuq Von Rospach <chuqui@plaidworks.com> writes:
>> I guess if the default moderation bit is set, then we wouldn't
>> send out the confirmation message, and non-member postings
>> would have to be approved just like they are today.
CVR> I would set things up so that they don't go into the
CVR> moderation queue until they're confirmed, and then moderated
CVR> as normal. The moderator stuff doesn't change, except that
CVR> the moderator doesn't see them until the user confirms
CVR> them. That closes the hole of the moderator having to deal
CVR> with spam to the posting address. So basically, you put TMDA
CVR> in front of the moderator, not replace the moderator in that
CVR> case. The list is still moderated, just whitelisted THEN
CVR> moderated.Ah wait, I see what you're suggesting. A confirmed non-member wouldn't get added to accept_these_nonmembers, but their message would not show up in the admindb until they've confirmed.
The messages would be in a sort of limbo until them, with timeout/auto-discards if they don't confirm after a certain amount of time. Once they've confirmed, we'll do the normal non-member action (although it would make little sense to go through this rigamarole if we're simply discarding or rejecting non-member postings).
Maybe the admindb should have a button that would let them see all held message, including non-confirmed ones? Perhaps that's a YAGNI.
Have I got that right? I'll think on it and try to decide whether it's worth adding to 2.1 or not.
-Barry