What is going with this spam detection here?

mrjj · wrote on 11 Mar 2016, 15:15

yeah its not mega show stopper
but kinda surprising when it happens.

SGaist · 14 Mar 2016, 12:04

Hi,

Do you have small example that reproduces this ?

mrjj · 12 Mar 2016, 09:49

i forgot what it was. Been a while since last time.
@kshegunov help at one point, maybe he can remember
as he found what part of code that triggered the spam checker.
( I asked him on chat)

kshegunov · 3 Dec 2016, 09:51

@mrjj
It was Wieland's code and this triggered the spam filter (editing is not checked, so that's a workaround):

#include <QDebug>
#include <QQuickItem>
#include <QQmlContext>

SGaist · 3 Dec 2016, 21:10

So writing includes ?

#include <QDebug>
#include <QObject>
#include <QWidger>

Makes it trigger ?
[edit: Fixed code after testing SGaist]

SGaist · 13 Mar 2016, 00:49

Ok after a quick test, the includes themselves are innocent. It's the < > signs that triggers the detection. I think they might detected as html tags. A simple fix for that is to tell markdown that you are writing C++. Simply add c++ after the three ` when you write a code block and you're good to go.

kshegunov · S SGaist 12 Mar 2016, 21:15

@SGaist

It's the < > signs that triggers the detection. I think they might detected as html tags.

Not all headers trigger the anti-spam plugin. In my investigation from the 10-15 includes only this block appeared to be troublesome. If I had to guess, the combination of <, > and the words debug or object are the prime culprit.

Kind regards.

Jakob · S SGaist 12 Mar 2016, 21:15

@SGaist Hm, I tried that - didn't help

Jakob · S SGaist 11 Mar 2016, 22:19

@SGaist It is the exact code snippet that is now in the ubuntu paste bin, for which I posted the link.

Jakob · J Jakob 11 Mar 2016, 13:51

I adjusted the title a bit, now that I'm not so frustrated anymore. But in conclusion:

Number 1: I think it is a very good idea to have some protection on a forum like this.

However: introducing such a thing, without letting any user of the forum know, apparently without even some of the moderators(!!!!) knowing exactly about the details, to me, is a very, very bad idea. To the user it feels they are not taken seriously, and the maintainers of the forum just do whatever they like. That is a very, very uncomforting feeling to get from a forum in the 'Qt-world', where usually a high standard of professionalism is the standard.

mrjj · wrote on 14 Mar 2016, 12:25

Hi
well considering I have posted around 2000 posts and been
hit 2 times, its not overly aggressive if u ask me :)

Also its VERY normal not to tell/make public available how to cheat a filter as it
then stops working very fast.

Also, it has been here all along. At least since I started. My first "SPAM" was
like in my first week.

But I agree. I would be nice to know WHY it triggers on pretty normal code.

JKSH · 4 Apr 2016, 06:04

Pinging @tekojo -- the false positives with code snippets are still happening :(

tekojo · J JKSH 4 Apr 2016, 00:24

@JKSH
Hmm, I thought it was fixed.
Should be ok now.

tekojo · wrote on 4 Apr 2016, 06:08

As for why it hits code snippets... I'm not completely sure. My feeling is that it mistakes them for some sort of scripting attack.

To be honest the main type of spam we have had, has mostly been chinese false educational spam and weird korean stuff.

mariakatosvich · 9 Aug 2020, 13:32

I find the rules somewhere, such that I can format the snippet differently?I just have tried myself being told it was spam when trying to post code.
Thanks
My Expertise - setup nfs server Kubernetes

SGaist · wrote on 14 Jun 2016, 20:01

Hi,

I usually append c++ after the opening three back ticks when writing C++ code.