-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't start a DM conversation #11
Comments
How exactly are you starting a new DM? Discord Messenger doesn't give you that option. |
If you add a new friend on the official client, it will show on the DMs sidebar on Discord Messenger regardless of whether a message has been sent before or not |
This behavior happens on Discord as well, where when you accept a friend request, your new friend's name shows in the DM list. I'm not totally sure how to fix this. |
I don’t think I expressed myself well, sorry. When you click on your new friend’s name on the DM list, you get an empty chat. That is expected behaviour. However, you can’t start a conversation. If you try sending any message, you get the popup error I screenshotted. Once your friend messages you, or you message them through an official client, then you can exchange DMs normally. |
You did, this is normal discord client behavior. When you accept a friend request, their name shows up in your DM list; this appears to be a temporary channel where sending a message actually creates the channel! Since Discord Messenger doesn't have the ability to create DM channels (and probably will never due to antispam concerns), I will need to look for a way to rectify this problem for a better UX. (Preferably without resorting to hacks that check if a friend request was accepted around the same time that the channel was created) |
System: Windows XP SP3 x86
Version: 1.00 MSVC
If I try to start a DM conversation with a friend, I get an invalid request error pop-up. If the DM chain already exists or the other party starts the conversation, I can send messages normally.
The text was updated successfully, but these errors were encountered: