element-hq / element-hq/element-x-android

Please support MSC4171

Open
#3,522 1 comment 4 reactions 0 assignees View on GitHub
T-Enhancement
Dominant language
Kotlin
Stars
2.4k
Forks
624
Avg merge
1d 14h
Merged PRs (30d)
149

Description

### Your use case

#### What would you like to do?
I'm using mautrix-signal bridge, and private chatrooms are named by the signal-user AND the bridge-bot-user.
I discussed this in the chatroom for mautrix-signal bridge and realizied, that element X does not support MSC4171.

In legacy Element the rooms are named only after the Signal-user. That's what i expect.

#### Why would you like to do it?
Consistent room namings in bridged rooms.

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

### Have you considered any alternatives?

Think it is only necessary, that element x has to implement MSC4171

### Additional context

Element X V0.6.3

### Are you willing to provide a PR?

No

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is named. Start by reading MSC4171 and reproducing the private bridged-room naming case described for mautrix-signal; done means Element X names the room after the Signal user without including the bridge-bot user.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin, rust
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.