I ran into this question:
And while I thought it a very interesting question, I questioned whether or not it belonged under "Unix & Linux", and even gave feed back about how displaying random characters around real information can make things hard or near impossible to read and wondered what they were trying to accomplish,
But the question goes into using bash to generate and/or maintain a background of an unrelated image and interspersing it around content text.
Then they go into using bash's prompt vars to aid in generating this, as well as asking about how this output is generated or comes from a "VT subsystem" (a primitive vt102 emulator that runs on the console for purposes of using the console with curses-type programs when one would like more than a simple line-oriented interface during system repair).
Then there is talk about how bash makes use of the terminfo database capabilities by including them in the prompt vars (PS1, et al), which is a misleading statement/point of view, as bash doesn't make use of that database and shouldn't -- though a user might they might do better to store output of 'tput' for various actions rather than hardcoding some terminal specific terminal codes -- though they do use tput later.
I keep wondering what the question was -- where would this be used, but it seems clear it has little to do with bash, more than other posix compatible shells.
If I knew what the question was, I might think it better on a computer-art forum or something else, but it's hard to see how this is a unix/linux question as I tried to answer how it's not the best way to communicate information as dynamically generated background around content, but somehow that got translated by him into my thinking it doesn't belong on any SE sites, which I wasn't saying though in thinking about it, it doesn't really seem to fit the Q/A format and might better belong on some QA's wiki, but not having much experience w/that, I can't say. Anyway, he was then justifying how the Q getting 22 points justified its inclusion on the unix.sa site, and saying if it wasn't allowed, he wouldn't have done 116 other contributions "which stands well above ̶y̶o̶u̶r̶s [your contribution count] at this point in time" .
At this point, I don't know what to do if anything, but hoped to bring it to the attention of those with more experience who might be able to do the right thing (if doing anything at all).
Responding to a comment by @sim, You said it belongs here. Do you mean here in meta? Or that it is a question about Unix or Linux and belongs in the original forum.
To clarify why I had a question about its current location being appropriate:
Looking at what the forum is about (from https://unix.stackexchange.com/tour):
1) Ask questions, get answers, no distractions This site is all about getting answers. It's not a discussion forum. There's no chit-chat.
2) Get answers to practical, detailed questions Focus on questions about an actual problem you have faced. Include details about what you have tried and exactly what you are trying to do. Topics to ask about:
- Using or administering a *nix desktop or server
- The Unix foundation underlying MacOS (but generally not frontend application questions)
- The underlying *nix OS on an embedded system or handheld device (e.g. an Android phone)
- Shell scripting
- Applications packaged in *nix distributions (note: being cross-platform does not disqualify)
- UNIX C API and System Interfaces ( within reason )
---- I'm not sure ascii art in the background of normal foreground TTY traffic really fits...
Questions that don't work:
Not all questions work well in our format. Avoid questions that are primarily opinion-based, or that are likely to generate discussion rather than answers.
*Don't ask about... 1) Anything not directly related to Unix or Linux
(How is this question directly about either?)
Questions that are primarily opinion-based Questions with too many possible answers or that would require an extremely long answer
(um...how is this question not leading to extremely long answers?)
Like I said -- it is interesting, just not sure that it belongs under the Unix/Linux site, nor after thinking about it, am I sure that it fits the format of this site.