I've just made a map of all Stack Exchange sites, except for the three biggest ones:
(A high(er) res png file) (EDIT: there was a PDF file, but for some reason it was eating more than 1 GB of memory, at least on my computer)
- The graph is based on users with rep>=200 at a given site.
- Node size is related to number of such users.
- There is an edge between two sites if there are common users more often that one would expect on random, see on observed/expected ratio on Stats.SE.
- Colors are indicating different graph communities (nodes which have much more connections inside a group than with other groups).
On GitHub there is code and a recipe how to make a similar plot (or tweak this one). Also, you may want to look at a Graph Map of Math.SE.
Why not include Server Fault, Super User, and most importantly, Stack Overflow?
Stack Overflow, to some extent, is a different story from the other sites. When it comes to Server Fault and Super User - unfortunately, the Stack Exchange API (or at least - my Python wrapper, se-api-py) has some issues with obtaining more than 100k items.
Any questions and comments are welcome.
account_id
) has accounts more sites, e.g.['gaming', 'rpg', 'boardgames']
(each with rep>=200 just to filter out people how are not active at all, otherwise the resulting graph is a mess). Looking at similar texts may be tricky (but good e.g. to suggest migrations), tags at different sites may have different meaning, etc. Anyway, there are many possibilities to mine the SE data. My code is on GitHub, feel invited to use it. When it comes to using my API - I need to clean it up before uploading.account_id
. AFAIK the only field that is comparable across sites isEmailHash
.acount_id
(AFAIK, an identifier of account across sites) shouldn't work?account_id
is an API only thing, and on a bit of testing at api.stackexchange.com/docs/… and api.stackexchange.com/docs/… it does return the sameaccount_id
for me (but notid
).