INDEX:
Besides the phishing reporting feature ("!phishing" command) that I added to a couple of weeks back, starting from today the community can also report on-chain:
The improvement consist in the fact that instead of only consuming 's or
's list of hacked account,
I can now automatically use, in addition, this community-reported hacked accounts list.
Mm, auto-replies. That's it?
1. The hacked-users ban list will also be used by to implement the solution that some Hive devs suggested and that
explained in detail in his post 👉
As part of the logic that automatically handles adding a hacked account to a banlist, in the near future I will also make it add it to my mute list (or likely to an alt account's). In this way community owners will be able to hide all phishing comments simply following my mute list in the community settings. FYI most-popular communities leaders 👆
2. All these new ban lists will be used by my Universal Script for Hive Frontends.
As requested by (hopefully before the end of this week) I'll submit a Pull Request to the Hive condenser repository. I'll do that as soon as the version 2.0 of my script, improved and adapted among the other things to use my new ban lists, will be ready for release.
HOW do we report unsafe links and users, you ask?
Post a comment anywhere using the format below. You can leave it under your blog, as reply to another user, etc. You can use any Hive Frontend.
" command_to_execute link_or_user"
Example: " !SCAM https://nedspizzaforfree.com"
!INFO -> replies to your comment with the list of all available commands
!PHISHING -> reports phishing links targeting the Hive ecosystem (see here)
!SCAM - adds the target domain to the scam domains list
!UNSAFE - adds the target domain to the list of compromised domains
!HACKED - adds the target user to the list of hacked accounts
What will happen when you post a comment with those commands?
...in about 3 seconds you will get an auto-reply and a ~0.03 upvote.
Use these commands only when you are confident about the issue.
Users that intentionally abuse these commands will get $5 downvotes.
Databae updated:
Auto-reply for the newly reported link:
AUTOREPLY TO SCAM LINK IN MEMO: [supported for all commands]
DB correctly updated:
Auto-reply for the newly reported link:
Database correctly updated:
eg. for the phishing command...
DB correctly updated:
Hacked user notification:
Scam link notification:
Compromised domain notification:
In order to reduce abuse, a domain whitelist is in use. Meaning that for example a newly created user cannot add hive.blog to the scam websites banlist =]
All top40 witnesses and a list of whitelisted users can send just a single report to add entries to the ban list.
That's not the case for regular users:
Minimum reputation for the reports to be processed: 50
Amount of reports required for regular users for each type of report:
-- Phishing domains: 3
-- Scam domains: 10
-- Compromised domains: 0 (only whitelisted users and top40 witnesses can)
-- Hacked accounts: 5 (will increase if abused - keep in mind the $5 downvotes..)
For 24 hours please feel free to test these commands using as targets non-existing domains and non-existing users.
Add the word "test" to your comment/report so that it will be easier for me to clean up the DB afterwards.
These scenarios should be covered too:
- Phishing/scam/unsafe links hiding
in shortened links;
- Unsafe links added to a comment
afterwards as edits.
Unfortunately your tests wont get reward$ because at the moment the voting power of my accounts is drained to fight against a comment farming campaign. See my latest post on if you are willing to help, anyone can help using that 10 line script easily executable in your browser.
PS - UPDATE: rewards doubled thanks to new delegations!!
Example of JS/NodeJs code to use in your project:
const HIVE_API = 'https://api.hive.blog';
const TARGET_BANLIST = 'phishing-db'; // <<<< BANLIST PERMLINK HERE
const fetch = require(node-fetch); // <- for nodejs only, not needed in websites
fetch(
HIVE_API,
{
body: JSON.stringify({
jsonrpc: '2.0',
method: 'condenser_api.get_content',
params: ['keys-defender', TARGET_BANLIST],
id: 1,
}),
headers: {
'Content-Type': 'application/x-www-form-urlencoded'
},
method: 'POST'
},
)
.then(res => res.json())
.then(({ result } = {}) => console.log('Banlist:', result.body));
Again, if you are a maintainer of one of the Hive frontends you won't need to integrate my ban lists yourself if you use my Universal Script for Hive forntends.
FYI Hive Frontends maintainers:
PERMLINKS of the ban lists:
DB PERMLINK: 'zy71ydsnp4o1ufhs6j7ksz' - parent post containing all the banlists
To track changes to the ban lists over time you can use:
https://scribe.hivekings.com/?url=https://hive.blog/@keys-defender/PERMLINK_HERE
Keys-Defender features: