💾 Archived View for gem.acdw.net › html › favicon.txt captured on 2024-07-09 at 00:07:59.

View Raw

More Information

⬅️ Previous capture (2021-12-03)

-=-=-=-=-=-=-

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>favicon.txt</title>
<link type="text/css" rel="stylesheet" href="/default.css"/>
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<body>
<h1>favicon.txt</h1>
<p>20 text/plain
<h1>Favicon.txt</h1>
<p>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.
<p>
<p>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.
<p>
<p>What are we going to do next, "black-hole" any IP that requests any file of the glob /*.txt?
<p>
<p>Just my +/- 2 cents on the matter, I suppose.

</body>
</html>