Supreme @lguesslmlose

[2.646]

Staff is sleeping

Beware of scammers who impersonate me!
Note: Messages such as "Hello, Hi" will not be considered.
______________________________________________________________
THIS SPOT AVAILABLE
______________________________________________________________

[38]

@Alex Hi, could you please review this case?

[38]

[font][font]@Alex
@Ping
@Liars
@Eminem

Hello, please review this case. It's been open for two weeks and no one from the administration has responded.[/font][/font]

[3.276]

I was requested to perform a functionality test on this configuration and to provide a statement regarding whether or not it was operational.
For testing purposes, I requested a list of sample data containing confirmed hits to properly evaluate its detection capabilities. During the test, the configuration successfully identified hits and the corresponding keywords listed within the text file for inboxes containing messages that matched those keywords.

That said, I did not conduct an extensive or in-depth review of the configuration’s internal logic. If I were to hypothesize, the primary bottleneck likely resides in the routine responsible for parsing through inbox contents of each account in search of the keywords contained within the keyword file. I recall encountering a similar performance issue when I personally ran it, albeit not to the same degree as what is being reported here.

I had even commented at the time that it would be beneficial for such a checker to include an optional preliminary phase — one that first validates login credentials before proceeding to execute the inbox-parsing module. I briefly began conceptualizing a separate tool written in Rust to handle rapid login validation, with the intention of later integrating inbox parsing as a secondary module. However, that project was never fully realized.

Given my prior involvement in this matter, I believe it would be improper for me to preside over or contribute further to the resolution of this dispute. Therefore, I will be transferring full custodianship of this case and its resolution to @Alex.

 

 paid ad - 05/15/2026

   [Selling Signature Ad Space - DM Me]

 

[Ping's PGP Key]

Before conducting any form of business confirm my identity through onsite PM.

[4.225]

@lguesslmlose have you tried helping the user with his issue? At least trying to understand what could possibly be the problem with the user setup.

@Beatifulmo Does this happen with a different config? Or just this one?

Top Ad by @SonicRefs | Ends in 30/05


Bottom ad by @Refunding | Ends in 15/06

[2.646]

@lguesslmlose have you tried helping the user with his issue? At least trying to understand what could possibly be the problem with the user setup.

@Beatifulmo Does this happen with a different config? Or just this one?

Yes, I helped, even though the config was working, he said that the CPM was fixed. We tried it with "PING" and even he said it was working, you can ask him.

Beware of scammers who impersonate me!
Note: Messages such as "Hello, Hi" will not be considered.
______________________________________________________________
THIS SPOT AVAILABLE
______________________________________________________________

[38]

@lguesslmlose have you tried helping the user with his issue? At least trying to understand what could possibly be the problem with the user setup.

@Beatifulmo Does this happen with a different config? Or just this one?

With this one, I ended up buying another inbox search tool and it works well (it's not a Silverbullet config but a separate program) and it works fine.

He only mentioned general problems, which I also tried, as I mentioned, one of them was the VPS, which I followed his advice about and bought a VPS out of my own pocket, and even then the problem persisted.

And it's worth clarifying that in addition to the tool I bought, I also use Silverbullet with different configurations, and it works fine.

[38]

Furthermore, there's also a specific use case for his config, and he should have warned me before I bought it, for example, that it "only worked" with combos of +500k or something like that, or that it "only worked" in RDP. When you buy a config, it's supposed to work like a standard, like any other config, but I've had to guess as I tested it because he never explained anything to me specifically. The same goes for the keywords; if you look at the chat screenshots, I had to ask him before he told me how it worked.

But anyway, it still doesn't work with RDP or large combo boxes. I've already run the respective tests, and he says he tested Ping and it works, but only the logic works, which is fine for me too. I didn't say it didn't recognize the keywords or the inbox search bar, but the problem is that it doesn't analyze the entire combo box, as I already showed in the screenshots, and I'm 100% sure it's a configuration problem.