Is your feature request related to a problem? Please describe.
The current bridge design doesn't use Appservices on Matrix. It would be nice to support MSC4144, which are "per-message profiles". Clients will now see that each bridged person looks like a different user, if the client supports it.
Describe the solution you'd like
Send com.beeper.per_message_profile and <strong data-mx-profile-fallback>NAME: </strong>
Describe alternatives you've considered
There is currently not any other way to use a per-message-profile-like system without MSC4144
Additional context
mautrix/bridgev2 has a work in progress implementation
Is your feature request related to a problem? Please describe.
The current bridge design doesn't use Appservices on Matrix. It would be nice to support MSC4144, which are "per-message profiles". Clients will now see that each bridged person looks like a different user, if the client supports it.
Describe the solution you'd like
Send
com.beeper.per_message_profileand<strong data-mx-profile-fallback>NAME: </strong>Describe alternatives you've considered
There is currently not any other way to use a per-message-profile-like system without MSC4144
Additional context
mautrix/bridgev2 has a work in progress implementation