Implement Room Workflow #16
No reviewers
Labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
NB-Public/rocketchat2matrix!16
Loading…
Reference in a new issue
No description provided.
Delete branch "implement-rooms"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements #3
9552660bf9560327d5cd906f929144ecc4f0db109d73018ceato4ef070ed8532ec96187bto233df882ae233df882aetod45edc95e4cc8fa5838ato5f947b5deb5f947b5debto113f061b8e113f061b8etodcb231af93dcb231af93toad9b6226b7ad9b6226b7toba03626051Synapse overwrites the room owner sent upon creation with the authenticated user sending the request. This causes us a few problems, as we can't create direct chats over the API, for example.
Possible solutions that come to my mind are:
Any opinions, @sven.seeberg or @TreJo?
I think option 3 is definitely the best option. We will need user acces tokens anyways, because as you already mentioned we can only invite people into rooms over the API, but they still need to accept the invite, which they should not need to do manually.
ba03626051to08fcca5ed208fcca5ed2to924f606b4dWith #18 the token is saved now, I'll see to use it for room creation now.
924f606b4dtoce5a668f1c31b07fbe8d98fe90264f34670d445907a4f426bf07a4f426bf0b27d5ad280b27d5ad284692c7edea25f6284d065d5c751de8375afc834cto33d37b025c33d37b025ctoa06e379531WIP: Implement Room Workflowto Implement Room Workflow