30

I just found this post today, over 6 years later. I noticed this pattern on my own approximately 18 months ago. At the time, if memory serves, there were over 3600 such requests for gratuitous nudity. Since then, mostly in spare moments during dull meetings, I have been slowly knocking down the list. As of today there are zero. Some observations I've made ...


29

I've fixde the typo. With you in the next buidl (rev rev 2013.9.30.1041).


25

I'd say, no that's not ok. Sure, poor grammar in the edit summary might be cause for concern that the edit itself is poor, but it is far from a guarantee that that's the case. It's not fair to dismiss an edit without even a glance, if all you are basing your opinion on is the comment. Instead, evaluate the edit on its own merits. That's all that really ...


23

Fixed, should be available in your failed review audits so-o-on (like 2013.7.30.xyz)


22

This would require a fairly massive translation effort. We do have some support in the engine for such changes now, but the work required would be a waste without sufficient support. Stack Overflow in Canadian was proposed a few years ago, but deleted due to lack of interest. If this bothers you enough, consider starting a new proposal. Note that we would ...


20

they are not grammatical or spelling errors that make questions harder to read I disagree with that. Using capitals and paragraphs the right way actually makes the post easier to read. And that is exactly what we want! We want a useful, clear Q/A knowledge base. Of course, we value every single user contributing, and we shouldn't remove all personal style ...


20

Every single rejected edit only changes "How to...?" to "How do/can I...?" in titles. Yes, you should stop suggesting these particular edits. They are making the posts worse. If you absolutely must make it more grammatical, remove the question mark instead and fix other issues while you're there. "How to _____" is a far better ...


17

The example you mention isn't really a typo. A typo is a spelling mistake, caused by swicthing lteters aorund, omtting ltters, or innsreting addiitional onnes. The bash error above is a syntax error more than anything else. In other languages, it's more a point of style and readability, and is neither a typo nor a syntax error. It might be good to begin ...


17

meh :) One of the most important points of this website is that there must be the least amount of friction when answering, because answering is the site's livelihood. You don't need to write perfect English. You don't need to spell definitely correctly every time. Literally every single person on the internet (with exceptions) can propose edits to your ...


16

The edit makes a noticeable improvement to the post in the form of a spelling correction to the title, had the post been otherwise perfect they might have (and I would have) accepted the edit. This post however had many issues remaining Strange use of commas, " , " with a space on both sides "Thank you for any help." :D Good day. That I could find without ...


13

'Bountied' is used as an adjective here; you should think of the tabs as the following list, but with the word 'questions' omitted: Newest questions Active questions Bountied questions Unanswered questions More tabs (OK, that's the odd one out) You won't find this usage in most dictionaries but English is known for constructions like this; this is status-...


10

Thanks for bringing this up. I've fixed the typo and it will be live in the next release (meta: ver > 2015.3.31.3224, q&a: ver > 2015.3.31.2427).


10

Stack Exchange doesn't provide spell checking at all. It is your browser doing that, and it does work for question titles too on Chrome: On Firefox though it can be an issue, although out of the control of the Stack Exchange developers. As one user commented: As I know Firefox does spellchecking only for multiline edit boxes. Which is the issue you ...


10

I agree improving grammar and spelling would be beneficial, but it's very hard to automate. Consider the following situations: A question on English Language Learners about the correct spelling of a word. The AI would correct the wrong spelling, making the question useless. Some parts of the question may be in another language, especially on some of the ...


9

Please don't do this. We have pretty high expectations regarding the content of good questions: they should clearly state the question, provide evidence of what the OP has tried so far, include just the right amount of code, have a single objectively correct answer (except for sometimes), not be hypothetical, and so on. New and even not-so-new users often ...


9

Clearly it's intentional, status-bydesign. "teh twitters" wouldn't even be correct as "the twitter", as "twitter" itself should be spelled "Twitter" since it's a registered trademark. Feel free to read it like this: Not on Twitter? No problem. Just add #SOReadyToHelp to your "About Me" on your profile page. Just as you would read "gimmeh-teh-codez" ...


9

It does have some kind of spelling correction. Searching for 'spellings' and sorting on newest gives your question as one of the top results, even though it does not contain the word 'spellings': This is the result of using so-called stemmers in Elasticsearch, the repository powering the Stack Exchange search. If you frequently misspell words, it's better ...


8

I'm going to agree with Jeff here. Perhaps a little explanation would show why allowing trivial edits is a bad idea. Currently, approved edits are rewarded with rep. Allowing 1-character edits will result in every spelling mistake being fixed separately, since you earn more rep that way. This will fill up the review queue and give undue privileges to people ...


8

This seriously needs to be automated. I know that there are ways to get out of these things, but these should be removed on post. :) has 190,000 results. Are you kidding me? I'll put together a list of things that should be cleaned. :) - 194,431 :-) - 39,636 ;) - 38,482 wanna - 18,141 ;-) - 16,210 thx - 11,892 gonna - 11,315 pls - 9,521 plz - 8,850 ur - 7,...


8

Look closely at any email with the old design. :) <3


8

Nice catch! Working on a fix right now. Thank you!


7

When you vote to close on such things it's normally closed as Too Localized, or, you don't think that it will help future users or cause the OP to learn more about the language. So, if you can (reasonably) imagine people thinking oh, I didn't know that detail about bash syntax then it's not too localized, but if it's always oh, it's just a spelling error ...


7

But then everything would look like this: I have some Python code to intact with a MySQL database, but I don't think it's Pythonic. The creator of Python, Guido, says that running code from a JS bookmarklet isn't good, but I disagree. I am also using Delphi. If I run this from a cronjob, how can I decompile my code? Befunge isn't an esolang anymore! Is ...


7

Fixed. Cue someone posting a "bug" about a different context in which that cap made sense... Oh - that change applies to all previously-closed questions.


7

Fixed in the next build. Thanks for ccoreccting us. Really wanted to status-ccompleted this...


7

Yeah, looks like this bit wasn't kept consistent with the rest of the site (it lives in its own view, as it is something that just mimics the look of a post and isn't supposed to work like one otherwise). With you in the next build.


Only top voted, non community-wiki answers of a minimum length are eligible