# Tag Info

6

Another aspect related to this: Sometimes even high reputation users might be among problematic users of the site. (For example, I could imagine a typical FGITW user having a rather large reputation, while some part of their activity might be actually detrimental to the site.) I have also seen a situation when some user used email of this type as an ...

3

This solves it $$\rho_h(f)=R_h(f)/R_0(f)$$ instead of $$\rho_h(f)=R_h(f)/R_0(f)$$ This is surprising since its not a problem on Physics SE. Hope the Mathematica code checker can be updated to accommodate this, imho, common way of writing.

2

Currently the Privileges API (/2.2/privileges?site=meta) is returning the description as see votes, expandable usercard. Updating the API, can solve this issue. Screenshot for reference:

3

This got fixed this afternoon. Thanks for pointing it out. Apologies for the delay, holiday code freezes got in our way. Hey, that rhymed!

4

This got fixed this afternoon. Thanks for pointing it out! In our effort to improve our frontend so things like this are less likely to slip through the cracks, something like this slipped through the cracks. THE IRONY!

3

This issue is fixed (the proper way this time). Migration notices on all sites should now be showing up properly.

3

This was an issue that only happened in FF. It is now fixed.

-1

I read somewhere (but now can't find it again) that you have to edit your question to stop the duplicate suggestion from appearing again. Maybe the system assumes that your question is currently a duplicate and so when you edit, you are editing in the reason that it is not a duplicate. Another thing I think I read was that maybe the system is making sure ...

19

I think this is an excellent idea. To be precise: to replace auto-generated mails with one or more of the suggestions made in the request. Similar to the recently suggested Replace the 100k and 250k swag ... it would really not cost much money to improve status quo. It would only require some people at SE Inc. to sit down and be creative. There are so ...

4

Wiki pages have been updated. Thanks.

3

The contents of the community bulletin are cached and only updated every 24 hours, so it's not unusual to have to wait up to 24 hours for the daily script to update the bulletin's contents (remove un-featured posts, add new featured posts). If you've waited 24 hours and the bulletin still hasn't refreshed, you should ping an employee.

1

I don't see an issue with the message text. You are being told to award the bounty to the best answer as soon as possible. If no answers currently exist, then "as soon as possible" will be after an answer is posted.

5

I just diagnosed it and it's purely an issue with rendering background images in Safari and has nothing to do with Javascript. The slowdown occurs when using multiple images in background-image with different background-attachment attributes. I made a bare-bones html file that shows the same slowdown in Safari but not Firefox and Chrome (and included the ...

2

That +15 is caused by three upvotes (+30 reputation) minus 15 because of the unaccept. Since all events happened on the same post, they're lumped together. I do see the unaccept in your reputation history:

14

We had one server going a bit crazy with memory (from a competing process) - I've gotten a dump, cycled the issue (to restore production), and will dig into what's causing it first thing tomorrow. Thanks for the report!

3

This has now been fixed. The extra space has been removed.

4

This is now fixed and deployed. I guess we are good now until we hit 10 million, right?

3

This has been fixed. All links within post notices should now be shown once more.

5

This feature has been implemented. When you add a bounty to a question, the button for awarding the bounty to an answer is now grayed out for 24 hours, with an appropriate tooltip message and cursor. If anyone wants to see how it looks, I encourage you to add a bounty to this question. As others can't try, since I just did, I'll post a picture to comfort ...

10

This was caused by a race condition. Two users happened to cast a sixth spam flag on the post at exactly the same time, which caused the system to process all the resulting actions twice for the post because neither process knew anything about the other process already running.

1

Fixed as of December 12, 2019.

34

This should now be fixed; if it doesn't show immediately: the cache is sentimental 😢.

3

Sorry to hear about that. Unfortunately, the Android app is no longer supported. Please use the responsive web on your mobile device.

5

We are not providing any further support for the mobile apps. There will not be any more builds made for either the Android or the iOS app (even for breaking bugs). We encourage all mobile users to use the responsive website. We hope to continue to incrementally improve the user experience for mobile users.

1

The reputation update in the top bar is 'powered' by the same websocket on all pages. No matter where you are, you will always receive the same updates. It might take a few seconds for the +2 to register, so if you navigate away from the page too soon, you'll miss it. But AFAIK this has always been the case and is definitely status-bydesign.

6

There isn't really an "implementation" here - all that was done was the Community user's display name and bio was manually edited by someone on those sites. It was simply never brought up on the other two sites, so it was never done. That's not really a bug, just a lack of people caring in those places. I've changed it on the Russian Language site to match ...

4

You're only ranked in the reputation league database once you get more than 200 rep on a site and that only happened today for this user on Politics. Wait 24 hours for the nightly job that calculates ranks and the rank should appear.

4

There's a check that runs when you submit a review which verifies that you're even allowed to review things in that queue - this check rules out a lot of weird / bad stuff, like folks reviewing after being banned from review, after being suspended, without having earned the privilege of reviewing, etc. It's also the check that grays out the queue on the top-...

4

The cause here is a sanity-check which attempts to verify that a given review action is actually valid for that review: for a LQ answer, that means a Delete action is only valid if you have delete privileges, the answer scores <=0, and you still have delete votes remaining for the day; a RecommendDelete action is only valid if one or more of the above are ...

17

Funny story... That answer and its question were posted by the same person, using two different accounts. When this was discovered, moderators deleted the sockpuppet account and the owner of the other account requested that one be deleted as well. So in a sense, the system was doing the right thing here - not pinning a self-accepted answer - but, it was ...

-1

You're the owner of the tag wiki because you created the tag wiki excerpt. As tag wiki and excerpt edits have to be submitted at the same time, once you submitted your excerpt edit without entering anything into the wiki box, it also submitted the blank wiki, so thus you own it. This behavior is harder to find because it's inconsistent with what happens ...

1

From some snooping around, this bug only happens if the first editor of the tag wiki submitted a binding edit to make the wiki (or excerpt), not a suggested edit. As suggested edits are based on diffs, and you can't by definition have a diff if there is no prior revision, when a user without enough privileges submits a tag wiki or excerpt proposal, the ...

5

It turns out that there are two different thresholds one for main sites (6 months) and another for metas including MSE (12 months). We run a script once per month which means in some cases the period might happen to be almost 7 and 13 months respectively. The fact that the edits were rolled back is entirely incidental.

1

This is something I can fix by doctering with the CSS of this page using the FF developer tools: Original settings: Altered settings:(Increased bottom padding from 0.3 to 0.4)

2

The fix is quite simple: When I change the height property of .posts-navigation in the CSS from 10 to 15, as in below screenshot The bottom of the arrow alligns with the bottom of the word "Previous", the text is however now slightly smaller in height then the arrow is.

4

It's not a bug. Mathoverflow is a bit different from other sites. One of the consequenses is that they don't have the hot network questions: They prefer not having the hot questions list, and the design is adapted from an older design created while they were still an SE 1.0 site as far as I know.

35

Ever look at a line of CSS and think "that seems legit"? I should really stop doing that. The fix is live in production. Thanks for the report!

7

We just pushed a build that fixes this...again. Thanks for the report.

4

This has been fixed. There had been one part of the code that was getting the duplicate selections, and another where it was only showing the duplicate selections if they had an answer. So if there was only one suggestion and it didn't have an answer, you would see the notice but would not be given anything to choose from. Has been fixed to show all ...

5

Well, yeah that was broken. It turns out that the cookie we used to track whether you wanted to use the mobile UI expired on Jan 1st, 2020...so that's why it stopped working: This was just fixed to extend the expiration until Jan 1st, 2030, so on Jan 2nd, 2030 it will stop working again.

2

We pushed a fix for this typo in the latest build. Thanks for the report.

5

A fix for this is rolling out with build rev 2020.1.8.35735. The bug here was a regression from when we switched default URLs from http to https. The server-side code that detects question URLs had to consider both cases (http and https), but was relying on a default parameter value for the http case instead of explicitly probing for it (site.Url() instead ...

4

This is now fixed. Empty post notices should not happen anymore. Update the regression has been fixed (actually, the original fix did not really fix the issue, the real fix is now in place)

3

I couldn't repro this, so it looks like it's been fixed? For testing, you can trigger the indicator from your browser JavaScript console by running: // off StackExchange.topbar.handleRealtimeMessage('{"Inbox":{"UnreadInboxCount":0}}'); // on StackExchange.topbar.handleRealtimeMessage('{"Inbox":{"UnreadInboxCount":1}}');

13

Yeah, good catch - thanks for the report, Glorfindel! This fortunately hasn't been abused much - I found 102 votes across the network that should've been removed. I've removed them. That includes the votes on your Chess answer. After the next build, these will automatically be removed along with the pending flags when a user is deleted. Reputation will be ...

6

A fix for this is rolling out in the next build (2020.1.7.35722).

2

Thanks for reporting. The 500 error is fixed now.

4

I checked on the traducir.win, the tool we use to translate strings, and found that there are two almost similar strings that say If you need anything else, please visit our contact form and select Other for additional help. Only one of them was translated. I copied the translation and submitted it for Japanese and Portuguese languages. The translation ...

2

Thank you for noticing the error. I edited the article. Now the phrase formatted as a quote, not as a code.

2

Looks like you saw a brief bug in the new Post Notices rollout - resolved since by the lovely Yaakov :)

Top 50 recent answers are included