You are viewing a single comment's thread from:

RE: Phishing on Hive? No more. Solution for all Frontends.

in HiveDevs4 years ago
  1. Yeah, you're right, there should be a default blacklist with an opt-out option though.

  2. If you create a Blacklist / Mutelist like @jarvie mentioned, I can consider using it for D.Buzz

  3. I want there to be a tool where any user can create a list of domains that would be lined out in red, and that their list could be followed by any other user.

#3 would decentralize the service you are offering.

Sort:  

You replied to your own comment instead of on @keys-defender's comment. 🤨 Therefore, they would not receive a notification. 😒 Anyway, this comment is enough for them to get notified of your comment. 🤨🤨

1 - we already have 3 phishing domains blacklists available. When I have time I'll release a new version of this script that uses them all, including the phishing links reported by the community (see my latest post). It will be up to the frontends to offer a way to let the user choose which one to use or to opt-out. My code will make the integration simple.
2 - blacklists and mutelists are to mute users and that's not effective because phishers keep rotating new accounts in their attacks.
3 - that seems like a feature for the core dev team.

@chrisrice is not notified of your comment, since you have neither replied directly to him nor tagged him. 😐

Yeah, I'll pull the phishing api from.your blog and will probably impliment it in April.

  • The work you did there.is good.

I don't disagree with everything you do and say, just the way you communicate with users, which was likely.adopted from HW's culture.

Posted via D.Buzz