💾 Archived View for rawtext.club › ~sloum › geminilist › 002341.gmi captured on 2020-10-31 at 14:29:00. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Solderpunk solderpunk at posteo.net
Sat Jul 25 15:52:48 BST 2020
- - - - - - - - - - - - - - - - - - -
And my axe!
Errm, by which I mean, yes, gemini.circumlunar.space has not been leftout of this and I've seen just over 3,000 requests from that IP.
On Sat Jul 25, 2020 at 11:18 AM CEST, Martin Keegan wrote:
I'd start with hardening Gemini servers ...
Yes, indeed. The spec does have a status code (44) meaning "slow down!"intended to allow machine-readable communication of a rate limitingpolicy to bots. Of course, it can be ignored by malicious bots, but itshould help against well-meaning but incompetent bots. And, if nothingelse, serving up code 44 with no response body over and over againrather than serving up actual resources should spare the server sometraffic, and also might slow down discovery of new URLs to hit by anoveractive crawler.
Anyway, to the best of my knowledge no server actually implements a ratelimiting scheme using this status code, but I suppose the time has come,as it inevitably would. Posts like this one have been common for yearson the gopher mailing list, which is precisely the reason I added such astatus code. Let's see if it helps any...
Cheers,Solderpunk