Strange new users
-
@dylenbrivera said:
I'm getting strange users from time to time on my forum. Any idea what this is about? Spam? These are the usernames. The domains are also strange. Anyone else experience this?
ljzuzfgfks
nipccawhh
owpucgbqr
nfenmdjWhen you have usernames that you can't pronounce, consider them, 99.999% of the time, to be SPAM.
-
@julian it doesn't, reported in this topic.
Spam be gone plugin.
As I didn't see the discussion in the plugins category, I have a question, it's apparent that it works, but looking through the users on nodebb, I'm seeing a...
NodeBB Community (community.nodebb.org)
-
With the forums I've managed, I've found that the best approach is to just ask a simple question at registration. The bots are not programmed to provide the correct text response so they always fail. Humans have no problems. Every site can provide their own question and answer. I went from zillions of spambot accounts created to absolutely zero.
Is there a nodebb plugin that will do this?
-
-
Just published a Q&A plugin for the registration page, in case captcha isn't your thing
So, this needs to be escalated, reviewed, and a solution needs to be resolved as to how to handle this better so that the bots cannot register an account period.
FWIW, @dylenbrivera doesn't have any spam plugins enabled, and I think @Scuzz is running on a version of NodeBB that didnt't have captcha support yet
-
@psychobunny Would be a good selling point if you packaged spam protection as standard.
-
Yeah ideally the plugin should be written by one of us so that we can update it right away if any breaking changes are introduced. Not sure what the other two think but bundled spam protection isn't a bad idea at all
-
@psychobunny Shot in the dark, how about allowing NodeBB onto the plugin project for every "official" plugin, so that if something does go, you don't have to wait, not sure that's possible though. Perhaps any that don't allow access are unofficial and unsupported.
-
Maybe you could denote official plugins as ~official~ in some way, like a little tag in the ACP or something, to indicate this.
Just an idea, not sure if I even like it or not.
-
One thing we could do is transfer over officially supported plugins to our organization
And create an official plugin developers group maybe (similar to the documentation translation group). If the original author doesn't get around to upgrading then one of us could step in.
But this is of course, totally up to the original author of the plugin
-
@psychobunny Cheers buddy, doesn't seem to work for me though. Not sure if I'm using it wrong though.
$(window).on('action:posts.reply', function() { $('.js-lazyYT').lazyYT(); });
Seems to only pull the video details on a refresh at the minute.
-
I think you posted in the wrong thread by accident (I sure hope it's not because of a confusion when I forked the previous thread)
The hooks actually are
action:composer.topics.post, action:composer.posts.reply, action:composer.posts.edit
-
@psychobunny I did.
-
-
@Tanner said:
Maybe you could denote official plugins as ~official~ in some way, like a little tag in the ACP or something, to indicate this.
That would be handy. There should be a way to identify them.
-
@scottalanmiller Are you utilising spam-be-gone now? (Have you been using it all along?)
We unofficially take abandoned plugins under the NodeBB umbrella... but don't want to set a precedent... otherwise that org is going to be a dumping ground for half-finished, broken NodeBB plugins
-
@scottalanmiller I suggest using the question plugin that @psychobunny created. Use that with the spam-be-gone plugin and I have had no bot accounts since.
-
@julian said:
@scottalanmiller Are you utilising spam-be-gone now? (Have you been using it all along?)
We unofficially take abandoned plugins under the NodeBB umbrella... but don't want to set a precedent... otherwise that org is going to be a dumping ground for half-finished, broken NodeBB plugins
Not yet, looking to use it soon but don't want to add more plugins while chat and other features are broken.