I see you are using regular formatting for code/shell commands on your comments. Not that that's a problem but just a note you can use one of HN's comments formatting tips[0] for this.
Text after a blank line that is indented by two or more spaces is reproduced verbatim. (This is intended for code.)
Re:Curl Wttr.in
by igor_chubin on Friday June 26, 2020 @09:08AM
(#23651543)
Wow! That's cool. Let's try it
curl() { [ -t 1 ] && curl "$@" | sanitize || curl "$@"; }
Re:Curl Wttr.in
by aloknnikhil on Saturday June 27, 2020 @02:43PM
(#23663732)
I actually stick to regular formatting on HN because of how terribly code formatting on HN renders on a phone. It doesn't wrap around when you format it as code and I have to scroll horizontally since the width is fixed. But it's probably OK for something like this code snippet.
Re:Curl Wttr.in
by igor_chubin on Friday June 26, 2020 @09:09AM
(#23651550)
Yes it works!
The difference is minimal though
(it was intentionally a one-liner)
Anyway, one can write a small filter, to cut any suspicious sequences from the output off, and add some wrapper like that to your bashrc:
curl() { [ -t 1 ] && curl "$@" | sanitize || curl "$@"; }