The spam is real.

? Offline

They just keep going, very persistent.

The issue with Akismet is when a user posts a link without manually changing its appearance (http://google.com instead of Google) the plugin is likely to "prevent the topic from posting" the user gets an alert, the composer stays active.

In reality, the plugin allows the post.

Very easy to get several duplicate topics like this.

julian

@Ted is this an issue with spam-be-gone's handling of spam topics, then?

a_5mith

@julian I think that's just an issue with akismet as part of the spam-be-gone plugin, enforcing someone to embed a link with Markdown doesn't really constitute spam prevention, just user annoyance.

julian

Login | NodeBB Forum Software

NodeBB Forum Software - A better community platform for the modern web. NodeBB is a next generation forum software that's free and easy to use.

(manage.nodebb.org)

^ Testing a link as-is

Edit: Seems to work

Trev

? Offline

@julian Of course my issue was when the old Markdown library was in use. I can't imagine Akismet would have had an issue with it but not the new library considering both simply render text into links -- unless the old library operated at the time of post and the new one operated at the time of display.

julian

Thanks @Trev

Those must've been around when the daily digest got sent... at least, I hope that's the case!

julian

@Ted the new markdown library functions in the same capacity as the old one, on the server-side. If it does happen again, please let me know!

? Offline

So far we've been without spam - hopefully that didn't jinx us - so I don't see myself incorporating Akismet support in the plugin anytime soon. In the event that it becomes an issue, I'll look into it.

Then once everything's broken, I'll let you know @julian

julian

We also happened to be on an old version of spam-be-gone (.4 instead of something like .24), though @bentael assures me it makes no difference

I'd never enabled Askimet because the free plan is supposed to be for non-commercial use only. This morning I decided that this forum constitutes a non-commercial entity (that being a support forum for an open source project), so that was ok.

bentael

do you require email confirmation before allowing new users to post?

julian

@bentael We do not, no, as this forum was up before that particular option made it into the ACP, and we saw no reason to restrict it.

I could turn it on, though I'd also point out that with some of these "temporary email" services, it's almost trivial to automate the email verification process.

Hell, Mailinator has an API!

(I keep spelling it as Marinator )

bentael

okay.. i dont know.. how are these bots bypassing captcha on registration? Mechanical Turk? OCR ?

julian

The fact that they're getting past spam-be-gone makes me think it's manual. Now that I turned on Askimet, I haven't seen them, but it's been < 24 hours.

Tanner

@julian said:

The fact that they're getting past spam-be-gone makes me think it's manual. Now that I turned on Askimet, I haven't seen them, but it's been < 24 hours.

They're baaaaaaaaaaaaaaaaaack :squirrel:

<baris>

@bentael said:

do you require email confirmation before allowing new users to post?

This is enabled on this forum now.

a_5mith

@bentael, any chance akismet can be trained to look at the topic title as well as the post content. Current spam is only in the title. Whether the title is included in post content or something like that.

xbenjii

@a_5mith said:

@bentael, any chance akismet can be trained to look at the topic title as well as the post content. Current spam is only in the title. Whether the title is included in post content or something like that.

Could it be something as simple as changing

comment_content: data.content,

to:

comment_content: data.title + data.content,

a_5mith

That was my thinking. As akismet doesn't have a specific title field, could be combined with content.

Xiph

@xbenjii said:

@a_5mith said:

@bentael, any chance akismet can be trained to look at the topic title as well as the post content. Current spam is only in the title. Whether the title is included in post content or something like that.

Could it be something as simple as changing
comment_content: data.content,
to:
comment_content: data.title + data.content,

As the title could be considered a top-level header, how about we add a couple newlines?

comment_content: data.title + "\n\n" + data.content,