Hi Caleb,
On Tue, Mar 30, 2010 at 2:12 AM, Caleb James DeLisle <
calebdelisle(a)lavabit.com> wrote:
Guillaume Lerouge wrote:
Hi Caleb,
On Mon, Mar 29, 2010 at 9:16 PM, Caleb James DeLisle <
calebdelisle(a)lavabit.com> wrote:
> Should this be a jira top level project? I don't see what existing
> application it
> would fit in.
>
> Some information about the code's current form:
> It allows users to invite their friends to join a wiki, it has some
strict
> measures too handle
> spam situations, the email message is saved and administrators (people
with
> edit rights on that page)
> can review sent emails. The email has an ID string which is contained in
a
> link sent to the email
> address so that the invitee can report the email as spam (this is a
> function of the template.)
> falsely reporting messages as spam is protected because the ID string is
a
> large random number.
> Users can send to one address and admins can send to as many addresses
as
> they like.
> Email addresses are checked against a regular expression before sending
and
> invalid addresses
> will not be sent to.
> If the sender is a user and can only send to one address then the
address
> is checked against
> LiveValidation as well.
> If a message is reported as spam, then it is flagged on the list and
when
an admin
views the list
they can inspect the message and select a button to indicate that the
situation has been
investigated.
Sounds good. To make sure I get things clear:
- An user can invite another user without necessarily having a prior
admin validation (though admin validation can be forced through
configuration)
Currently all users who have view access to the inviter are
allowed to send
using it.
A user (admin) with edit access to the inviter may send to multiple
addresses at
once.
Ok. Sounds good.
- However invitees can report messages as spam
(what happens then? the
admin get notified that the inviter sent a
spam message and takes
action?
does an inviter whose at least 1 message has
been marked as spam gets
prevented from sending further invitations pending admin clearance?)
What
happens is it is highlighted on the list, there is no notification
process
(I'm not sure how this would be implemented)
Preventing a user from sending further messages after one of their messages
is
flagged as spam was not something I had thought of but it should not be
difficult
to implement.
Maybe the threshold should be a bit higher, 3-5 messages marked as spam and
not only 1?