> How is that obvious spamming? I think there are very Trac-specific conditions that 'could' be detected (I don't know Askimet, I have no idea if it can be configured to detect such conditions)
For example, the same request have been sent with a somewhat regular pace to various tickets (i.e. same POST data, to several URLs) Other example include unusual actions, such as changing the milestone with no other ticket fields. They are very few chances that unauthenticated users (at least on t.e.o.) perform very similar or identical actions in a short timeframe, whatever the remote IP - I mean detecting the client is not required. I don't know how hard it would be to detect such conditions, but I think it would help against massive spamming - until spammers write more sophisticated spam requests. Another "way" would be to teach Askimet whenever the TicketDeletePlugin is used to remove a comment from a ticket. I guess this leads to Noah's idea about integrating the delete feature into Trac core. If Askimet were able to automatically learn from the TicketDeletePlugin actions, it could prevent the server from being spammed with further identical requests. -- Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev -~----------~----~----~----~------~----~------~--~---
