Here's the logo as defined by DEK at \magnification 6000 run from plain.tex. Judge for yourself.
Addendum: DEK wrote a brief article for TUGboat with his recommendations for "correcting" the kerning for the logo in different (cm) fonts. He also mentions some (limited) experiences with non-cm fonts.
I could understand such a message if a substantial part of a user's questions were closed as “off-topic“, “too broad” or “unclear what you're asking”, or several got downvoted.
Closing as duplicate might mean that someone with more experience found a question that could apply also in a different case and the unexperienced questioner couldn't realize it. So ...
Update: This was almost certainly my fault.
On December 20, 2013 I moved the TeX (and meta) databases to new homes. I'm not sure how the original problem occurred, but TeX and its meta had a very odd database collation. Of the hundreds of databases, it was only those. We didn't recognize this for several years until we started aggregating data across ...
The unannounced change should be reverted as soon as possible. I would even remove boldface from the current tab name, normally active, because the rule under the tab name is sufficient.
Boldface is a device to be used very sparingly, because it catches attention: with the current setup, tags are more prominent than question titles.
There's a script that looks for "suspicious" voting patterns between users. The details are kept intentionally vague, and normally you shouldn't ever be aware of it...
But it is possible - and in this case very probable - that 63 up-votes cast on your answers by another user were nullified early this morning.
Sadly, as one of the top users on the site, you'...
Honestly the SE sites have generally very good designs and very nice choices in regards to how things appear, but the tag change is really a punch in the eye. The tags now are as black as the text, making them virtually indistinguishable from the text at a first sight.
I'll just say this:
Using bold for everything is like using the highlighter pen for the ...
The line with the bronze badges is getting clipped if it is too long. The HTML code of the website contains the full number "322" which is clipped here to "32". If you look closely to the displayed "2" you see that it gets a little clipped as well.
The CSS settings used to style each site is different from SX site to SX site, so e.g. SO seems to not be ...
This is not a bug, but accurately reflects the reputation gained over a particular period of time. If you look at the Users page you can select the period of time:
So it's entirely possible for a user who gives a lot of bounties to have a negative reputation when calculated over one of these smaller time periods.
I think the main site looks a little bit silly now. In the following screenshot, the things encircled in red need to be bold as well.
The content of the blue circle needs to be super-mega-bold to fit again.
Just reverting the bold tags to normal would be easier and better, though.
Based on \\ corruption, I've created a new query
TeX.SX \\ corruption (based on user ID)
which I hope will help anyone to find their own posts affected by this bug!
P.S. The database is updated every sunday, so the query will return also updated Q&A until the database is refreshed...
We tracked down the bug. The Tex community has a few special classes for text formatting and those happened to conflict with a recent mixin that was added to a global file. The change was unintentional and an update is rolling out soon. Thanks for the catch and your patience.
What changed is that we started using imgur thumbnails by default in chat; so when you link to http://i.stack.imgur.com/iSQFI.png, we display http://i.stack.imgur.com/iSQFIm.png, but link to the original:
<a rel="nofollow" href="//i.stack.imgur.com/DmZBd.png">
<img src="//i.stack.imgur.com/DmZBdm.png" class="user-image" alt="user image">
The blue links point to answers you recently visited, the others are red.
Click one of the other links and go back to the list of answers, that link should then have changed the color to blue.
The color the browsing users sees depend on visits by him, not on visits by the profile owner. Just in the case your view your own profile it's the same.
You do not have enough reputation to add another bounty. You added a 250 rep bounty on December 5th. For you to add another one, you must double the reputation. You do not have 500 reputation to offer such a bounty.
This is the documentation I could find on meta.stackexchange.com about the definition of "unanswered" and when the Community user bumps a question:
Jeff Atwood, July 2011: Just to be 100% clear, our definition of unanswered is "no upvoted answers".
Why does the “Unanswered Questions” tab show questions that have answers: “The Unanswered Questions tab shows ...
Surely you're seeing something we're not. Here's an image of the votes and view count font on my system (Firefox 10.0 on a Mac):
I really don't see how the 4 and the 2 are very similar, and although the font is serifed it doesn't seem very baroque to me (although obviously this is a matter of opinion.)
The Data Explorer infrastructure relies on past data, not real time. In fact, it uses an anonymized data dump of all creative commons questions and answers from the Stack Exchange family of websites.
We can see the last data update in the front page:
Once in a while, the data is updated. There are also backups in the XML format available for download in ...
I believe there's an answer on MSE that addresses the issue. The important bit is:
A colon and %3a are semantically identical in URLs per the RFC.
If you look at an example on Gaming (and read the comments), you'll see that the problem should actually be fixed by the site that serves pages with colons in the URL. This is actually a bug at Gitorious.org....
It is status-bydesign, as per-site metas (or child metas) don't actually have an exclusive profile. :( The only exclusion is Meta.SO, since it covers network-wide meta-related content, and have individual user profiles separate from StackOverflow.
As reference, see Hat not showing on site meta.
A similar question was posted on Meta.SO, which revealed the following:
Ok so those indexing times are correct, this was a different issue. You may have noticed before the holidays that TeX was read-only for the better part of a day while I did some very fun database maintenance. For some reason I can't explain (it predates me working for Stack), TeX and ...
For the purpose of pretty much everything where it matters, a "new user" is anyone who doesn't have the remove new user restrictions privilege.
If you have less than 10 reputation and post an answer to a question 30 days or more after it was asked, your answer is going to end up in /review. We'll dequeue it if your reputation exceeds 100 before the post is ...
This seems status-bydesign. Based on the current time of 2014-09-10 14:31:43Z,
"today" is defined to be the time range 2014-09-09 14:31:44Z to 2014-09-10 14:31:43Z (or the past 24 hours) and is listed in a "just now", "Xs ago", "X mins ago" or "X hours ago" fashion;
"yesterday" is defined to be the time range 2014-09-08 14:31:44Z to 2014-09-09 14:31:43Z (or ...
Thanks; there was a bug on the "tag engine" (the backend system that deals with this stuff) that failed to update the "count" of an index when that index was being reduced to zero (it is fine when reducing in general - just the zero case is the problem). This meant it was happily reporting data that it knew wasn't "featured" (or whatevever) any more. ...