Adding this would seem like a low effort/high reward type of thing. It would certainly open up a lot of possibilities in seeing how the Trilogy is used as a whole, instead of analyzing individual sites in a vacuum.

To make it easy to integrate into the current structure, this data could be exported in a new "table" with 4 columns (one for each Trilogy site user id; NULLable to account for no linkage), with one row per user.

Obviously, this would be a Trilogy-specific feature, so in terms of file structure, the new data should go in a separate folder from the 4 dump folders.

Since everyone's linked accounts are shown publicly on the user page, I don't think there are any privacy concerns that need to be dealt with here.

  • that sounds similar to the way I suggested the data be included meta.stackexchange.com/questions/23615/… – Kyle Cronin May 18 '10 at 19:49
  • @Kyle: Yes, you're right. Sorry, I didn't see that post. Hmmm.. what should I do with this question? – Jon Seigel May 18 '10 at 20:03
  • note you can get a pretty accurate estimate using the EmailHash – waffles May 18 '10 at 22:02
  • This question is OK - it's an issue that was never addressed. I was mainly trying to populate the "Linked" section. – Kyle Cronin May 18 '10 at 22:03

The users file has as documented since February 2014 an AccountId attribute. This enables to link users between several sites. Notice that the attribute emailhash, as mentioned in the comments, is now always null in SEDE and for that reason non-existent in the users.xml in the data-dump.

I used AccountId in some questions I answered, for example:

| improve this answer | |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .