A few of your suggestions are already implemented—we regularly recommend r/AskHistory to users who want more discussion or want an answer but aren't necessarily interested in having it vetted for accuracy and we're also in regular contact with moderators of r/history (some folks are mods of both subs); we aren't in regular contact with the moderators of r/AskHistory, mostly because they take a very different approach to moderation than we do—theirs is a very hands off approach to moderation in which mis/disinformation is addressed (or not) through users via decentralized moderation (i.e., votes) rather than mod intervention. Both subs are listed in the sidebar as part of the history network of subreddits.
I'm not an historian—I'm an information scientist who studies moderation, but I have a background in library and information studies. What you're describing in your second paragraph:
But where do people go who just want to ask a question where they might not know what information it is they're seeking?
has a name in LIS: Anomalous State of Knowledge (ASK)—you know you want to know something, but you don't know enough to be able to articulate it. This can make question asking (or searching for information in google) really difficult. Browsing (or looking through existing information) is a much better solution for people in the ASK state. Being a Q&A sub, this is a bit of a challenge and one that moderators and flaired members of the team address through the FAQ in the wiki, so that someone who wants to read through background information on Greek mercenaries can read through the existing answers and, ideally, ask their own question from there. Another thing moderators here do that's less visible because it tends to happen in modmail or in removed question chains is provide coaching on how to ask questions. For users who want a quick answer we direct them to the dedicated thread for short answers and try to prioritize answering those when we can. There are also a set of flairs who regularly respond to those kinds of questions too.
These are all initiatives undertaken by mods and supported by expert flairs to make sure our users have as many ways of getting the information they want while still maintaining the goals of the subreddit—to provide question askers with comprehensive, accurate, and trustworthy responses to their question. I guarantee that no one on the mod team is going to say: "We don't care about raising general knowledge and interest in history" because that's the foundational goal of the subreddit and the primary reason why members of the modteam dedicate hours of their time everyday to the community—I've written about that here and published more details here.
There are a few challenges of course—Reddit's design means that these efforts are harder to find (for a while, and perhaps still, the wiki wasn't available on mobile, which is where the vast majority of the sub's traffic comes from) and it all takes time and labour. Every time a moderator makes a visible comment they are always at risk of pushback (which is benign in intent, but can be stressful, particularly when it happens en masse) and at risk of abuse. So it's often a balance between wanting to do more and having the time and the emotional energy. Because some of the feedback requires specialist knowledge it's not simply a case of adding more moderators. Moderation is a lot of work and moderators are human. There's a ton of stuff that the team works on and does to address the issues you raise, it's just hard to get it out there and make sure people see it.
Completely off topic but you just nerd sniped me. As a developer a frequent problem I run into recently is that google favours more popular answers over more recent, so if for example I'm searching for answers on an ES6 function that shares it's name with a jQuery function, the newer ES6 threads are completely obscured by the bajillions of jQuery questions. Do you know of any good techniques or guides that help a search under such conditions?
Also this might be the first time I've asked a librarian an actual librarian question.
Google provides a few tools that can help with a situation like that:
When you know the results aren't what you're looking for because of age, you can use the "Tools" button to filter by a date range. Often setting a "From date" newer than the majority of incorrect results helps a lot.
When you know the results aren't what you're looking for because of topic, in this case because of the use of a library you do not want (jQuery), using the search exclusion operator
-(a minus/hyphen) prefixed in front of that word will remove those results and hopefully leave you with more relevant ones. For example,myfunction -jquery.Modern Google tries to guess what you mean and can change or convert search terms. If you notice one of your search terms is not actually appearing in the results, surrounding that term (or set of terms) in double quotes should force Google to look for results where those terms appear verbatim. For example, if a search for
myfunctionis giving you results likemy other function, use"myfunction"instead.Don't be afraid to add more terms to further refine your results! You can always go back if they lead to results you don't want.
Sometimes, using more specialised collections can help. For example, searching StackOverflow directly (and using its tagging system), searching mailing list archives specific to your library, GitHub issue trackers, etc.. That said, a lot of developers like to write more opinion-based pieces on blogs, which aren't discoverable with this method.
More generally:
Of course, none of this necessarily helps when you don't know what you're missing and don't have enough clues to prompt search engines along. In that case, actually asking other people isn't a bad idea :) Mailing lists, Stack Overflow, IRC chatrooms, even some subreddits can be good places to ask questions.
I have had experiences, increasing as time goes by, of Google seemingly utterly ignoring date range in their responses. I don't even get a message akin to the "no results found matching X" you get with keywords.
Thats because a lot of websites are spoofing the date ranges - reddit does it now. If youre looking for old threads through a google search it obfuscates the thread age and tells you most of the page results were from within the last few days ago, when it's a 3 year old locked post. Its just another bullshit SEO optimization that only serves to undermine the purpose of archival
AMAZING.
Thought I was going crazy. Getting 8y old reddit posts at the top of Google results that the search result displays as 1y or less.
Very interesting, thanks!
putting stuff in quotes doesn't seem to work as well anymore either.
In your Google search, include
after:2021-06-30or your required date range.Beforealso works. Also include a negate:-jQueryto exclude results which contain that word.Problem solved
I have had experiences, increasing as time goes by, of Google seemingly utterly ignoring date range in their responses. I don't even get a message akin to the "no results found matching X" you get with keywords.
Can you not still add -JQuery to the end of your google search to remove results that include that word?
That may work in that specific circumstances (IDK) but in more general queries of this type I'm loathe to take that approach because of the high probability that the articles I'm looking for will make passing reference to the other thing, if only to point out the differences and the fact they are frequently erroneously conflated.
"Today we are talking about the foo function in ES6, users of jQuery will rejoice that it has finally been added to the standard!"
or else it's in the meta data or in navigation, or a list of "related" content.
If you go in stackoverflow you can search for your function there and filter out jQuery, or specifically search in the ES6 tag.
Oh man, trying to look up pre-covid mask research is horrible nowadays
The fact i now know theres a phrase for knowing so little i dont know what to ask, i feel alot mroe confident asking a librarian for help.. so thanks!
In that specific example, you should use the MDN.