Timeline for User Experience for Fraud Detection [closed]
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 17, 2022 at 14:54 | history | closed | Doc Brown gnat Jörg W Mittag | Needs details or clarity | |
| Sep 17, 2022 at 11:17 | answer | added | Ewan | timeline score: 2 | |
| Sep 17, 2022 at 7:26 | review | Close votes | |||
| Sep 17, 2022 at 14:55 | |||||
| Sep 17, 2022 at 7:08 | comment | added | Doc Brown | There is no "best convention" for this. This depends a lot on how many users your site has, how much spam you get, what happens to the posts (are they visible immediately all over the world, or are posts moderated?), can everyone post or only registered users, can posts be marked as spam by other users like here in the SE network, and so on. When you ask such a question, please try to give more context. | |
| Sep 17, 2022 at 5:21 | comment | added | Martin Maat | Any response message will likely not be read by anyone since these things are typically automated. Pretending all is well and the message has been posted seems your best approach (if you are sure about the spam). Of course the bot could come back later and look for it's own message to try something slightly different if it's not there. But then you would block the IP address because you know who it is. Anyway, anything but success as a response will give away you spam detection immediately. | |
| Sep 17, 2022 at 4:16 | history | asked | user1767270 | CC BY-SA 4.0 |