Conversation

even iocaine’s strongest config known to me – that which the author uses – is bypassed by grok

terrible

2
0
0

to be fair, I run Iocaine 2.5.0 stable whereas the latest version of that config is for an in-dev branch

0
0
0

@shroomie can you be any more specific /lh

1
0
1
@alexia is iocaine bypassed by grok? is grok iocaine-proof?
2
0
0

@shroomie As of right now, with the 2.5.0 release of iocaine and the config, yes.

Grok actively hides itself. It does not use a recognizable useragent, it uses a real browser, it makes requests reminiscent of what Safari on an iPhone would do.

Point is, it actively hides itself and as such bypasses a lot of iocaine’s measures. It also caches so even if you set up iocaine afterwards and Grok is catched, it will just use an old cached copy.

The measures that the Nam-Shub of Enki config used by the author currently implements might not be enough to deter grok, is what I’m saying.

2
0
1