Following up the reports possibly with a chatbot

[sekisanchi]

Roughly more than half reports can't be identified with current UI, and those are left intact, I guess. Having some sponsored bounty program for the chatbot would be easiest and quickest improvements on it. Inspired with this blog post - https://hackernoon.com/bots-are-here-to-stay-here-are-4-reasons-why-caaec6bf5be3

[409H]

Hi Seki,

Which reports are you talking about?

[sekisanchi]

I did not aware of exact user scenario cases last time. There are two entry panels you have now,

1. EAL Chrome extention "Report a domain" button to https://etherscamdb.info/report/domain/
2. EAL Site "Report" button to https://etherscamdb.info/report

Let me try sorting out the UX

First, two perspectives - a) Users want to report "incidents" with some hope to recover b) Backoffice to find out malicious domain/hash from the incident, and return guidance

I looked around the panels, and here's some quick recommendations prior to considering the bot.

1. Having a common entry and a common scenario for reporting incidents or findings, by changing "Report a domain" into just "Report " at chrome extension button, connected with common entry
   https://etherscamdb.info/report

2. below as one of UX improvement to capture the incident detail.

The chat bot will perform similar incident report hearing scenario aside current input forms maybe.

The malicious url/address dup check can be done by the chat bot also.

[409H]

Ahh, I understand. Thanks for the mockups and explanation.

I'll pass it over to https://github.com/MrLuit/EtherScamDB and we can plan the desired UX changes.

[sekisanchi]

Thanks. That's the smallest piece, and I'll put separate issues or PRs. for other actionable changes in the large loop of reporting.