It wouldn't surprise me...
@JohnLocke said (forgot which one of the fake accounts) he wanted to move from Switzerland to Romania or Bulgaria... so the username kinda fits
😉
and this
balkansbiz just joined, went on a posting spree and already recommeded the forum to other users:
🤣
(screen from his post):
View attachment 832🤣
and then just in case he bumped the Hamilton bank thread...
🙂 with this:
View attachment 833
and gets likes by
@lory (fake user) and
@JohnLocke puts a like there at 11:08 CEST,
then after a few minutes he logged in as
@bubbledouble (MG lifetime user) and put other likes to his other fake user (
@bountymounty) that said to another (real) user to "upgrade to mentor group gold, it will help you achieve..."
🤣
(time descending, check timestamps):
View attachment 834
let's scroll a few hours later in the latest activity view of OCT to dig when he liked that post:
he was logged in as
@lory at 13:42 CEST when he put the like to
balkansbiz post, then he switched user to balkansbiz to post another message...
(time descending)
View attachment 836
but we could even check a random time in the morning... same thing:
he was logged in as
@koohl at 05:55 CEST, he put a like to
@alley (we know it's him), then logs out,
two minutes later he's back as
@bubbledouble and he put a like to
@EliasIT (yep always him...) and a like to...
balkansbiz 🤣
View attachment 837
these screens are ALL the forum activity, not copy-paste the single users, aka there was no activity in between those lines in the whole forum...
sometimes he goes back and forth with the fake users, sometime he gets notifications from real users and so he comes in with multiple fake users to keep the thread going.
when the thread dies, he uses another fake users to bump it back up... hoping that the real user will get the notification and come back
I hope the whole thing is automated via AI agents but I doubt... I went through months of forum activity and can see it's always the same guy typing, same mistakes, same style
😱
and then when I start to query too much...
View attachment 840
