in reply to Re^4: Unable to connect
in thread Unable to connect

All of the hits are from Anonymous Monk, and all are submitting queries to Super Search — which, of course, is quite resource intensive.

Maybe there should be a rate limit for Super Search and other expensive functions? Applied only to Anonymous Monk, so that regular monks can use Super Search as usual. A sane limit might perhaps be something like two or three searches per second per IP address, and no more than perhaps 20 per Minute per IP address. That would still allow a few Anonymous Monks behind a masquerading gateway, but would block robots.

Or, a little bit evil: Require a login for using Super Search. Yes, it's at least annoying for people not wanting to create yet another account. On the other hand, a Google search with site:perlmonks.org works quite well, so Anonymous Monks could use that.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Replies are listed 'Best First'.
Re^6: Unable to connect
by jdporter (Paladin) on Mar 24, 2025 at 12:21 UTC

    At about 1210 UTC today (corresponding to 08:10 server time), I modified Super Search to disallow Anonymous Monk usage. This should be considered experimental and temporary, to see if/how it affects site responsiveness.

        Interesting, but I don't see any evidence that google is the origin of the large number of hits.

      Just a few minutes ago, I got "Unable to connect" when trying to refresh the RAT.

      map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]