Guest 07:13:23 PM Nothing, or nothing you can see...
This is sort of interesting. I wonder what the bot found.
Have been noticing them for years; can't recall a good explanation. Assuming bots shouldn't be able to access something I can't see. Thinking it was once explained bots can see links I can't see, but this status implies they're also accessing them.
What they're trying to access is not listed, usually. This would be the case for any links that aren't visible, but also for any DB actions that aren't mapped. Look at a URL carefully when searching for something. You'll notice a question mark followed by a string that might be as simple as 'x=y' but sometimes a lot more complex. This is the query part of the URL, where you're trying to pose a question to whatever it is that responds to you on the server.
Those questions are all mapped. If you check someone's profile, for example, there will be a query string to that effect, and the online activity lookup (that is in itself a query) will list any actions taken by the profile (basically an IP and a user ID) registered to any mapped activity, such as checking someone's profile. If the activity isn't listed, a standard response will say something to that effect.
I don't know if *any* random query would trigger that kind of response. Probably not; it would cause all kinds of bad things. It's one of the ways you might construct a DoS attack on a server, so I assume the SMF programmers know better.
But essentially, this is what you see. It's really just a listing of known activities mapped to IPs (of which some are known).
