The discrepancy is by design:
Total reputation is your current reputation on the site (accurate to within 24 hours).
Month reputation is the amount by which your reputation changed that month, excluding "private" reputation events. Certain reputation events are excluded from your public user profile, such as deleted posts or downvotes, so those are excluded ...
I can't believe that there is no answer yet where people could vote for the capital M and lowercase k. This is one.
+1 for international standards here. -1 if you dislike international standards.
Disclaimer: I'm a non-native English speaker and user of SO and SE sites. And perhaps I can speak for some other users who are more familiar ...
Based on David Fullerton's answer, I've written a simple user script that adds a "hotness" indicator to the question infobar:
To use the script, you'll first need to install a user script manager like Greasemonkey or Tampermonkey for your browser, if you don't have one already. Then click this link, which should prompt you whether you want to install ...
Japan has a very long and storied history. Little known is that during the Yayoi era the Japanese invented computers, the internet, and yes, even Stack Overflow, but unfortunately the database became corrupted sometime during the Warring States era. That's why the stats seem wrong. What is certain, however, is that 8.7 questions/day over 2013 years makes ...
It will be, just haven't gotten there yet. Implementing it on other code bases is trickier and involves some duplication. We want to make sure it's exactly how we want it on the main Q&A engine before duplicating anything to the other sites, as that potentially means fixing n things rather than 1 down the road. Also, there are a few APIs and such to ...
So here's the deal. Our image path code sucks. It's bad. It's no one's fault, it's just the result of years of special cases and new use cases that never got a full rewrite of love they need. I know this code pretty well and still spent today git reverting my changes getting nowhere. This is such a great example of tech debt it's ridiculous.
Ultimately, we ...
Here's the explanation:
There are 119 sites in the drop-down menu, there are 117 sites listed as Q&A sites under stackexchange.com/sites. The two sites that are not there are Area 51 (which is still linked in the footer, but is not a Q&A site) and Mathematics Educators, which is in private beta at the time of writing this answer.
The 233 that is ...
Stack Exchange interacts with the community via The Loop, a system whereby hand-picked individuals from a diverse range of backgrounds who are excited about the growth of Stack Overflow are given the opportunity to provide feedback about some parts of the Stack Overflow functionality.
The other Stack Exchange websites are not currently represented.
You can ...
Well this was fun to debug. I changed this recently from a ton of API calls to direct DB queries as part of a massive HTTP overhaul we're doing internally (moving internal traffic to HTTPS).
In the method, it's now a Parallel.ForEach fetching many site moderators at once (we need data stored in each site's database). 3 methods down there was a "current ...
This should be back online, we've been attacked in a variety of ways the last 12 hours, it's been fun.
This was not so much a direct attack as a very abusive crawl bot from china (not even related to a search engine). This was causing us to load profiles on SE.com like crazy, tying up the API backend that serves those default profiles and inboxes, the ...
Or is the idea that the selection algorithm itself (being man-made) is written in such a way that some people may find it unreasonable and arbitrary?
Yes, exactly that. The algorithm, or rather, parts of it, have been selected arbitrarily (say - things like the relative weights of different factors).
This is actually an API bug, we're not returning a launch date for patents since it never went through Area 51.
This will be fixed in the next API deploy (should be a handful of minutes from now), and when the site stats fall out of cache on stackexchange.com everything should make sense again.
So, I looked around and found out that yes, both the data explorer and stackexchange.com still have a few obsolete openId providers listed in the login / signup options.
I have pushed fixes to both, which will remove claimId (and a couple of others) that are no longer in operation.
The obsolete openId providers will be gone in the next builds of either.
It's simply an artifact of going 'out of the box' to stand up a site. Our system is built around:
Site topic is proposed on Area 51
Said topic is vetted with a clear statement of purpose and audience
A private beta for the site is brought up
If all goes well, site goes into public
Our international sites are developed and tested on our development tier, ...
As far as I can tell, the below sites will be counted in the "higher" count and won't be counted in the tour page number:
Sites during Private Beta phase
Experimental sites, e.g. https://cs50.stackexchange.com
Area 51 which isn't really a Q&A site.
The above gets a strong positive nudge from the fact the full sites list on stackexchange.com also ...
The main issue here is creating a new Q&A site - the subdomain is just an implementation detail.
The process for suggesting and creating a new site is done via Area 51, and explained pretty extensively in its FAQ.
In the 6 to 8 weeks this takes to get fixed, you can use the following userscript that solves the bug:
// @name set selected site
// @namespace https://meta.stackexchange.com/users/158100/rene
// @version 0.1
// @description set selected site in league
// @author rene
// @match https://stackexchange.com/...
That list of sites is sorted according to what StackExchange.com considers to be the "default" sort. It's a value calculated per site that's a combination of total question and answer counts, answered %, total users, and daily visits, sorted in the descending order.
((TotalQs + (TotalAs / 3)) * PercentAnswered / 100) + TotalUsers + ...
We're beginning to make some long-term changes to our code base to completely remove Linq2SQL, unfortunately the aggregation event hook that relays comment creation and deletion to the central network database was in a place specific to .SubmitChanges().
I've hooked aggregation up to our new POCO version (inserts/deletes via dapper) and it will start ...
I think this would be a bit misleading, considering that the Careers site is only for programming jobs and is tightly integrated with Stack Overflow. There are lots of sites on the Stack Exchange network, but only one or two of them deal with computer programming.
In fact, if I saw a link to http://careers.stackexchange.com/, I would assume that was a way ...