search

EionRobb / purple-discord

A libpurple/Pidgin plugin for Discord
GNU General Public License v3.0
382 stars 43 forks source link

Discord new usernames #443

Open alexolog opened 1 year ago

alexolog commented 1 year ago

Has anyone migrated to the new username yet? Were there issues with Pidgin?

LurkerHub commented 1 year ago

Also interested to know. The plugin seems to work with existing buddies that switched to the new ID, but I am hesitant to switch myself.

aidaho commented 1 year ago

Works fine for me.

LurkerHub commented 1 year ago

Thanks! Tried it and no apocalypse so far, log seems as clean as before the switch.

alexolog commented 1 year ago

Thank you!

chainria commented 1 year ago

Quite some of my friends already migrated, I didn't. The only thing I noticed was that Pidgin treats the new usernames as new accounts, the rename logic is not being triggered by this switch. So you got to clean up your contact list yourself. Maybe something worth investigating @EionRobb ?

Edit: Fix typo.

alexolog commented 1 year ago

I rename manually

chainria commented 1 year ago

It seems I have an issue now. One of my contacts - and only one of them - has a split history between username#0 and username#0000 - curiously only username#0000 is on my contact list at all. username#0 seems to "siphon away" messages I send from the official client

alexolog commented 1 year ago

Strange. Can you search for username in blist.xml and see if you have both?

chainria commented 1 year ago

Did search for it. Only one instance found: username#0000 - I don't know where username#0 starts coming from.

Plus, other accounts start to get affected now. username#0 is appearing at more and more username's. Haven't changed my own one yet. Maybe discord is punishing me for not doing as they want me to? :D

Will try to watch the debug log to spot any strange occurences.

alexolog commented 1 year ago

I cannot recreate it. I tried sending messages from the native client to a new-name account, with Pidgin running and without, and it did not use any #0.

What I did notice is that messages exchanged while Pidgin was not running, were not fetched from history when I restarted Pidgin. But that's a separate bug.

alexolog commented 1 year ago

I sometimes start Pidgin with debug log.

In Windows:

@echo off
set PURPLE_UNSAFE_DEBUG=1
set PURPLE_GNUTLS_DEBUG=1
set PURPLE_VERBOSE_DEBUG=1
"%ProgramFiles(x86)%\Pidgin\pidgin.exe" -d > "%APPDATA%\.purple\debug-%date%-%time::=.%.log" 2>&1
chainria commented 1 year ago

Can't reproduce it either. Maybe it was some weird fluke. Tried everything I could the whole weekend. Simply not happening anymore. Maybe it was some weird A/B tests they did or something? I don't know.

chainria commented 1 year ago

I was able to reproduce it. And it really starts to annoy me. Basically every time you message someone not on your friend list, or freshly added, the conversations get split. When you message them from the official client, your own messages will be in username#0 but the replies will be in username#0000

karxi commented 4 months ago

I was able to reproduce it. And it really starts to annoy me. Basically every time you message someone not on your friend list, or freshly added, the conversations get split. When you message them from the official client, your own messages will be in username#0 but the replies will be in username#0000

This is still the case, and remains supremely irritating. It also means that replies no longer show up, presumably because the buffers with your messages and those of others are separate. Numerous times, a conversation is bifurcated—with the other individual's messages correctly under "username", but my outgoing ones stuck in "username#0". What's going on?

In addition to being inconvenient and annoying, this significantly reduces the accuracy of logs, which are a major part of why I use this plugin to begin with. Is there any chance for a fix?