There are several things you can do, in whatever combination you feel comfortable:
Downvote (the answer is incorrect, after all)
Leave a comment explaining why the answer is no longer correct/current
Edit the answer to be correct. (This can be tricky, though, as it may look to some like you're changing too much of the original)
Personally I go for 1 and 2. ...
There's nothing wrong with asking and answering simple questions - after all they're only simple if you know the answer.
If you don't know the right terms to search for then no amount of Googling is going to help.
It's also worth posting if you have to go through several links or wizards to get to the answer or it is buried somewhere in the depths of a ...
Such questions should be Closed with the custom Off-topic reason: Questions on applications or application features that are no longer available are off-topic for Web Applications as no one will ever be able to make use of the answers again.
In some cases, such as Hotmail, there is a clear successor app. The tag for the retired app should be made a synonym ...
Yes, a "this is not possible at this time" answer is perfectly acceptable.
You should back it up with why it's not possible - quoting and linking to the relevant section of the help (if there is any) for example.
Adding a workaround would be a bonus, but not essential.
Of course, you should be prepared to have your answer downvoted at a later date should ...
I'm not an active user on this exchange, but I just noticed the question, so here goes my thought.
Update 08/21/18: It is the #1 result and they even created a nice onebox for it.
If you search I've lost my gmail account it's the #2 result (after ads)
Change lost to can't find and it's (still) the 3rd result, other variations will still leave it in top 5
Posting on Web Applications does not require signing up.
New users can just come in and post their questions.
However, they can't create the orangedox tag unless they also have 300 reputation. But, higher reputation users will shortly come along and add the tag if it fits.
Keep in mind that you can't funnel all your support to Web Applications, as it has ...
There are three important aspects of a question post at Stack Exchange, and you shouldn't neglect any of them. They are the title, the question body, and the tags.
This is the advertising for your question. This is what people will see in the question list on Stack Exchange, as well as in the search results in web searches such as from Google. The ...
There was no political intent here. If at all, I took a very apolitical stance and removed something that was not germane to the question at all.
A reference was made to a Twitter profile of a figure that is...controversial in many circles. Since it added nothing of value to the post, and could be construed as inflammatory/offensive/inappropriate, I ...
Google Glass is based on Android. Why wouldn't we discuss it at Android Enthusiasts?
Issues with an Apple smartwatch would be best served at Ask Different.
The issues you might encounter with Facebook are going to be quite different depending on whether you're using the desktop browser version or the Android app or the iPhone app.
Then what about PC ...
Head over to your profile, click on My Logins & click on Add More logins.
Now, at the login page, login with another openID provider, or create a Stack Exchange account. You'll be able to login to your account using the selected openID provider or using Stack Exchange account
As Al has mentioned, anyone can post questions to the site, regardless of reputation. Just about anyone can answer as well. The exception to that is "protected questions," which one must have at least 10 reputation to answer (not including the association bonus, but that's not applicable in your case).
In addition to either of those, anyone can ...
Without a more concrete example of the kind of question you'd like to ask, the answer to your question here is: It depends.
As for WordPress ...
I have amended the tour to be more specific on what is allowed. The Ask About... section now states:
Augmented browsing extensions that directly relate to the use of a web application (Greasemonkey scripts for a web application,
I have left the Don't ask about... section as it is. Hopefully that will clear up any confusion.
The existence of a tag does not automatically make something on-topic.
Be that as it may, yes, Github is, among other things, a Web application. The trouble is is that it's a tool used almost exclusively by developers. I don't think that it's necessarily off-topic here, but you, and future readers of your question, are far more likely to get a useful answer ...
Without going into too much detail - it's not my place to say who may or may not be stepping down - we (the mods) were contacted by the community team for the simple reason that it had been 6 years since the last election.
After a bit of discussion it was decided that, on balance, we did need an election.
Priorities change for people, real life intervenes ...
I would say, yes, they should be closed. However, I don't think we should go out of our way to find them. Just vote to close them when Community pops them to the front page.
I asked a similar question about Hotmail, but that was motivated more by all the people coming here and complaining about the switch to outlook.com.
In this case just retag the questions. The new-twitter tag will then just disappear from the system.
If there were 10's or even 100's of questions with the tag I'd create a synonym, but for such a low number it's not worth it. Even as a low rep user you can suggest the edits and when they get accepted you'll get some more reputation.
As long as the questions asked here are on-topic for Web Apps, they'll be welcome, although I expect that they'll require some very specific knowledge that may not be well-represented here. If you're planning on answering the questions then that's all to the good.
I would caution you, however, against attempting to turn Web Apps into your general-support ...
I think that the (lack of) voting, close voting, editing, and tending the queues are all definitely due to a lack of active users, as both Al and phwd have pointed out. The fact that we have closed questions based on the votes 5 regular users only a handful of times has been more bothersome to me than the voting for a while, to be honest.
As phwd pointed ...
As the other answers here suggest, the bit of text that was removed is completely superfluous to the question. We try to make questions on the
Stack Exchange network relevant to others, so personal anecdotes and other bits of nonessential contextualization are often removed from posts. The text that was removed from your post fits into that group, and the ...
I wasn't involved with this, but since you asked for feedback, I'll share some personal opinions:
If you're asking how to improve the questions, one way would be to flesh them out.
It might be helpful if the questions stated the requirements more explicitly. When I see a very short question, I often start to wonder if maybe there are some requirements that ...
What we did on WordPress Stack Exchange might fit here too. Slightly changed copy from WPSE:
This question does not appear to be about Web Applications within the scope defined in the help center.
Now we can use the proper flag/close reason, and the asker gets a helpful link.
Web Apps is for users of web applications.
Media-wiki is a web application.
Therefore, if you are asking about the use of media-wiki then the questions are definitely on topic. This can include the end user or the admin user of course.
However, if you are asking about the installation of media-wiki then the questions are off topic. Webmasters is probably ...
The situation has changed:
All recommendations should now be posted to the new QA site Software Recommendations.
Questions should be tagged web-apps.
Please note that rules are very strict over there:
Questions are required to explain all requirements if fine details,
Answers are required to describe how the app meets each requirement.
Questions should be ...
The faulty spelling is a part of your assumption that the Google support didn't really know what you were talking about. On the other hand you use it to make a statement that there's no gapless playback on Google Music.
In this particular case it is an integral part of your answer and it shouldn't have been altered. There is an option to rollback edits. ...