11

Questions or new users are often migrated to TeX.SX from Stack Overflow (SO). We try to support their account mergers via the Text Building Blocks:

Migrated questions/answers/users

  • [Welcome to TeX.sx!](https://tex.meta.stackexchange.com/questions/1436/welcome-to-tex-sx) Your question was migrated here from another stackexchange site. Please register on this site, too, and make sure that both accounts are associated with each other, otherwise you won't be able to comment on or accept answers or edit your question.

  • [Welcome to TeX.sx!](https://tex.meta.stackexchange.com/questions/1436/welcome-to-tex-sx) Your answer was migrated here from another stackexchange site. Please register on this site, too, and make sure that both accounts are associated with each other, otherwise you won't be able to comment on or edit your answer.

    To make the comment more personal, you can replace another stackexchange site with the respective link, i.e. [so], [su] or [sf] for the big three or [something.se] for everything else, e.g. [ubuntu.se].

However, often times there is confusion and they end up creating a new (separate) account on TeX.SX from their original (say) SO account. If this is the case, how can we facilitate them to have their account merged or make suggestions as to achieve this?

Here is a hypothetical scenario: Assume UserX has an account with SO and the question is merged to TeX.SX. They create a new account UserY. Should we suggest UserY merges the TeX.SX account with SO and then flag it for moderator attention on SO to merge UserY with UserX? Would that solve the problem? Is not, what's the best way to make a suggestion?

1
  • I have to admit that when I first posted the question on SO and it got migrated I did not know what to do to merge the accounts. I was also new to SO at the time. This was quite sometime ago so perhaps things have gotten better. Is there any reason why the account can't just be created automatically since all these sites are really the same within the same corporation so no information is given to a third party?
    – Peter Grill
    Commented Mar 2, 2012 at 3:29

1 Answer 1

Reset to default
5

The easiest thing to do would be to amend your blurbs to specify that they should register with the same openid credentials as what they use on SO.

Of course, if they were unregistered on SO as well, they'd have to register there as well.

5
  • Thanks Anna. Taking @PeterGrill's comment into consideration, it may be that new users who are unfamiliar with the idea of registration across the network still register with different IDs. If this is the case, how would one go about consolidating these accounts? Also, what would be the difference between a registered/unregistered account? Does that have an impact on mergers?
    – Werner Mod
    Commented Mar 6, 2012 at 0:23
  • @Werner Contacting a community team member should do. The main difference between an unregistered and a registered account is that the former is only tracked through cookies on the user's machine, so it's easy to lose ownership of it. A registered account has an OpenID associated with it (i.e. Facebook, Google, Stack Exchange, etc.). There's not much impact on mergers, so long as the user has at least one registered account. If not... give us a shout anyway and we'll fix it up. :)
    – Adam Lear StaffMod
    Commented Mar 8, 2012 at 2:34
  • How do "we give any of the community team members a shout"?
    – Werner Mod
    Commented Mar 8, 2012 at 6:47
  • @Werner You can make a meta post, have a moderator ping one of us in chat, or send an email to the "Contact Us" link at the bottom of each page on the site.
    – Adam Lear StaffMod
    Commented Mar 9, 2012 at 3:50
  • Reminder: if the user is unregistered, cross-site association doesn't really work. Ask them to register - if they use the same credentials, everything should work automatically; if they don't, we can fix it.
    – Shog9
    Commented Apr 6, 2012 at 23:05

You must log in to answer this question.

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