28

Steps to reproduce:

  1. Change your name on Stack Overflow. After some time it won't allow to change your name again for one month

  2. Create user account in Super User or change your name on Super User with the same OpenID

  3. Go to Stack Overflow and associate your account with Super User

Now the name on Stack Overflow has changed to reflect the one on Super User

Is this a feature or a bug?

|improve this question
  • 4
    reproduced. But I'd say "It's not a bug, it's a feature" – Tobias Kienzler Jun 25 '10 at 10:25
  • @ Tobias - Then it breaking another condition . then it wont be feature .. I would say ..its mistakenly done .. still you need to change code for association .. – Tree Jun 25 '10 at 10:57
  • 12
    Yay! -------------- – Pëkka Jul 5 '10 at 16:31
  • 3
    status-bydesign ♥ ♥ ♥ ♥ ♥ ♥ ♥ ♥ ♥ – Pëkka Mar 8 '12 at 19:43
  • m so happy this bug exists!! :) – NoobEditor Jan 1 '14 at 7:55
  • I heard a rumour that this has changed. Is it true? – Lightness Races in Orbit Mar 14 '14 at 14:02
  • @RagingScallion: Right, the rumour came from you, but by posting here I was hoping someone authoritative could answer. – Lightness Races in Orbit Mar 14 '14 at 15:23
30

This is now my favourite bug report on Meta.

Finally, anarchy is restored.

Thank you!

|improve this answer
12

I actually reported this in a question way back when I first joined. It's partly why I was stuck with the name "ccornet" for so long back then (it was supposed to be ccomet), and it's also how I changed my name to "Grace Note" two days ago but can change it back as early as July 11th. It was established that this was basically a feature, at best it allows you to change your name once a week, and it wasn't worth fretting about for the effort it'd take to implement validation on the profile copying. So I deleted the question.

There was also a report, admittedly in just a comment, in this early post. It didn't really raise much steam, so I always assumed it was something of a silent trick.

The direct cause is that profile copying, not merely association, does not get validated for name changes. This is because it is just copying data from one table to another, instead of accessing the Name and changing it directly. So the copy function ends up bypassing the restriction. The name change in itself is expected behavior, but the bypass may well be.

The new system causes automatic profile copy in some scenarios when you associate two accounts. I haven't quite figured out what these scenarios are, as I've been repeatedly associating and unassociating my SU and SF accounts but neither had a profile copy that wasn't manually instigated by me.

|improve this answer
  • 12
    Wait, so you actually were ccornet for a while? That explains the confusion. – mmyers Jun 25 '10 at 14:13
  • 8
    Oh thank goodness, my eyes do work properly. – Jon Seigel Jun 25 '10 at 14:15

You must log in to answer this question.

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