You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are about to start using a second list of suspicious sites, maintained by Phishfort. We should ensure we are not directing users to eth-phishing-detect to dispute sites blocked by Phishfort.
Currently this warning page directs users to eth-phishing-detect to dispute blocked sites, with the "please file an issue" link.
We could ask Phishfort for a new dispute URL to use for their list, or a set of instructions on how users can dispute blocks. Or we could hide all instructions on disputing a block when a site is blocked by Phishfort. Either way, that section will need to be conditionally rendered, and we'll need a new query string parameter to communicate which config the block is coming from or how to handle disputes.
The text was updated successfully, but these errors were encountered:
We are about to start using a second list of suspicious sites, maintained by Phishfort. We should ensure we are not directing users to
eth-phishing-detect
to dispute sites blocked by Phishfort.Currently this warning page directs users to
eth-phishing-detect
to dispute blocked sites, with the "please file an issue" link.We could ask Phishfort for a new dispute URL to use for their list, or a set of instructions on how users can dispute blocks. Or we could hide all instructions on disputing a block when a site is blocked by Phishfort. Either way, that section will need to be conditionally rendered, and we'll need a new query string parameter to communicate which config the block is coming from or how to handle disputes.
The text was updated successfully, but these errors were encountered: