We have 6 (5 + myself) LaTeX aficionados who would like to try getting a TeX based community going. All are current or formerly active members from the [TeX.SE](https://tex.stackexchange.com/). A private beta period would be preffered over public just to get things started on the right foot, experiment with how it will go, and make sure everything is copasetic before making a more public invite.
**Update:** The community ended up trying [something that's more similar to SE](https://writing.codidact.com/questions/39219) at least for now. (Basically, we needed a home Right Away because of SE, and a temporary site that looks more like SE made for an easier transition. The long-term decision remains open.)
I'd like to see a community for programming questions. I'm quite shocked to see it hasn't been created yet.
I'd like to start a C++ programming questions site. I ask and answer a lot of C++ questions over at StackOverflow, or at least I did. I'm looking for a new home: https://stackoverflow.com/users/2642059/jonathan-mee?tab=summary
I'd like to see a sub-site for [R](https://www.r-project.org/) coding and troubleshooting. I'm not volunteering to be a moderator, but I promise that I'll be an active member of the community.
Do we have enough material and interest for a "home computing" site? I'm imagining something like Super User, but not restricted to PCs -- Macs, phones, tablets, etc would be welcome too. (There might be overlap with \*nix, which we should discuss.) I expect most questions would be about software and most of the rest about configuration, but I assume there'd be some hardware-related questions too.
This sounds like an idea that is great concept but would be very problematic in practice. Most conversations are not rigorously threaded in that way. While the incidences of reply pings increase a lot when there's a lot of crosstalk happening, the nature of a filter means that _only pinged messages_ would get captured. In my experience, crosstalk usually dies down and a lone conversation carries on; but a filter would mask this part of the thread.
I'm a fan of **linking** to "duplicate" Q & A but not so much of **closing** (= preventing answers) at the same time. This is something I think the SE model *almost* got right, but not quite. In most cases I have encountered, a question is rarely an **exact** duplicate (such that no useful answer to the specific question is possible).