# Reputation and badges are no longer visible next to the users' names

Right now it seems that a bug is affecting MO: reputation and badges are no longer displayed next to the users' names.

This happens both on the front page:

as well as on pages of individual questions:

Furthermore, the reputation pop-up is also not displayed when I hover the mouse cursor above a user's name.

This seems to be a MO-only bug, since it doesn't manifest itself on the other SE sites of which I am a user. This also doesn't manifest itself on Meta.

This is not a mistake. It’s an intentional change to the site that the board and moderators agreed on. We coordinated poorly and did not have a formal announcement ready when the change rolled out; apologies to those who are confused. However, given that the whole point is to minimize attention to points as a feature of the site, drawing a lot of attention to the change would have been self-defeating.

• The fact that the bar initially loads then disappears draws quite a bit more attention to it than a meta post would. Jan 11 at 2:01
• So it seems like the bug is that the reputation info is breifly appearing when pages are loaded, whereas it should no longer appear at all. Jan 11 at 2:14
• @gparyani I take your point, but I am not sure that it can be avoided.
– Ben Webster Mod
Jan 11 at 2:45
• @Dan: Yes, there are a couple of bugs we could not anticipate, due to the integration of the script into the SE system. We hope they will be resolved shortly.
– Asaf Karagila Mod
Jan 11 at 8:07
• I have no preference regarding showing the reputation or not. I am a bit surprised, though, that this decision has been taken in secrecy by a small group of users and does not follow from some large consultation of the MO userbase. While it may turn out to be a good choice, it is definitely a loss for democracy and transparency. (My bet: the change will have no consequence on the behaviour of users, things at large will stay almost the same.) Jan 11 at 8:39
• Expect a dozen or more "bug" reports incoming on various places on the network I guess. I personally think that it is a very poor choice to fall so out of line with the rest of the appearence of the SE network, even though you are able to. Jan 11 at 11:21
• @Luuklag: We also don't display the HNQ on the site and instead have the recent badges awarded. I don't hear any complaints about that.
– Asaf Karagila Mod
Jan 11 at 11:58
• @AsafKaragila, well that's mainly because the HNQ isn't all that visible for most people, and those can be turned off by default already under a users preferences. Jan 11 at 12:00
• @AsafKaragila: Luuklag's answer is correct: I had deactivated HNQ in my profile a looong time ago, so that I wasn't even aware that it existed. Jan 11 at 12:02
• Alex: MathOverflow exists independently on SE. I don't see the importance of us keeping the same appearance as the rest of the network. There's a reason why individual sites have individual themes, individual looks. Nobody complained when we had the citation script running and the rest of the network didn't. This is a change, I get it. People don't like change. I too get riled up when SE releases a new GUI feature. But you get used to it, and then the old one seems weird. We will fix the bug, you can opt-in and see reputation points again, and we'll all move on.
– Asaf Karagila Mod
Jan 11 at 12:04
• @AsafKaragila: Agreed. I'm neither complaining, nor planning to make a fuss about this minor issue - we are grown-ups. I would only like the next such significant change to be discussed with the community in advance, though. Change can be good or bad and can rarely gather a consensus, but it is ethical to be discussed in the open before committing to it. Jan 11 at 12:50
• I agree with Alex M. Some changes are major and others are minor. Minor changes don't need a lot of public discussion. This change strikes me as a major change; evidently the moderators did not think so. That's fine; moderators have to make judgment calls. However, if users give feedback saying that they regarded a certain change as major, then I don't think the moderators should just brush off that feedback by saying, "This is a change, I get it. People don't like change." The point is that good leaders try to stay in tune with public opinion. Too much divergence is a recipe for trouble. Jan 13 at 18:13
• In particular, the question isn't whether the change is good or bad, but whether it's the sort of change that users think should be publicly discussed ahead of time. So I think the appropriate response should be something like, "We didn't think that this was a major or controversial change. We hear that some of you think it should have been discussed publicly ahead of time. We'll take that feedback into account the next time we contemplate making a change." Jan 13 at 18:15
• I've posted an announcement here: meta.mathoverflow.net/questions/5218/… I do apologize about the slightly botched roll-out. A fair amount of it is my fault for reasons too dumb to recount. I hear the points above; obviously a more significant change the site, especially one that wasn't easy to opt out of, would require quite a bit more discussion. Certainly, any future experiments will be more carefully synchronized with an announcement of what we are doing.
– Ben Webster Mod
Jan 16 at 1:57

