element-hq / element-hq/element-web

Append /shrug instead of prepend /shrug

Open
#20,525 0 comments 1 reaction 0 assignees View on GitHub
A-Slash-Commands O-Uncommon S-Tolerable T-Enhancement X-Needs-Product
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Your use case

#### What would you like to do?

Append the shrug characters to the end of the message instead of the start.

#### Why would you like to do it?

When a longer message is typed, which has several points, it's valuable to have the shrug at the end with your final statement on the topic. It also lets you control when the shrug is sent, as you decide where to stop, yet every message starts somewhere.

"While that is an option available, it shouldn't be used like that. If you do decide to use it like that, I can't help you ¯\_(ツ)_/¯ "
vs
"¯\_(ツ)_/¯ While that is an option available, it shouldn't be used like that. If you do decide to use it like that, I can't help you"

Discord and Keybase both exhibit this behavior.

Currently, obtaining this behavior either means copying the characters manually OR sending a second message after the fact of just shrug, which has different social connotations than it being in the same message. Whereas it being in the same message communicates how you feel, going out of your way to send it in yet another message can be seen more as blowing someone off by further communicating your uncaring stance before they can reply.

#### How would you like to achieve it?

I'd like for someone to replace the line of code which executes "shrug" + message with message + "shrug"? Not really sure what to put here.

### Have you considered any alternatives?

Manually adding in the shrug characters after messages, after a search for them, or editing a sent message to move them, or using *shrugs* are all possible alternatives. I find myself sending many messages intending, and expecting, to append shrug though just for it to be preprended and don't care to invest the extra effort.

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.