I recently unsubscribed from the Gemini mailing list because of the amount of noise. Because of that, I missed the kerfuffle around favicons and all, mostly, and only tonight have I caught up on the whole thing. I'm writing this page to prove that it's absolutely ridiculous to even think about "black-holing" an IP requesting /favicon.txt, because /favicon.txt can be a totally regular file, like this one. It does nothing to "bloat" the spec, nor does it even interact with the Gemini spec. /favicon.txt is just a file on a server, and "black-holing" anyone for requesting it is utterly stupid, on the level of "black-holing" a client for not following the /robots.txt conventions because of whatever is thought to be the type of client that's used. What are we going to do next, "black-hole" any IP that requests any file of the glob /*.txt? Just my +/- 2 cents on the matter, I suppose. gemini://gem.acdw.net:1965/raw/favicon.txt/2

-- Leo's gemini proxy

-- Connecting to gem.acdw.net:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/plain; charset=UTF-8

-- Response ended

-- Page fetched on Wed May 15 18:45:35 2024