To simplify adding users to StopForumSpam, since currently it involves copy/pasting three times between at least 2 (3 if the user is already registered) web pages...
https://www.stopforumspam.com/usage > Adding to the Database for details of SFS's API.
Admin/Moderator profiles would require an extra field into which the API Key (generated at https://www.stopforumspam.com/keys) would need to be stored. If this field is empty they attempted usage of the reporting buttons/functions below would generate an error indicating it needs to be filled out.
Anyone without privileges to view another user's IP address and email would not have this entry visible, nor would the reporting features be visible.

A report button would, at a minimum I suggest, be required on
Registration Queue (/admin/manage/registration)

User page (/user/$USERNAME)

Clicking those would take user to a new page listing the three known items about the user that will be reported (username, email, IP address) and would have an extra field for any evidence, and that page would submit to SFS.
Perhaps this is better handled by the spambegone plugin? It deserves some pretty significantly improvements, at the moment SFS isn't even used by it I think.
I thought the underlying data retrieved from SFS for the registration queue was in core?
@barisusakli - thoughts? :)
stopforumspam is definitely used when displaying users in the registration queue.
I meant, would that be a better place for this request? :D
Edit: probably yes, if that's what's providing data into the reg. queue...
The stomforumspam code is in core actually https://github.com/NodeBB/NodeBB/blob/master/src/user/approval.js#L238
We've reached out to @akhoury directly to discuss moving all this into spam-be-gone :smile:
So i started working on this but i could use a little bit of guidance @julianlam
Since stopforumspam was being used by nodebb core by default, I think it should be enabled by default in spam-be-gone, but
spamData and ipMatch in the template
I have no idea how to, __from the spam-be-gone plugin load callback__, add the "Report to StopForumSpam" buttons, one in the Registration Queue, and the other on the user's profile, just like the last 2 screenshots that @pauljherring shared


if that's in fact what we want to do, I really shouldn't be updating the core templates for this, no?
if that's in fact what we want to do
Those were only suggestions as to how I'd think it could work from an end-user point of view - they're not set in stone :)
What happens when someone hasn't installed spam-be-gone? how should the Registration Queue page handle this?
I'd go with don't show anything (extra) - same as if:
Anyone without privileges to view another user's IP address and email would not have this entry visible, nor would the reporting features be visible.
Ok, so this is 99% ready, I just have to actually test the final request "reporting a spam to stopforumspam", i tried to register so i can get an API key, but they didn't send me the initial email, i just contacted their administrator.
As of now, ONLY administrators and Global Moderators can actually report someone as spam.


The error in red is because i used a fake key


Most helpful comment
We've reached out to @akhoury directly to discuss moving all this into spam-be-gone :smile: