Sort:  

Interesting, never seen that one before. Will consume those lists too.
The contributors seem to be @good-karma, @therealwolf, @rishi556, @holger80, @reazuliqbal, @quochuy.

  • It does not seem to be actively maintained though, those lists haven't been updated in 2.5 years (1.5 ys for bad actors and 2.5 ys for bad domains).

  • Using that library, to get an updated list of known bad actors/domains requires you to pull the updated npm library and do a frontend release. Not as quick as required to counteract phishing waves.

Besides the lists of bad actors/domains in my "database", KD consumes @guiltyparties / @logic lists too:

So ideally Hive frontends should consume from all 3 sources. Or let the user decide which ones to consume from (eg. with checkboxes).

Mine is going to keep being actively maintained as it has for the past 3.5 years.
That's also because I have more development plans for this bot, as the token of my game (crypto shots) will be used to unlock premium features for this and other projects of mine in order to add utility. [spoiler 😉]

By adding list into above hivescript, we could potentially have same API from multiple frontends, pointing to same list. @asgarth what do you think? Is your @keys-defender, db or code opensource which we can use to combine somehow and create multiple endpoint of same list?

Totally agree. A single list (or at least a single API) will be so much easier to handle for multiple frontends.

@good-karma you mean having hivescript dynamically consume data from my "database" and the other APIs maintained by other Hive folks?

Yeh we could fork that repo (not loving the name) and add that code there.

Something like:

import { fetchBadUsers, fetchBadDomain } from '@hiveio/newname/index.js'

For mine it's just a matter of doing this:
https://peakd.com/psa/@keys-defender/re-quochuy-s3wa0h

Repo forked and added this to my backlog but not really sure when I'll have some free time for this.