You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 26, 2021. It is now read-only.
Currently the framework does not support puppeting the matrix user, that is being bridged.
That means that using the framework also involves keeping track of an additonal matrix client/api in order to puppet this user as well. It also requires own code to decide in which way an event is supposed to be handled - either relaying the message via the framework (relay_service_message) or relaying it as the real user (again, having to write own code for submitting messages and room events via the matrix api since the framework cannot masquerade a user not in the user-namespace).
Do you have any plans or ideas regarding this already ?
The text was updated successfully, but these errors were encountered:
Currently the framework does not support puppeting the matrix user, that is being bridged.
That means that using the framework also involves keeping track of an additonal matrix client/api in order to puppet this user as well. It also requires own code to decide in which way an event is supposed to be handled - either relaying the message via the framework (
relay_service_message
) or relaying it as the real user (again, having to write own code for submitting messages and room events via the matrix api since the framework cannot masquerade a user not in the user-namespace).Do you have any plans or ideas regarding this already ?
The text was updated successfully, but these errors were encountered: