Hot answers tagged

23

This is what I wrote (with slight edits) at the MO chatroom: I guess I should mention that I am often in contact with my fellow moderators, especially when a sticky situation arises that I'm not sure how to handle, I'll want to consult them or get consensus. That kind of behind-the-scenes activity is of course invisible to general users. I think ...


15

I asked the SE folks and they promptly fixed the problem, noting that it was due to a simple oversight when rolling out the feature to the rest of the network.


13

The logic behind the Strunk & White (and the Copy Editor) badge has changed slightly in 2011 (thus after the split between MO and the SE network). See this answer on MSO for details. The changed logic means that fewer edits count towards these badges, which is why the thresholds were lowered. By the old logic, you had over 100 edits that counted, but by ...


13

Nope, everything is fine, no need for new elections.


12

Based on this request, we've updated the link colors using a brighter blue that is more distinguishable from the surrounding text, and tested with a colorblindness simulator (though it's not an exact science and if you are still having issues, let us know). We didn't make the main question link color in the question list the same blue because now that the ...


12

The "teapot" error is one of the various responses we return if something looks very suspicious at the http/form level - most likely because of an XSRF check failure. On mathoverflow, this is usually from bots that spend their entire life trying to edit one post (seriously, it is always the same post - I have no idea why, there's nothing particularly unusual ...


11

This is due to two specific changes from the 1.0 engine to the 2.0 engine. The first is that the minimum length of display names on the SE 2.0 engine is now three characters, not two. Names shorter than two characters were normalized in the pattern of user{user_id}. This is something they can change by editing their profile. The second is that the engine ...


11

If an event is less than one year old from this calendar year (thanks quid!), the year is not written. I recognize that this is not a convention that is immediately unambiguous to new users. Perhaps we can add a feature request to make everything ISO 8601-compliant.


10

Looks like all of the links in your profile were marked with a "nofollow" attribute, which in turn told our engine to stop rendering them as links. This is probably a side-effect of your other site profiles having lower reputation and MathOverflow joining the SE network. ("nofollow"ing links from new-ish accounts is in place to prevent the less scrupulous ...


10

This had to do with the citation helper script - mostly with how I implemented the integration with the editor. The fix is being deployed right now.


10

I thought the community deserved a little update on the internal moderator discussions on this point. My answer below just speaks for me, but I did run it by the other moderators, and got no objections. It's my attempt to lay out our thinking, so that people have a chance to disagree. Our basic calculation is that moderator elections have the potential to ...


9

StackExchange.com consumes our public API, which is guaranteed to return a launch date for every site, but didn't for MO. Sites that were not launched through Area 51 need to have this value explicitly set, which hadn't happened for MO yet. It's set now. Thanks!


9

If you click on the number "0.0x%", the links gets you to reputation league for MathOverflow. (The link given in the question is actually list of the registered users and not the reputation league.) As far as I know, only users from reputation leagues count for the purpose of these statistics. (That means that cut-off is at 200 reputation points. Notice the ...


8

The analytics key had not been entered for stackexchange.com. The next build will include this and report the correct stats. It should be live within the next few hours.


8

A couple I have noticed: using \\, instead of \, splits the line, using \\; instead of \; splits the line, and using \\! instead of \! splits the line. Added later: There have been some instances where people have used \_ instead of _ but I believe all of these have now been fixed. Edit by R. Andrade: Apparently, there are still instances of this issue ...


8

This had to do with the citation helper script - mostly with how I implemented the integration with the editor. The fix is being deployed right now.


8

I have to admit that I initially got aware of the since September 29th 2016 missing trackbacks for MO, because we at PhysicsOverflow faced the same issue. Now I am happy to report that our system developer resolved the issue after learning from communications with the ArXiv that they changed the protocol for trackbacks from http:// to https://, and now uses ...


8

I've updated the MathOverflow script to use https, and set it to re-run on posts modified since September 29. Thanks for the notification of the problem, and the solution from @Dilaton.


7

Yep, there sure is...however it's granted when you create the accounts as we go, which isn't really import friendly. Luckily we already have a way to fix these up, I've just run it to grant it to everyone currently mapped up and we'll run it several more times in the coming days as we get users all mapped up to their existing Stack Exchange accounts. If ...


7

No no, there is no link anymore. You go to "review" and then you should see "tools" somewhere on the top part of the page (below the top menu, though).


7

I suspect if we can concoct some regular expressions that catch common sources of LaTeX problems we may be able to get some automatic replacements run on the database. I'm guessing this is our back-ticking habit coming back to haunt us, now that the interaction of markdown and MathJax has changed slightly.


7

Fixed in build rev 2013.7.2.799. From this build on special characters between $ signs won't need to be escaped in comments. However I should note that this breaks some existing comments that escaped special characters: $p^{\*}$ test $(p^{\*})^2$ The above markup in existing comments renders the same as in posts: $p^{\*}$ test $(p^{\*})^2$, and can be ...


7

I have "re-baked" the HTML generated from the existing markdown for the current revision on all posts that exist on MathOverflow. This seems to have cleared up the cases that have been reported thus far. Please let me know if you find any other issues.


7

That answer has what we call community wiki status applied to it. This is a special sort of status, wherein anyone with at least 100 reputation can edit the post it's applied to. If you look at the revisions of the post you can see where it's applied. It's not a bug. The implementation is rather confusing at first glance, we're working on improving that, for ...


7

Fixed the phrasing as suggested, as the score for answers is calculated from non-wiki answers - the wiki status of the question they are on is not relevant. With you in the next build (rev 2013.9.26.1037).


7

This is an artifact of some fail-over testing we did during the weekend. Sorry about the noise, this should be cleared up for everyone by now. For those that don't know, we have redundant data centers, data replicates between them. If something happens in the US East, we can (very quickly) come back up in Oregon, without anyone losing anything they've ...


7

MathJax v2.6 was released on Dec 30, close to the OP. These updates can lead to errors if a browser cache contains a mix of MathJax components with different versions. In that case, clearing the browser cache from all things MathJax (and for some browsers, additionally restarting the browser) should help.


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