You are viewing a single comment's thread from:

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

in HiveDevs • 4 years ago

This is also what I am in favor of @jarvie . . in fact, we are scheduled to release @blocktrades' Decentralized Blacklists / Mutelists solution on https://d.buzz this Tuesday.

  • Red lining suspected phishing domains is also a decent idea, but it should be opt-in @keys-defender, and there should be more than one list of suspected phishing domains, and it should be handled by more than one person / groups of people.

Opt-in + Multiple Choices, decreases centralization and in the end, censorship.

4 years ago in HiveDevs by
$0.00
    Reply 7
    Sort:  
  • Trending
    • [-]
     4 years ago (edited) 

    Exactly what I stated in my post.

    • I’m not part of the spaminator team and I’ll start offering my own known phishing domains list with some automation in place to allow trusted members of the community to automatically add new domains to the blacklist

    And yes, we agree but it’s up to the frontends to let users choose which blacklist (if any) to use. IMO at least one should be ON by deafault though in order to protect them.

    $0.00
      Reply
      [-]
       4 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.

      $0.00
        Reply
        [-]
         4 years ago  

        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. 🤨🤨

        $0.00
          Reply
          [-]
           4 years ago (edited) 

          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.

          $0.00
            Reply
            [-]
             4 years ago  

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

            $0.00
              Reply
              [-]
               4 years ago  

              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

              $0.00
                Reply
                [-]
                 4 years ago (edited) 

                It looks like @dbuzz can rest from marking posts with phishing links as blatant scam on D.Buzz. 🤔

                $0.00
                  Reply