I sometimes have questions that are suitable for 2 or more Stack Exchange sites. For example, a question on configuring a development database for a website.   This question could be posted on  or .   Wouldn't it be a good feature if you can post the question on one site, then just register it as a 'cross-site post' so that the question and all its answers can be visible on all the sites that it is marked for.   This will cut down on cross-site posting, and allow the same question to be answered by experts with different expertise.   This will promote cross site collaboration, as different users from different sites will be able to see how other parties are answering or commenting on the same question.
32538
I've been a Stack Exchange contributor for a couple of years now, currently most active on . One thing that keeps coming up is questions that would appeal to audiences on two different Stack Exchange sites but there are almost no features taking advantage of these questions. On travel.SE we have crossover questions most often with  and possibly next most often with  - but it can happen with almost any SE site. Today alone we had  with  and  had . I am absolutely sure that this must happen all the time between arbitrary pairs of Stack Exchange sites but the only feature that takes advantage of it is the possibility of migrating off-topic questions which leaves the original question acting as a redirect across the two sites. I think there is a missed opportunity to build the network between sites where users of one site don't realize they could make valuable contributions to a sister site they have had so far little to do with. At the very least there could be a way to &quot;advertise&quot; a question on a second site that could be interested in it. Probably by listing it in the sidebar where there are also links to meta questions, linked questions, related questions, new blog posts, and But there could also be some kind of features that make some sort of acceptable crossposting. There could be gamification/badges added around building cross-site questions or whatever else you can think up. I think this is a great way for people to spread their expertise from their main site onto other sites, to make the network stronger and more cohesive, to bring more attention to questions that would have a divided audience between two sites. I can think only of positives and no negatives. Does anyone else have some ideas to add or think this is a bad idea for any reason?  Example crossover questions: Here are some links to some crossover questions I've been finding in the Stack Exchange network here. (This was previously posted as an answer, but more people wanted it to be part of the question.)   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :   ▶  :
1183
I think there should be more Stack Exchange networks available when flagging a question to be migrated. For example I'd think that the following question:    ...would be a better fit on unix.stackexchange.com instead of Stack Overflow. But without the option to mark it so, I feel hesitant to mark it.
3520
I often use Stack Exchange sites from my smartphone. It works great, but I always have to switch to full version to see view counts of a question. Can you please add it? There's plenty of space on question page for it to place. I request community to suggest a location.
80746
Why can't there be (or is there?) a way to gain credence from one's reputation on one site to be able to do something on another (SE vs. SO)?  As someone who has long consumed StackExchange, StackOverflow, SuperUser, but only within the past few years posted questions or answers, I am confused and frustrated by the whole reputation thing.  I understand why reputation exists, but it is frustrating to want to upvote, comment, answer, or whatever, and be told you are not allowed because you don't have sufficient reputation.  If I had some new original questions I needed to ask, then I could gain reputation, but "the system" seems to think I am unworthy or clueless to be able to contribute or assess.  Finally I had enough rep (small by most standards) to be able to vote, and maybe even comment(?) on StackOverflow, based on technical questions.  But when I went to Stack Exchange for a question on OS X stuff, I have to start over with 1 rep.  Seems a bit like a slap in the face, particularly since (so far as I know) some questions could appear either place.  Yes, I have ready folks talking about exchanging bounty and how it is more difficult to earn rep on SE than SO, and I don't claim to know all about bounty and the ins and outs of types of rep.  But I do know that I feel as if I have to start over in each meeting place for technical questions, and it is a disincentive (for me) to be involved.  I realize not all (maybe nobody) will agree with my sentiment, but since I only have 1 rep, I guess folks' downvotes won't hurt me, right?
13945
Are the questions submitted on SO and other SE sites initialized with 1 view, or does the first view belong to the user who posted it?  Why is a question given a free first view? It just appears, as soon as the question is published.
1039
I frequent Stack Overflow a lot and there are many questions that get downvoted because they don't fit in the "Code only" question format. There are many users who will immediately downvote people for asking the question in the wrong place, but whoe never provide suggestions about WHERE they should be asking that question.  My question is: Is there a good description of what types of questions are acceptable in each of the Stack Exchange family of sites?    I know there is an FAQ, but this really does not address which types of question is fit for each site.
44101
I'm wondering why there is so much work to close duplicate questions.  We can see that the Stackexchange concept allows users from all around the world to find answers very efficiently.  Wouldn't it be better to have the maximum number of answers even for the same question as each one is slightly different. The more there are answers the more a user can find his one.  Are we limited in disk space or something ?  Imagine a question badly asked one day then the same well asked later that is easier to find from google, which one is supposed to be closed as duplicate ?
71605
I've recently run into many questions where to author asks several related questions in one post, many of them asked before.   I'm wondering what out policy is on such questions:   Should I vote-close them as being not constructive? Should I vote-close them as duplicates? Should I leave them be? Or even suggest an answer?    - Each of the questions: Waiting for an AJAX request with selenium, and headless browsing in selenium have been asked here before, but he asked both in one.  I've done my best to search for similar questions here in meta but I was unable to find any, reading appreciated.
84583
The Problem - The Stack Exchange network has so many sites with more being added all the time, a user probably doesn't know that a Stack Exchange site exists to answer a question they might have. In addition, when asking a question, the user might not know the best place to put the question. Asking the question on the wrong site could be downvoted, and it might not be in the user's best interest to ask the question if he/she doesn't know exactly where it belongs.  The Idea - A Stack Exchange site where you can ask any question, and it's up to reviewers of the question to decide which site would be best suited to answer the question.   I don't know much about the process for migrating questions to other sites as they stand today, but I think a voting system would be good, to allow reviewers to vote where the question belongs best, or someone with enough rep is allowed to move it directly.   The conditions that determine when a question is migrated could vary. Some ideas:   After a certain period of inactivity When the vote gap between the #1 and #2 result is large enough   The voting system should also have some way to denote that this question doesn't (yet) have a Stack Exchange site suited to answer the question.   When asking the question, the page could provide a list of similar questions as it does now, and "suggested site" box. This way, if they're writing the question they could see some suggestions as to where the question might belong. They could then select one of those sites and have it submitted on that site. The primary data source for this would probably be the tags. For instance, if the user enters tags that have a lot of followers on StackOverflow, the page would suggest that the question might belong on StackOverflow.  This feature would allow users to ask questions without being as concerned about where it belongs among the vast Stack Exchange network. In addition, this could be a valuable resource in determining what Stack Exchange sites people would like to see. If there are a lot of questions that are filed as "Site Doesn't Yet Exist To Answer This Question™", that would be an indicator that there is a need that Stack Exchange isn't currently fulfilling.  Please comment with any suggestions or criticisms.   PS: I hope that this is the correct place to post this suggestion.  Edit  Maybe a dumbed-down version of this might be useful. Instead of having the review process, just have a page for a user to enter their question, get suggestions to where it might belong, and choose at the end where the question belongs. Right now, choosing where to ask the question is the first step. I think moving it to a later point in the conception of the question would allow the asker to better categorize the question.
3726
There have been discussion earlier if similar but different questions should all go into one question post or into several independent (which may link to each other). The general consensus is to ask several separate questions:      I fully agree on that. However, when I do it, often enough I get votes as exact duplicate.  One example:    closed as exact duplicate of    It is obviously not an exact duplicate because it asks about try_lock which does something different than lock. It still may be that the answers may be the same, however, I am not sure about that (and the people who closed it also don't, regarding to their comments).  I am wondering how I should handle it in the future. Because of such problems, I start to put several questions again into one question. But then I often don't really know what I should choose as the answer if they only answer one of the questions.  When I had them separated and the second and the second one gets closed, I am also not exactly sure what I should do if the first question was already answered but the answer does not answer my second question (see my example above -- the answer about lock does not mention try_lock at all).
41962
Sometimes don't understand this question better suits to which SE site. So I may have account on that site but not able to understand that question should be asked there. Or may get similar question on that site. But I wouldn't like to see faq of every site to check . We can see different types of areas here . There might be question which can fit into 2 or more sites.  Is there any central location for what kind of questions can I ask on every SE site? Or is there any collection of site with it's one faq saying .  Update: I am saying is there any central location also for reading what kind of question I can ask on this site like  And I am not saying to remove What kind of questions can I ask here? faq from all sites. I do read faq of every site. But it would be good if I know what kind of question I can ask on each site when do anyone join SE community. It would be helpful for searching my similar problems on that sites also.
75681
Sometimes a question can be on-topic for one site, but more likely to get answers from a different community, for example:   In this case the question is on-topic for Ask Different and perhaps off-topic for Electrical Engineering. However it's likely to have more understanding and knowledge and get better answers in Electrical Engineering since it's about the Arduino. Many variants of this example case also exist where the question is on-topic on both sites or somehow sits in the middle, etc.  Something very similar to my suggestion below has been asked before:  however I have incorporated the feedback to that suggestion into my suggestion so that it avoids the problems detailed there and hopefully makes it work better for the asker, answerers, and the communities and moderators of both sites.  The suggestion:  When positing such a question you would post it on the site where it's more on-topic (Primary site) and select an option to create a proxy on another site (Secondary site), you would choose the other site and at the same time pick the tags from the other site.   Posting this question would NOT create the question on the secondary site as well, it would create a proxy-object for the question and tag it with the correct tags. The primary site would post the question immediately as normal, but on the secondary site the proxy-question would need to be be moderated and approved before the proxy object becomes widely visible. When browsing the secondary site, users would only see proxy-questions for questions held on sites on which they already have an account (There could be a user setting to show proxies from all sites if desired). When clicking on a proxy-question you would be taken to the primary site in a new tab (the question is only in one place). Answers would only be posted on the primary site. Proxy questions could be visually distinguished from normal questions by various means: using different colours/style, an icon or obvious 'proxy' tag, putting them in a separate section, etc.   This idea of using proxy-questions may also help to solve a few other cross-site issues. For example when closing off-topic questions, moderators may also be able to convert the question into a proxy-object of a duplicate question on another site (I've seen suggestions around this too).
93964
Often I have a question, in a specific area (say Math SE or English SE) that is appropriate for the child meta of that site.   Then I realize it is not particular to the meta for that site but for Meta for all sites (like this question itself; I wanted a link to Meta Stack Exchange from meta.english, but realized no meta sites had such a link).  Wouldn't it be nice to have a link in all meta sites to Meta?
90974
My question is that I asked a question on stackoverflow.com and  I want to share my question to all other technical stackoverflow linked sites like ,  etc.  I want to share my question on only selected sites related to stackoverflow. I don't want to post duplicates, I just want to make my question visible for the users on the related site, that may not necessarily be the members of the both sites, but may be competent to answer.  Is there any option in StackExchange network to perform this operation?  Can any one suggest me how I can do this?
3101
I love Stack Exchange and really hope to see it evolve, maybe into a helper page for sites like Wikipedia. One of the problems I have as a user is the kinds of questions I generally have are for lists of answers, or to get a vague and rambling set of answers to dig through and collect the pieces I'm looking for. For instance, it would be nice to ask for a list of great food websites (as an example only) and then get a listing of these sites.  I'm wondering if there is a sub-section or side-section of Stack Exchange that offers this kind of back-and-forth that is restricted on the Stack Exchange topics normally? I get that sites like facebook offer this to one degree or another, and message boards, etc. But none of those sites have the indexing, tagging, searchability, and referencing options that Stack Exchange does. So I'm hoping that there is a Stack Exchange-approved model for this question that I just wasn't aware of yet.
47362
I think its good if we have one user account for all the SE sites(i.e. a StackExchange Profile).   Profile page should facilitate (from account owners pov):   List all the SE sites we have subscribed and we can visit the site account by clicking on the link. A summarized status of each account (e.g. whether there are new replies and comments) List SE sites we have not subscribed and instant subscription capability to any SE site.  Facility for grouping and using separate names.(It seams, some users don't like the idea of one profile . If a user doesn't want others to see all his/her accounts, then user can use separate names per group or account and set-up visibility settings so only the accounts with a similar screen names will be shown together. Yet account owner can manage them at one place )   Having a SE profile page will allow users to have separate accounts for each site, still managing them will be much easier. I am not suggesting to remove the profile pages we have at SE Q&amp;A sites, I think separate profiles should be there since each site serves a different cause. Adding a link on each SE Q&amp;A profile page, which will direct the user to SE main profile will be sufficient.  In the prevailing system visiting a SE site, which we don't use often, is a 3 step process. Lets say one wants to visit SE TeX but he/she has bookmarked StackOverflow only. Then steps should be StackOverflow &gt; accounts &gt; SE TeX. But if we have a Profile page at StackExchange, then it will be a 2 step process SE Profile &gt; SE TeX.  If we have a SE site that we visit very often then we can bookmark it in our computer. But bookmarking all the SE sites we have signed up is pretty messy thing to do. So if SE provides a "StackExchagne Profile" page we simply can bookmark our profile page instead of bookmarking everything.  From StackExchange's point of view, enabling grouping facility will reduce the size of the user database.  Similar ideas were discussed in following pages, but I opened a different Question since the facilities I am requesting are different to them.   (1)  (2)  (3)
631
There seems to be more than a few computer science/programming Stack Exchange networks (is that the correct term?). Stack Overflow, being the first, has by far the most users, questions, and answers.  What is the reasoning for creating the others, and are there clear guidelines for which kinds of questions should be posted? I can see a large amount of potential overflow, many cases of people not getting a good answer to their question, because the person who has the answer isn't browsing that particular network at the moment.  I understand that they were probably created for organizational purposes, but wouldn't it almost make more sense to just have them as categories under Stack Overflow, keep them separated but still connected, instead of making people have to create multiple 'account's, one for each network?  I am sure there was a very good reason to break them up, but as someone that is new to SE, it can be somewhat intimidating to decide which one to post in to ensure you get a good answer. For example, if I am a computer science student, my first instinct might to be to post in the computer science network, until I see that it literally has 1% of the users as the Stack Overflow network, which still seems to be for programming/computer science related questions.  So my second instinct would then to be to post it into the Stack&nbsp;Overflow site on the basis that I have a significantly higher chance of my question being seen and getting a good answer. Then I notice that there is also a 'programmers' network, and I don't even begin to know where that fits in. I, and I am assuming most people, will probably just post on Stack&nbsp;Overflow to be safe.  My question is, other than the short little description blurb of each one, is there a clear cut set of guidelines which what each network is intended for, what kinds of questions should go to each one, and is anything being done to encourage people to post in these newer, smaller (more specialized?) networks as opposed to just posting in big daddy Stack Overflow?  Now again, this is for computer science/programming/"why isn't this code doing what I want?" related questions, I am not saying that if I had a question about Linux or WordPress or something I would have the same confusion.