MSN nick keeps switching randomly (or so it seems)

[atourino]

On my MSN account I see that my Display name keeps changing when I send messages to my contacts. They report that my name is the same but in my window my nick changes to different nicks of contacts present in my contact list. I don't see a pattern. Will add to the bug report if I notice anything else.

[nosnilmot@…]

(In [b576470ab9bee5e0b1c48de1e78e3e6234254cdb]) Don't update our local display name when we get a response from the server when we store buddies' friendly names on the server. Fixes #4062.

For other people who encounter this issue with Pidgin 2.3.0 I suggest you set an Alias for your account, your own friendly name is *not* being set to random things - this is a purely local display issue.

[wpliao]

I am suffering from the same problem here, version 2.3.0, where my friendly name displayed in my chat window has been randomly changed to one of my contact's, and it seems to be the person who has recently changed their status to online (but I could be wrong).

While the other person engaged in the chat does not see the incorrect friendly name (i.e. the other person sees the what I have previously entered), the incorrect friendly name is stored in the log file and also shows up as the default value in the input box when I attempt to update my friendly name.

This means somewhere in the program it mistakenly adopts the incorrect name internally and globally in the program although the process to update the friendly name has not been initiated.

The trick of using an alias for myself may work (it seems to work for the last couple hours, but there hasn't been anyone logging on during this time and will not be at this hour). However, setting an alias means I need to update my alias every time I change my friendly name (so I can see it in my own chat window), and I do not understand why I need to enter the same thing twice. Besides, I like to change my friendly name, which adds fun to messaging especially when the new name has a subtle meaning to the engaged conversation, but this is not fun if I don't see the friendly name myself.

I do not quite understand why the status has been changed to closed, although a temporary work-around has been offered, the actual problem has not been fixed. I'd really appreciate if this bug can be reset to open/assigned, or, even better, if this bug can be fixed.

Thanks to all.

[nosnilmot]

It's been closed because a fix has been committed to our source control system, which will be included in the next release.

[vitimnunes]

great...but it's impossible use pidgin until the next release? when the next release be ready?

thanks!

[rekkanoryo]

Replying to vitimnunes:

great...but it's impossible use pidgin until the next release? when the next release be ready? thanks!

If you read the first comment on this ticket, you will find a suitable workaround to your problem.

[mroz]

Replying to rekkanoryo:

If you read the first comment on this ticket, you will find a suitable workaround to your problem.

And if you read the response you'd see why the workaround is inadequate for them. I have the same issue for the same reasons.

A response stating either it is not possible to give an estimated release date, or that releases are typically made every xx weeks, or an actual estimate would be appreciated. Comments implying the authors are unable to read are not.

[rekkanoryo]

Replying to mroz:

And if you read the response you'd see why the workaround is inadequate for them. I have the same issue for the same reasons.

The workaround is only inadequate if the user has a pedantic obsession with abusing the friendly name. That does not render the workaround invalid, inadequate, or insufficient.

A response stating either it is not possible to give an estimated release date, or that releases are typically made every xx weeks, or an actual estimate would be appreciated. Comments implying the authors are unable to read are not.

The release schedule is covered in the FAQ for a reason--if you can't spend the time to read the FAQ, that's not my problem.

Also, we can read; your insults suggesting otherwise are a waste of my time and as such I am done with attempting to help you or anyone else having this issue.

[atourino]

Come on guys. No need for a flamewar. The next release is due in 2 weeks. Until then you can chill. If you *really* need your friendly name and can't live without it for 2 weeks then you can try the official MSN client for these 2 weeks. No biggie there! :D Not being able to change your friendly name is an annoyance, not a showstopper.

[mroz]

Replying to rekkanoryo:

Replying to mroz:

And if you read the response you'd see why the workaround is inadequate for them. I have the same issue for the same reasons.

The workaround is only inadequate if the user has a pedantic obsession with abusing the friendly name. That does not render the workaround invalid, inadequate, or insufficient.

The workaround is inadequate for the clearly described use case. That you think that is a misuse is neither here nor there, since your subsequent response doesn't address the issue. By all means state that kind of usage is considered misuse & no effort will be expended on supporting it, however simply insulting a user with no rational basis is pretty hard to justify.

A response stating either it is not possible to give an estimated release date, or that releases are typically made every xx weeks, or an actual estimate would be appreciated. Comments implying the authors are unable to read are not.

The release schedule is covered in the FAQ for a reason--if you can't spend the time to read the FAQ, that's not my problem.

I don't consider it reasonable to expect a user to read /all/ available documentation to find such information, however certainly searching for it does seem reasonable. I thought I had tried this. I must have been mistaken as a search now for 'release schedule' finds it pretty quickly in the faq. My appologies for this oversight.

Nevertheless, I find you attitude saddening & dissappointing. I don't consider anyone gains from insulting someone who makes such a mistake.

Also, we can read; your insults suggesting otherwise are a waste of my time and as such I am done with attempting to help you or anyone else having this issue.

My suggestion, at best mildly insulting, was actually based on logic & intentionally merely mirrored your own behaviour. /If/ you had read the post concerned, there was no way your response to it could itself be considered logical. Your similar insult, which it seems you consider reasonable, was not founded on such reasoning.

I'm quite tired of dealing with irritable people. TBH While I appreciate that if I have repeated cause & choose to act as I have done in this thread, I might very well alienate enough devs that if I ever need their help, I won't get it, I don't think I particularly care. I consider intollerance of rude behaviour to be of higher priority.

[mroz]

Replying to atourino:

Come on guys. No need for a flamewar. The next release is due in 2 weeks. Until then you can chill. If you *really* need your friendly name and can't live without it for 2 weeks then you can try the official MSN client for these 2 weeks. No biggie there! :D Not being able to change your friendly name is an annoyance, not a showstopper.

Thanks, the info's appreciated. I also found in the faq 'every third Thursday' barring showstoppers.

This issue is not a showstopper of course, as you point out, but I don't think anyone claimed it was. Rather it blocks the originally described use case, which would be hard to describe as anything other than a mild annoyance for most users, which the workaround will solve for all but a small proportion of them.

The bigger annoyance for me is having my logs corrupted up until I applied the workaround. Nothing that can't be fixed though in the html case. Text based I would guess might be irrepairable.

Thanks for the helpful response.

[skerit]

I just installed Pidgin 2.3.0 on a few computers at work (We mainly use the MSN protocol, work through a proxy) but this problem hasn't been fixed.

We also don't see our own name, but the name from someone on our list...

[skerit]

Replying to skerit:

I just installed Pidgin 2.3.0 on a few computers at work (We mainly use the MSN protocol, work through a proxy) but this problem hasn't been fixed. We also don't see our own name, but the name from someone on our list...

Appologies, I thought this ticket was in reference to the previous version.

[rudlavibizon]

Ha, the changed name becomes visible to other persons sometimes. Which caused a frustrating and funny conversation this morning. My name was changed to the name of the person I was chatting, she thought I was making a prank, and I didn't know who I was talking to at all nor 'who I am' because my name was displayed as some other. You should make more bugs like this or a special plugin called confusion. :D

[emilal]

In Pidgin v.2.4.2 (Windows) this problem still exists - change the nickname in MSN Live Messenger, logout, login in Pidgin - all other IM users see the old nickname instead of new one.