This has been discussed/requested many times on Meta Stack Overflow. The canonical response is here:
Would it be possible to have a "community accepted" feature?
The request is marked status-declined, under the premise that the question with the most upvotes is effectively the community-accepted answer. Actually marking an accepted answer is the ...
Super User is in no way a community specific to Windows products.
While we do discuss Windows-related problems, we also discuss pretty much any other operating system. So putting Windows into the description wouldn't be appropriate.
If you don't know an answer, why don't you simply pass-by?
Your meta-question (quoted above) is based upon the assumption that the question you asked on the main site meets our criteria for what a valid question is.
IF you asked a question that is:
Answerable (with something other than opinions),
Focused on an actual problem you're having,
I don't think so. It may just end up promoting people to answer questions with more useless answers.
The current badges for answering questions, such as "Great Answer" promote quality over quantity, which I think is more oriented towards SE's goal than just having a ton of answers
I am strongly objecting the removal this tag. If title and body contain important (non-meta) information about the topic of the question, then there should also be a tag for it—especially with "big" things like Android. This is the case for any question that deals with a topic of reasonable importance. Which Android definitely has, even if it's just about ...
I feel (entirely biasedly) that this proposal seems to miss a lot of context and community culture.
First and formost, most of these sites are successful by Stack Exchange standards and have met all the requirements for graduation. Where they didn't, they still have large self sustaining communities capable of answering questions.
Lets start with 2/3rd of ...
This has been requested hundreds of times in the history of Stack Exchange. The Stack Exchange founders and team are adamant that voting shall always be anonymous. Requiring a comment to downvote would remove that anonymity. Changes were made to remind people to leave a comment when downvoting, but it has not been made and will not be made mandatory.
I have now created an extension that adds the requested button:
The extension is available on GitHub and should work as:
Please go to the StackApps page for the latest download links and report any issues on the GitHub issue tracker and I'll look into it.
Migration for old posts is not possible even if we vetted it.
Disable migration for questions older than 60 days
questions older than 60 days should not be eligible for migration, either by normal user close-votes or by moderators.
Why would you "nest" keys in the first place? Keys aren't Russian Matryoska dolls.
Just do Ctrl + Alt...
I fail to see what the "bug" is about -- there are no "actual keys or other single units of input" that can't be expressed as <kbd>text here</kbd> + <kbd>text here</kbd>.
The nested keys is a funny concept that serves no ...
The whole point is that you don't want to send tons of "exp" (it's actually "reputation") around. I don't see how it would benefit the community, really.
That, and the fact that it's really a little old.
Oh, and we have a dupe anyway.
So, there's no real point in migrating this.
Comment upvotes are... special. They don't actually really mean anything (I seem to recall, at most a badge). On the other hand, comments are a useful way to extract and elicit more information from an OP, or to suggest something too minor to be a question on its own. A comment upvote is just a way to say "this comment added something" (and we don't downvote,...
I don't know why the particular person downvoted you, but the post was confusing. It was unclear whether you wanted to remove 1+ spaces, or 2+ spaces. First you answered for 2+ then you decided 1+. You have also mixed up whitespace and space in your question, stating space in the title, then whitespace in the first sentence. You should include what you have ...
Originally, the bounty system was strongly linked to "accepting" an answer:
There are three possible outcomes:
You accept an answer. The bounty is subtracted from your reputation,
and awarded to the answerer.
You do not accept an answer. Any answer that was a) provided after the
bounty period started and b) has 2 or more upvotes is ...
I'm not sure the two cases are really symmetric.
When the asker marks an answer as solving their problem (by accepting it), then effectively by definition of the tick it is the one that was most helpful to them. As the most helpful answer, it deserves the bounty and so it is safe to automatically allocate (unless, for some reason, the user has already ...
I don't know what you mean by "can't alow one user one IP".
If you're advocating that a user must be allowed to interact on a site from only one allowed IP, then that's a stupid suggestion. With DHCP IP addresses are recycled across many users and by such a method we're talking about blocking a lot of legitimate users out there.
Account suspensions are ...
A good reason to keep these posts around—and I'm not talking about Viagra or Gucci spam, but excessive promotion for file recovery tools et cetera—is to keep the evidence. Note that I'm using the word "spam" synonymously here: In essence, undisclosed and excessive advertisement.
We've had cases where certain companies or individuals spammed… well, the hell ...
This request hails from the early days of Stack Overflow, and was one of the first and most frequent feature requests to be declined.
The official reference thread is A "friends list" on Stack Overflow would be nice on Meta Stack Overflow.
What it essentially comes down to is what you've said - Stack Exchange isn't a social networking site. We ...
There's literally nothing we can do.
There's even a grace period after the one week/168 hours, but no way to undo a 'lost' bounty or to do anything once the bounty period is over.
meta.se's got an in depth answer that has basically everything anyone needs to know on bounties
Unix and Linux related questions are all on topic for Super User. They're fine to stay here. (So long as they fit the other requirements of being on topic/in scope, not being a smartphone, smartfridge, etc.)
The only time a question is migrated from here to the Unix & Linux Stack Exchange site is if the user asking the question requested so because they ...
Undeletion will help me to ask it anew.
Asking again will just get it re-closed. The question is no more on-topic now than it was when asked.
The post was removed because it isn't the type of question we want to encourage on the site. Therefore, undeleting it would be counterproductive.
Those questions are about the "Send To" action commonly seen on Windows OS when you right-click on an item.
Those that are using it as part of a sentence, they would need to be retagged.
On the whole it's a legitimate and specific tag.
F.lux has a rather specific spelling and there are other softwares that might use the non mangled name.
I'd much rather prevent use of the vague generic spelling and prefer the special spelling f.lux or manufacturer product style of cedrat-flux (as would be the case with the random software I found).
I don't think the synonym is relevant in this case, it ...
the system lacks a final bad-question-keep-for-reference state
This is by design. Bad questions are only kept for longer if the answers are (or have been) somewhat useful. But even then, at some point, they will probably be deleted. I'd recommend you to read The Stack Overflow Question Lifecycle
If users see a lot of closed questions, they’ll note that we ...
ffmpeg is computer software. It's not exclusively used by programmers or audio-video experts—it fits perfectly within the scope of Super User. That is not to say questions about ffmpeg are off topic for Audio-Video Production, but one of the most important rules regarding migration is:
Don't migrate on-topic questions away.
You should be a little jealous ...
Software Recommendations has really just gone public—until yesterday, they didn't even have moderators yet.
When migrating to sites, you want them to be established first. Which means that they've been in beta for a really long time, or that they've gone out of beta already. If you migrate questions to an early beta site, you run the risk of having these ...
Moderators don't have direct access to modify the blacklist; that can only be done by developers, and is non-trivial. However, having destroyed the spamming user and spam-deleted the offending answers, the built-in spam tools should have picked up enough information to hopefully prevent any more spam from this user. If you continue to see that specific link, ...
"bug" would be a meta-tag, i.e. a tag that is meaningless on its own or is only useful in conjunction with other more descriptive tags. We do not create such tags and in fact we actively hunt and remove them.
The less tag already exists on the main site and does not need to be created.