@hichris123 - I see what you mean, but I am talking about offering a second area, in addition to where it shows related. One group would only see the usual area of related, whereas the other group would see an additional area which showed roomba'd matches. Granted, they couldn't be opened by users <10k as they are removed, but the titles (and [closed]) could be shown, perhaps even with a red coloring for the text, to offer some signal that these types of questions were removed by the system.
So you want to "I tried to facebook with Java?", here are all of the related deleted questions, so... don't say we didn't tell you so.
@TravisJ Oh, now I understand what you mean. I thought you were more talking about attempting to classify whether a question would be bad by whether the related questions were bad.
I'm not sure though that a new user would understand red == bad or closed == bad. They see a textbox, they're going to post their question. Most people don't even read the how to ask page.
Ah, well I suppose that is in a sense a related topic of what I was suggesting, as in "what signal can we give from related roomba questions"; but the main idea was just to show the user how many times something like their question was closed and deleted.
As Atwood would say, it is a number of statistics. Even a 5% increase in quality when you are getting 10,000 questions per day is a large amount of progress.
@rene - Skepticism noted, although you have no empirical evidence to support it. Your assertion is more conspiracy theory than fact.
@hichris123 - Yeah, new users may not understand the coloring or whatnot, but it is easy enough to also append [deleted] to the title they see in the result box.
Also, this isn't just for new users. As many lament, experienced users also fall into the common trap of asking poor questions.
@rene - I am not sure how to determine if the question was probably a common pitfall aside from just offering more information and hoping that it is obvious to the user for clear result sets. The idea would be to show them roomba'd question titles similar to the related question dropdown that is currently in place.
The reason that I think roomba questions are good candidates is because they tend to last for a while on the exchange, and that means they are probably not offensive or spam, so they were just questions which were off topic or did not abide by the "how-to-ask" guidelines.
Any possibility one might consider adding the reputation leagues to SEDE?
As of now, there is no true way to use SEDE to extract reputation over time for users. One would have to build queries to aggregate votes, some of which may/not count once reputation cap is reached.
Of course, ideally, one would like to be able to extract the reputation per day, if at all possible, but leagues are a good start.
Most of the inspiration behind the idea is the large amount of use the current related area gets already from users. Many times I have seen in posts that users will type their questions in to the ask question page to look for duplicates because of the decent level of accuracy. If that could also be used to view questions which were clearly not a good fit for the exchange, perhaps that signal could be used by users to change their minds about asking that type of question or to make edits.
I feel like it wouldn't take much effort to implement as it is almost copy paste from existing behavior, and it shouldn't take much resource to provide as a service because it is a very narrow area of use and a small amount of data.
The only issue is maybe that those questions have no quality indicator, except that they are being roomba-ed. I agree they are not spam/rude but beyond that you have no real indication how valuable they could have been.
But maybe some data would help to see what would come up
In theory you could run a SEDE query now to see the questions that get roomna-ed thid weekend
If they got roomba'd doesn't that mean they were already closed? Isn't that a decent level of at least low quality?
I should really write a linq-to-sede implementation at some point.
I am not as savvy with classic sql
Overall though, I think there is opportunity to make changes to the ask page. Apparently it could come up for redesign or improvement this year. At least to get the project started. It would be nice to offer some set of ideas for the team prior to them breaking ground in that regards.
@JeffAtwood, agree. I've long wanted to offer a "guided" ask that's the default for new askers, with more of a wizard-style guide with separate fields for "code" what "what you want to happen," "what is happening", "details about the version, system, etc.," I think we could easily help users NOT crash into most of the fixable mistakes that get made. It's been on the "definitely worth doing... Soon" list too long, but I'll push to get this locked in on a "this year for realz" roadmap. — Jaydles ♦Apr 18 at 12:38
@TravisJ in SEDE we only have postswithdeleted (no title/body) but the posthistory table only holds non-deleted posts and I expect the roomba event to be recorded there in production
So you need a CM to run any query in the first place
Hm, well I wouldn't want to pester anyone on a friday for that
Perhaps some common poor titles could be analyzed for roomba % as a start or something. Like for example, what percent of questions matching "what is a null reference error" were roomba'd? Or some set of titles, you are probably more in tune with words in titles or phrases in titles that are red flags.
What characteristic behaviour does our community exhibit? Is it possible to capture this through some statistic or visually through graphs?
Certainly! There is a host of information available through the SEDE. This post is meant to collate some of the discussions contained within How can we expl...
well, it would make reputation growth analysis and leagues queries much easier and even correct as well as how much rep did a user had when they posted that q or a.
I would support it but for Stack Overflow it would mean a table with many, many rows
@rene True. On a per-user basis, the system seems to readily know how much reputation a user had, for all of time... I doubt that it calculates it every time...
> After this eulogy was posted, @cardinal requested the opportunity to return to the trenches and has re-acquired the moderator diamond. Welcome back, Cardinal, as our first resurrected (zombie?) moderator! meta.stats.stackexchange.com/q/3151
A similar question was posed quite a while back, without much specificity. The only answer identifies the taxing nature of a SEDE query on the server in order to get a rough estimate of the user reputation over time. This is rough because it doesn't include any reputation corrections (due to dail...
The keyword of my question is "display" not "calculate". I'm not looking to increase the precision of Scilab's calculations, just to display a larger number of digits, no matter how correct they are. Thank you for your answer though. — Paul Warnick4 hours ago
user315433
I was concerned that my remark about appending 111111111111111111111 to decimal output was mean-spirited.
user315433
Turned out this was exactly what the OP wanted: moar digits.