For users with an ad-blocker who want the old behaviour back: it seems adding https://cdn.sstatic.net/Js/webpack-chunks/8844.6aa9de60ac9aca9f14f4.en.js to your block list is sufficient to circumvent it. (For now; the filename might change with future deployments.)

(Context: I need that information for a userscript to help with blatantly off-topic questions to work properly.)

• There is an opt-in feature, by the way, but it stopped working when we integrated the script into the system for some reason. We hope to resolve this quickly. So there is no need to use ad-blockers for this.
– Asaf Karagila Mod
Jan 11 at 11:26
• No, it's in the achievement menu. You can see it already, it's just not working for some unclear reason.
– Asaf Karagila Mod
Jan 11 at 11:33
• @AsafKaragila There isn't anything there for me: i.stack.imgur.com/kCCeZ.png Jan 11 at 11:56
• @Luuklag: The script is not active on meta. You're on meta. (As I said, that feature doesn't work at the moment anyway, and once it's resolved we'll make a more orderly announcement with screenshots and explanations.)
– Asaf Karagila Mod
Jan 11 at 11:57
• @AsafKaragila it doesn't show on the main site either, at least for me. But I'll be patient :) Jan 11 at 11:58
• @Luuklag I see there "privileges", "badges", "show rep": i.stack.imgur.com/Jp26e.png Jan 11 at 15:36
• @MartinSleziak I still don't. It's either a caching issue, or perhaps tied to reputation? Jan 11 at 15:38
• For me it shows up on the main site, and it kind of works, in that clicking it makes reputation appear in all user cards on the current page, but the setting is not permanent (going to another page, or even just reloading the current one, makes reputation disappear again). That’s not very useful: I can as well click on the relevant user links to see their reputation with much the same effort. Not to mention discoverability (this is just about the last place where I’d expect this setting to reside, it’s completely counterintuitive). Jan 11 at 15:39
• @EmilJeřábek ah, of course, I'm a victim of my own workaround. After removing the ad block rule, I see it too, but it's broken, just as you describe. Jan 11 at 15:45
• (As I keep saying... some unexpected bugs came up when we integrated the script into the SE code.)
– Asaf Karagila Mod
Jan 11 at 16:09
• @Glorfindel: Hoisted with your own petard, I see. :)
– Asaf Karagila Mod
Jan 11 at 16:10
• @AsafKaragila looks like the opt-in switch is simply not remembered? That's going to be difficult with just JavaScript, it can store something in local storage but that only affects a single page. (But again, I'll be patient :)) Jan 11 at 16:14
• @Glorfindel: Yes. It's not true that local storage only affects a single page. In the tests we had using a userscript, it worked fine throughout the site. I am guessing that something in the SE code structure throws a wrench into the design of the script. And it makes sense, since userscripts are overlays, and this is more of a "built-in patch". So, something causes a reset of the variable almost instantly, which means that the setting is not cached into the local storage correctly.
– Asaf Karagila Mod
Jan 11 at 16:16
• @AsafKaragila, that is one of those "peace in/for our time" phrases: actually it's "hoist with his own petard". Jan 12 at 22:06
• @AsafKaragila Whatever the issue was, it seems to have been resolved now (at least for me): hitting "show rep" correctly makes the setting stay that way after changing pages. Jan 12 at 23:32