Re: OT: rude behaviour (was: Re: Is this list still going?)
here's a much nicer screenshot, without the extra Gophermap cruft - gopher://baud.baby/I/baby.png - that you had to dump a screenshot on your Web space rather than your Gopher space is quite telling though.
as to why: because it's my Gopher hole, not yours. I'm half and half computer nerd and multimedia artist and I like making bright, colorful things. I also like pushing boundaries on mediums, I do a lot of work with holograms to trick the eye and tight halftone patterns to create moire effects, for example, my Gophermap is no exception. I'd make a joke that if they see the escape codes and assume the hole is corrupt/broken, wait until they meet the author, but I'm not here to argue with myself.
I also make sure that once you're past the obnoxious artwork my Gopher space is fairly easy to navigate. I've made it a personal rule that as long as your browser doesn't crash out completely you should be able to close your eyes and just smash return and you'll still end up at my latest phlog post (or failing that a compliant map explaining what is going on), regardless of what your browser is or is not rendering.
while you are correct that the i in Gopher's itemtypes has been displayed by most clients for the past 20 years if you know your history you'll also know it's also not RFC compliant, it was not covered in the original spec and just adopted later unofficially. a fact that gets beaten around my head almost any time I poke it out of my Gopher hole as a way to try and "teach me how to Gopher properly". I'm new to the mailing list, not to Gopher space or the protocol or the ecosystem.
maybe I should have been more succinct in saying most Gopher browsers do render it but don't handle or display it correctly. some ignore the escape and just barf out the garbage after it, some crash completely, some strip the escape ANSI sequence completely and just render text and some display the colors as intended.
regards
█▄▀▄▀ cat K.
█▀▄▀▄ B 4 U D W 3 R K 5 _
▄▄▀▀▀ +1 (929) 601-BAUD
> On 15 Nov 2025, at 1:21 AM, Matt Owen <matt@jaruzel.com> wrote:
>
> It's this:
>
> https://www.jaruzel.com/shared/baud-baby.png
>
> I have to ask why, though. Surely you WANT people to read your gopher hole? Anyone landing on this will see that mass dump of escape codes, and assume the hole is corrupt/broken.
>
> The 'i' type in Gopher has been displayed by most clients for the past 20 years, and there is no hard rule that they shouldn't be shown. To state that 'most Gopher browsers won't render it' is simply untrue.
>
>
> From: cat K. <cat@b4udw3rk5.com>
> Sent: Friday, November 14, 2025 13:53
> To: gopher-project@other.debian.org <gopher-project@other.debian.org>
> Subject: Re: OT: rude behaviour (was: Re: Is this list still going?)
> there's a big unfriendly ANSI payload at the top, most Gopher browsers won't render it because it's not supposed to be there. I'd attach a screenshot but I don't want to get yelled at again.
>
>
> regards
>
> █▄▀▄▀ cat K.
> █▀▄▀▄ B 4 U D W 3 R K 5 _
> ▄▄▀▀▀ +1 (929) 601-BAUD
>
> > On 15 Nov 2025, at 12:17 AM, Peter Garner (iPad) <peter@petergarner.net> wrote:
> >
> > Interesting .. what are all the undisplayable characters?
> > --
> >
Reply to: