#1145: Provide link spam prevention
-----------------------------------------------+----------------------------
 Reporter:  Matthew Good <[EMAIL PROTECTED]>  |        Owner:  jonas   
     Type:  enhancement                        |       Status:  reopened
 Priority:  high                               |    Milestone:  1.0     
Component:  general                            |      Version:  0.8     
 Severity:  normal                             |   Resolution:          
 Keywords:  link spam                          |  
-----------------------------------------------+----------------------------
Comment (by [EMAIL PROTECTED]):

 So here is a summary of what has been suggested. If I miss something,
 someone please add:

  * Create a blacklisting solution for URLs being posted.
  * Delete comments
  * The google no follow thing
  * Deleting spam

 So here is what I propose. It should resolve #454 and this ticket as well,
 along with making this a nice solution for public facing and private
 projects.

 The main issue is a division in the user base, really. If everyone using
 trac was using it in a public facing situation, where they are vulnerable
 to spam in tickets/wiki/the whole nine yards, the argument to never allow
 deletion of comments in #454 would have never come up. The opposite would
 be true if only internal projects were to be using Trac.

 So here goes, this is what I think will work:

 1) Create a way for folks with TICKET_ADMIN (and higher) access to delete
 comments. If you gave these people TICKET_ADMIN rights, you should trust
 them enough to delete comments without questioning what they are doing.

 2) When deleting comments, give the option to blacklist the URLs and the
 commenter as well.

 3) Offer the option to keep a record of this deletion in the ticket.

 4) Make this optional. Something like trac-admin trac-env spamguard enable
 or trac-admin trac-env permission add group SPAM_ADMIN or something. This
 way if the project just doesn't need spam prevention, they don't have it
 and everything works as it does now.


 This may be a way to satisfy everyone, and both tickets. There may be ways
 to improve this as well, but as I see it, this might be a really good way
 to do it.


 At least I hope so :P

-- 
Ticket URL: <http://projects.edgewall.com/trac/ticket/1145>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets

Reply via email to