27

Hair, You can get a temporary workaround by adding an invisible comment using <!-- --> at the beginning of your answer. Then you can add 'Hair' after it. I agree though that this needs to be fixed.


27

I know all has been said. I know I cannot upvote twice. Maybe a picture helps. Below, @ajax333221 was removed, and also that original author is not listed as this a community wiki post: That bothers me a lot.


15

You can put the URL inside backticks, like this: `http://www.example.com/index.php` This results in a valid URL without a generated hyperlink: http://www.example.com/index.php Code for that page


13

I don't really like vote-locking (especially on metas), but given that we have it, it should behave consistently for all edits. Community♦ edits just aren't that special. If somebody has exploited it to conduct "targeted unvoting", deal with that user. I'm pretty sure that the way vote changes work for the vast majority of us is: we vote at some point and ...


13

We have performed a Hair removal removal. Having said that: http://www.youtube.com/watch?v=ozQ8qLMKW_s#t=1m28s Hair is no longer trimmed, cut, stripped, or buzzed.


12

I think there's no need at all to remove "hay" from posts, as people use more "hey" than "hay", see this (22.7k vs. 300, emphasis on your very uncommon). It's important to note that "hay" is a very common leading word in a sentence. This adds another supporting reason not to remove "hay". See the example above. Dear me, they stripped the whole sentence. ...


10

Hair, and particularly facial hair, is a sort of defense. It's harder to take a bite of someone's throat, or scratch their throat if it's covered in hair. So in a jungle setting there can be predators that prey on humans, but if they have longer facial hair they will be more likely to survive. Granted this doesn't depend on how fast it is, so an additional ...


9

the icy ball form of precipitation - induce the same bug. The regex is attempting to defeat an initial "hai" (as in o hai), but is over-zealous. The regex being: ^ # begins at start of body \s* # possible spaces ( hii?(?![a-z])| # any of these greeting words hello| h(e|a)y(?![a-z])| dear| greetings| hai| guys| howdy| h(i|e)...


8

Votes that are reversed are not completely erased from the system. They are stored in the database permanently, like a post, and simply marked as "deleted" when they are retracted. That said, there are no built-in tools to track serial vote retractions of any kind. Staff can manually write SQL queries to track cases (essentially looking at the ...


8

Considering the regex used seems to be: ^ # begins at start of body \s* # possible spaces ( hii?(?![a-z])| # any of these greeting words hello| h(e|a)y(?![a-z])| dear| greetings| hai| guys| howdy| h(i|e)ya| hola ) .*? # followed by anything, up to... ( [.,;!-]+ # one or more bits of punctuation \s* ...


7

It's a review audit: Further reading: What are review tests (audits) and how do they work? Who is the Community user? Stop using real accounts in suggested edit audits (explains why Community takes responsibillity for the edit, once the audit is over)


7

There are a few potential issues with the old links floating around: Badly written code might not understand them and do something sub-optimal. A redirect through HTTP potentially loses referral data, making it harder to tell how much traffic (say) Meta Stack Exchange is sending to Software Engineering. A redirect through HTTP potentially leaks sensitive ...


6

Special Casing Sucks. Any special case is literally more maintenance, involves specific situations, and generally makes things less maintainable. So more or less we're trying to change what's essentially standard behavior, consistent across any user, regular or otherwise, so that we can audit edits possibly made by one or more users who for whatever ...


6

From this excellent answer to a very similar question: You can put the URL escape a / with a \, like this: http:\//www.example.com/index.php This results in a valid URL without a generated hyperlink: http://www.example.com/index.php Code for that page Note that the live preview will show the \, but the actual rendering won't.


4

You should leave it alone. The new duplicate banner only applies to questions which were closed after the date/time the feature was implemented. Old questions are still reliant on the banner and it should remain a part of the post until such time that it gets reopened. Removing the banner itself does not reopen the question - it just leaves it in a confusing ...


4

A question title should give a good preliminary sense of what the question is about. If starting with one of the tags has that effect, I'm in favor. I hate having to read a wall of question of go digging for the tags just to see what on earth the question is about. I am opposed.


4

You seem already to have provided evidence that "Ha, " is being removed. I don't know what came next in your answer but I would always prefer to see an answer begin with: <start of answer meat> rather than: Ha, I just ran into this myself! <start of answer meat> To me "Ha, " is definitely chit chat, and all of "Ha, I just ran into this ...


3

I'm not actually sure those things would typically be broken - we'd simply just see a redirect to HTTPS. If its actually broken - its a semi trivial edit. If its not broken, its a massive task, or many edits, that doesn't fix anything. It's not a good use of staff time IMO. If you happen to come across a http link in your normal course of things, try it. ...


3

Usually, this is possible, but it might be that the editor automatically strips one or two characters from the question body and interprets this as a change. If you link to the post we can be sure. Most of the times, you can improve something else in the post, or perhaps substitute a word with a synonym and indicate you did this only because of the error ...


3

If the system auto-notifies the post owner, great, but removing @postowner from comments is another matter. This is messing with the contextual clues we get while reading through comments, and the resulting inconsistencies are subtle and manifold. Here are examples of just two issues that—even without any of the others—should be sufficient to ...


3

We don't want to make the system any more confusing than it has to be. We should be simplifying it at this point, not adding additional complexity. That said, I think this could get us a net gain in quality if paired with some additional efforts on that front. Getting people to write good, descriptive and clear titles is hard. Yet, the quality and clarity ...


2

I think that having this implemented would make a great start on improving the professional appearance of questions on every Stack Exchange site. The Tour of every site already says that there should be no chit chat, and I think unnecessary thanks are an example of chit chat. A Meta Stack Overflow Q&A that resonates with me is No Thanks, Damn It!


1

I don't see a reason to add extra complexity to the system. If you really need that list of edits, you can use SEDE: select postid as [Post Link], comment, approvaldate from suggestededits where owneruserid is null and rejectiondate is null This code will return all the approved suggested edits made by anonymous users.


1

Fixed it by adding an empty comment block before your code. The problem is that we have a filter set in place that automatically removes "Hello", "Thanks", etc. lines from the post when you save. As others have said in the comments though, you should add an explanation of the code.


1

StackExchange sites, and especially SO, already have quite a few rules and unspoken practices that are hard enough for new users to learn. Lets not impose another rule, even if its just an automatic edit of the title the OP chooses. While it may not be necessary to include tag terms in question titles, neither is it currently prohibited. People should be ...


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