Filtering: [German] XXLover Scam

[HungryBoy99Years]

Filter Mode

Auto-Smart Mode

Select the Problem

A type of spammer is not detected at all

(Optional) If 'Other', Enter Very Short Description

No response

Spammer Example / Sample

I noticed this type of spam scam message very frequently in German comments

⚡:SPEZIEL FÜR DICH "TO.SV/XXLOVER" ...

Message goes on for a while and is posted by "Sabrina" (UClz1T3CXuk_jOZmlXobssjQ)

Video / Post Link

https://www.youtube.com/watch?v=a9LYmGNvPGY

(Optional) Additional Info / Context

I've noticed that this tool in general also works well in German comment sections. Thank you for your effort!

[ThioJoe]

Looks like they get caught to me, what version are you using?

[HungryBoy99Years]

I used 2.8.0 for this scan. I've noticed, that that's a quite "old" version. Anyway, I don't understand why the program didn't show that a newer version is available even if it checked for updates? - I've downloaded the latest release manually now. Sorry for the confusion. 🙁

[ThioJoe]

No problem, I'm wondering why it hasn't notified you of the update. Perhaps it's being blocked by a antivirus or firewall? Maybe I'll add some sort of check for that.

It can't be that the program is blocked completely or else you wouldn't be able to authenticate with the API. So maybe something is blocking the call to GitHub specifically somehow.

[HungryBoy99Years]

I do have an antivirus (BitDefender), but there aren't threats or issues in the history. I've also changed nothing on the firewall settings. However, I've tried to manually check for updates within the main menu of the program, and it did find the new version and an available beta version. Very strange. Especially that it found nothing with the automatic check. 🤔

[ThioJoe]

Hm well the automatic update that runs at the beginning is made such that it doesn't ever throw any errors if there's a problem, it's only if you manually check. But since it worked when you manually ran it, it doesn't suggest it was an error.

Are you using a config file? Do you have auto check for updates disabled in there? If you do have a config file and updates aren't disabled, maybe try running without the config file and see if it makes a difference.

[HungryBoy99Years]

I'm not using a config file, since the program didn't detect my token when there was a config file. (But I guess that I've configured an error into the file back then...) Now with the 2.13.1 this error doesn't occur anymore.

The 2.8.0 doesn't check for updates when starting atm; neither with nor without the config file. There's not the text "Getting information about the newest version" like the 2.13.1 does. However, it's telling me that there's a new beta version available.

[ThioJoe]

Hm yea idk, well now in the latest beta it will at least say when there was an error checking for updates. So I'll close this

[Firecul]

Looks like they get caught to me, what version are you using?

You should probably add TO.SV to the domains list also @ThioJoe?