Suggestion - Cross-channel replies
Have replies carry over to different channels. For example, if I want to reply to someone's suggestion in #suggestions, but I need to do it in #suggestions-discussions, I want to be able to hit reply to that suggestion and then switch to #suggestions-discussions with the reply still active. Currently, if I were to try to reply, the reply thingy would go away when I switched to the discussion channel. This was previously done by copying the reply text and pasting it into the other channel, but since replies no longer apear in the chatbox, this isn't possible.
-
Was going to suggest this myself!
I think one way to implement this might be by having post links in a post turn a post into a reply? That way the current functionality of messages written in one channel staying there as a draft is retained.
3 -
"Replying to multiple submissions at once"
Reply pointers point to a single message.
0 -
It would also be great if that persons DMs was the first channel you could reply in
0 -
If you make this, discord may become better than telegram :) . In general, take a closer look at the telegram and take it's best features.
0 -
Yeah, I know so many people that wish this feature would be a thing too...
For the implementation:
Every chat message has a link that looks like this: https:// discord.com/channels/:server-id/:channel-id/:message-id (for DMs the server-id is '@me')
And clicking on a link like this in a message basically has the effect we want... Discord just has to hide this link behind the replied message reference. But they don't do that currently (idk why not).
Here is what they do:
- Every message is a div-container with the message-id in the id-attribute. (That's how you can find each message within the code)
- Clicking on the replied message reference calls a JavaScript event that scrolls smoothly to that message and plays the flash animation.
- This event also wraps the message that was replied to in another div with the 'backgroundFlash' class. This container is responsible for the flash animation. After the first time, the user clicks on the replied message reference, the message will not be wrapped in another container again.
- (idk why they do not simply add that class and animation to the message container while the event is called, but ok, they'll have their reasons)
The click event with the cross-channel-reply feature would first have to jump into the other channel (such a feature exists already with the #channel reference) and then scroll to the message.
This feature clashes a bit with the message cache feature (the message that you are typing is stored per channel, so you can look in other channels and come back to continue typing on it).
My idea on this issue is:
If you enter the reply-mode and switch channels, then it checks if you already have begun to type a message there. And if yes, then it aborts the reply and lets you continue working on your older message, so no work is lost. You would lose the reply-mode and would have to go back and enter it again by replying to that message, but that is an acceptable cost, I think. If no, it would let you work on a reply in that channel.
The drawback of this would be, that the reply feature would be application-wide and not channel wide anymore, which means you can only work on a reply to one message at a time.
This could be avoided with another reply-mode flag (like the flag 'ping the one I'm replying to or not').
If you enter a channel with the cross-channel-reply-mode on, where you are already working on a reply, then it would gray out the cross-channel-reply and would leave you with the choice between canceling it or the in-channel-reply. If you don't cancel one, the app prefers one of them and cancels the other one for you (up to the app developers). (This would essentially create a stack of these 'Replying to ...'-things, and potentially enable multi-message-replies in the long run.)3 -
Yup, I'd love to see this.
It helps steer the conversations into correct channels, too, which would be my primary use. People get off topic, and anything to help pull people to the correct channel would be great!0 -
Want to bump this, I was going to make my own feature request. Thank god so many people already think this is a good idea.
0 -
I'd also just like the feature to EMBED a message. instead of a big ugly link (that susses people out), I'd like to be able to (like I do for channel or user reference or message) bracket something in <> and add a # or @ and it automatically KNOW this is a mention to a message so it should embed it.
we can already embed things manually IN text chat with ```s surrounding something or implant direct code in a separate, easy to read font with `s, but I'd like the ability to do like a Twitter "Quote Retweent" instead of just taking out snipping tool or snip and sketch to do what I can type faster or make not look so scuffed.
It's adjacent to the idea of pinning stuff, but server wide, which would be perfect with the concept of community servers. Instead of relying on a bot to do that outside of discord, then feed it back in, why not just implement an "in-house" way to keep our data all inclusive to discord.gg and discord.com?0
Please sign in to leave a comment.
Comments
8 comments