49

Regarding the question "will it break too many posts?", what Adam Davis says is correct. So when we switch (and at this point I'm fairly certain that it's "when", not "if"), the most important thing to know is that this won't suddenly change old posts. Here are some thoughts I currently have about the switch. I'm just thinking aloud; we haven't decided ...


35

6 years later: Stack Exchange is switching to CommonMark! Yay Original answer: I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard: I hope to eventually switch Stack Exchange over to this Markdown ...


32

I completely support banning ImageShack images in new posts. The fact that it's an unreliable image host would be reason enough in itself, but the replacement of images by ads just adds insult to injury. If implemented in the same way as most content bans on SE, this would presumably mean that trying to post a question or an answer containing an image ...


23

(This was posted in response to the first version of the question and then edited after the question was revised once. It hasn't been updated for further revisions.) There are three aspects to this (original) proposal: accepted-answer stickiness accepted-answer reputation accepted-answer labeling (OP clarified in a comment that the intention is for the ...


21

I noticed two new thoughtful answers to this question and, by coincidence, the community team discussed this very issue yesterday. I'm not writing on behalf of the team, but rather summarizing my thoughts after our discussion. Initially the idea was that a beta site would graduate (or be folded) after 90 days or so. In that scenario, appointing moderators ...


21

Indeed. The current place isn't intuitive and actually causes confusion, also by regular users (like it did with me just now). The start bounty should be shown in the button bar under a question, and it should always be visible, so it is consistent with all the other buttons: You can debate about its position. I just put it at the end for now. Maybe ...


21

will it break too many posts? Posts are rendered into HTML upon submission, and edit submission, the HTML is then saved in the database and served. Thus, a change to CommonMark will not result in post breakage except in the case where one is editing an older post with a conflicting syntax. The preview, however, will show the discrepancy, and they should ...


21

I'm beginning to think that you all have been poking around in my brain. As I've mentioned before, this problem has been in front of me lately and I've yet to come up with solution that has been accepted internally.1, 2 FWIW, I've suggested a variety of things, internally, to "unpin" accepted answers from the top spot, including limiting it to those that ...


19

There is definitely something strange going on. First, the time stamps on the edits are different: Revision 2 was approved at 13:24:57Z Revision 3 was approved at 13:24:58Z Those timestamps match the +2 entries in your profile. But when you look at the reviewer timestamps is when things get screwy: talonmies approved the edit at 13:21:30Z us2012 ...


19

We have started showing a warning message when images are uploaded to Imageshack. We are planning on doing more such as sweeping through and uploading all images to our hosted image server over time. Old images in historical posts that no longer exist are very difficult to track down, so we may need your help finding them and re-uploading them as they are ...


17

This is a five year old question, with 5 year old answers. At the time those answers made good sense. I wonder if they still do. With the changes and clarifications in the difference between success and graduation beta sites are living longer then they did 5 years ago. They are successful with well defined scope but just have not graduated. Voting is an ...


16

I, too, have noticed this issue on some sites. Moderators are chosen early in beta and, two or three years down the line, the team is unchanged, most of the community wasn't even around then, and some of the people whose straw-poll votes were factored into SE's decisions are long gone. Sometimes everybody's happy and the team should just keep doing what ...


16

Marking this specific request as status-deferred because we are not going to be making any more changes to the current editor. The good news is that this behavior is functioning as you are looking for in the new Stacks Editor, which is currently live on Stack Overflow for Teams, and which we have plans for eventual release on the public SE network. It is ...


14

There's a few ways that we can go about this, so we're going to have to play with some ideas to see what works best. The first way is a wall that they have to acknowledge in order to comment. E.g.: If you're responding to someone asking for clarification of your question, there's a very good chance that you want to be editing your question to include ...


14

For registered users, we're working on storing cookie preferences against your account so that your preferences are saved across our different domains. That will save you from having to set preferences for each domain.


13

Moderator tools of some kind are on the roadmap, and review queue things will be in the "sooner rather than later" category when we get there.


13

Nope. It isn't (well, shouldn't be) possible to gain more than 2 points for making a single edit. As Mat pointed out in the comments, the edit revisions history does look weird. This could be a bug, but I'm not exactly sure what's causing this.


12

Yep, our capitalization is all over the place. The tricky part is our localization strings for other communities are based on the original English text. This means that if we change "share" to "Share", our translated communities (Russian, Japanese, Spanish, etc.) each have to re-translate. We'll be making things more consistent as we refactor and modify ...


11

This has come up before, more than once, as have variants on the same theme. And I find myself thinking about it now after encountering yet another comment to the effect of "This should be the accepted answer". The comment was left by a user who had found an answer to be "better" than the one the OP accepted. Such comments, of course, don'...


10

Something like this is planned, it's just going to be difficult to implement at first. The ideal scenario is: Stack Overflow gets its own meta site, for Stack Overflow specific issues, just like every other child meta in the network. Stack Exchange opens a central meta site, which propagates questions with certain tags or velocity through something similar ...


10

Well, this sucks! Unfortunately we're not in a position to fix it, yet. What I can do is a very close approximation which I've just done and you'll begin to see as cache falls out over the next 10 minutes. Since the last import of an SE 1.0 site (we're sure this time, we deleted the servers, always double tap!) we needed to run a network-wide aggregation ...


9

I think it should be a checkbox, like in this mockup I made: This way, people who ignore tags because they have spoilers can avoid them in the queues, while people who ignore tags because they are annoyed by seeing questions they can't answer can still review everything without having to change their settings. This feature could actually increase ...


9

Not to worry. We are working on a super secret project to do just that. To put it in trendy terms, we're hoping to "hyper target" ads in the future. Unfortunately the ETA is "this is way harder than we initially thought so some point in the future".


9

I've also wanted this for a long time and actually just spoke to our design team this morning. We're going to make this change because it is a big waste of space for single-line comments.


8

After a ton of digging through the database trying to identify how many users hit this bug and the cause of it, we've determined that it's a race condition. The fix will be going in this week, once we've identified all the places where we're hitting this same issue (Shog's got a list). The fix will include a redis lock (which we already use elsewhere), and ...


8

I've thought about this for a while - and perhaps its worth reframing the question in terms of what sort of information we need, and how this information is best stored, and shared in a way that meets both privacy, and the operational requirements of both mods and the folks who run the site. TLDR: Its worth considering alternatives to exposing IPs to mods. ...


7

It could be an issue of not having "Helvetica Neue" specifically. We can look at expanding our font definitions to include something more like this: font-family: "HelveticaNeue-Regular", "Helvetica Neue Regular", "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif; This font-stack solution was proposed by Chris Coyier a few years ago and its ...


7

Maybe Stack Exchange could gather up a list of all old ImageShack images urls, offer to pay the ransom for them, move them into imgur, and update the references server-side. It is after all SE's fault that the built-in image uploader wasn't around until two years after launch...


7

Just a wild suggestion regarding the accept button: The accept button 'claims' to show the 'best' answer, well, that is how people who are not used to SE think it does. And that claim is wrong, it is merely the opinion of OP, who doesn't have to be an expert on the subject and is not the person who you expect to be able to pick the best answer. What if the ...


6

This isn't entirely correct, you can access it via keyboard, just that you have to use Shift-Tab since the elements are at the end of the page, HTML-wise. However, it would be useful if the tabindexes of the menu were rearranged. Currently, Shift-Tabing takes you to the end of the multicollider instead of the beginning.


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