Hey folks! Wondering what the general consensus would be. Getting feedback that something I posted yesterday might be interesting for the wider MSE audience, not just MSO (although the original conversation started on SO). Is there a recommended best practice for how I might cross post without actually breaking the rules of cross posting for a post like this? meta.stackoverflow.com/questions/433769/…
There is. However, I think you should probably make a new question. There's a decent bit in there that, at least I think, is kinda site-specific to SO. For example, Discussions doesn't really relate to the rest of the network.
Cool! I am also checking with CMs on this, but just want to know what the general best practice might be for a more unusual post like this (as mine tend to be).
@Spevacus That's a good point and one a CM actually mentioned a moment ago. Would you say a companion post for MSE that might links to the MSO post would be good approach?
There are also probably broad-strokes discussions worth having about question closure in general and site topicality as a whole. It's nice for SO, monolith that it is, to have its own big overarching discussion about closure, so keeping your current post there is worth it IMO
@EmmaBee I'd say so, yes, just with some broad summaries of what you're looking for out of discussion about the subject. My recommendation would just be to have the existing posts be supplemental and open the floor for the broad, network-wide interpretation. I imagine you may get some interesting responses when you target the whole network rather than just SO.
@Sonic-missesShadow-Hedgehog I just wanted to end a sentence to Shadow Wizard, unfortunately broken a year ago. And now, coming back after a year, I see that he is no more since a month. It is terrible.
@EmmaBee I suggested many times to prefer migration against closure and deletion, if it is possible. I hit walls. I did not get a for me acceptable explanation, actually no explanation et all.
@Spevacus Looks people wanting to earn a lot of cash by coding, but not wanting to end their sentences with a ".", might really have a better place on the chatgpt.
@EmmaBee Honestly, it might make sense for there to be an MSO-MSE migration path and vice versa for regular users. Most "relates to one specific network site" (thousands of questions here) belong on MSO, and MSO has many questions which belong on MSE
@EmmaBee For reference, mods can migrate to any site - including to different child metas - if the question is less than... six? months old, and CMs can migrate to any site regardless of age.
Migration is an "off-topic" flow: just because a question could also be relevant on MSE doesn't make it off topic here. Respect which site the user asks on: jumping them back and forth between sites is not a pleasant experience (especially when they don't understand the network). — Robotnikyesterday
@StarshipRemembersShadow Many of the questions that are closed as about one specific site that are only relevant to SO are either from before the MSE-MSO split, or asked here because the OP is suspended on SO (in which case a migration will fail anyway).
@EmmaBee I haven't read the post closely enough to give a definitive answer, but scanning through it, it looks like it's mostly relevant to SO. A companion post describing its relevance to the rest of the network might be a good idea if you want broader attention brought to it.
@Twineee-MissesShadow-Wizard I personally disagree with the commentor there. The topic of MSU is questions about just Super User", whereas the topic of Meta is "questions about the whole network" (or multiple network sites, Meta itself, Area51 and stackapps, but you get my point)
@StarshipRemembersShadow Not refuting, just tossing this out there: The question would certainly just be closed as a dupe of... Something here on Meta, or as appearing to not seek input/discussion.
@StarshipRemembersShadow It's been established for many years at this point that posting questions that theoretically are about the entire network are on-topic on child metas. Users are not required to venture beyond the boundaries of their site to discuss issues that affect their usage of the site.
How is that any different from posting a question that is off-topic somewhere and saying "well I shouldn't have to venture beyond the boundaries of my site to ask my question" or "well I didn't know that site existed" so therefore my question should stay on its current site
@StarshipRemembersShadow That's... quite the false equivalency. The point is that if you find a bug that affects the site you use, or you have a feature request to improve the site you use, then using the dedicated part of the site to discussing the site itself is an appropriate way to post those questions. You shouldn't have to create an account on a different site to report an issue with the site you're currently using when there is a section of the site dedicated to questions about the site itself. That has nothing to do with saying that an unrelated topic should be allowed so that users don't have to go elsewhere; it's very much a related topic.
@Glorfindel Hey, your user script linked in this answer seems to no longer correctly recognize sites that use \$ delimiters for MathJax. Can you please fix?
@Twineee-MissesShadow-Wizard I find that true as well :)
@Mithical Why? If I happen to along have an account on Site X, but my question is a better fit for Site Y, the fact that I would need to go to Site Y doesn't mean I can post stuff that belong there on Site X. It's not very much effort to visit a website...
@StarshipRemembersShadow You could also ask in the Stack Apps room. Without looking closely, a "fill in the blank" close reason may be appropriate here.
On second thought, the obsolete tag description mentions "or no longer relevant". See, for example, what @M-- did here.
