-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🌐 Federated invitation handling 💌 - API #11278
Comments
|
spreed/lib/Model/Invitation.php Lines 72 to 83 in 2bf22e1
The endpoint to get federation invitation does not include the conversation name that the user was invited to, but the notification does include that in the rich parameters: I assume we should add that to the invitation endpoint as well?! |
Please split subject and message: spreed/lib/Notification/Notifier.php Lines 466 to 467 in 1ae1017
As we did for recording: spreed/lib/Notification/Notifier.php Lines 359 to 368 in 1ae1017
So push notifications can correctly show a subject and a message |
I think we should at least have the inviter in the subject Suggestion:
|
Sounds good to me 👍 |
The name of the person which shared the conversation is missing on the invitation endpoint, but it is available in the push notification. Can we add it to the endpoint as well? |
same for room name |
Should be fixed with #11505 already |
|
Assuming all is done for now |
FederationController->acceptShare()
could return to user, who accepted a share, a local room (with token. e.t.c), so it could be reused by clients to join room on click => feat(federation): Add room to response when accepting an invite #11459all users / only moderators / only specific groups
on this server to invite users to Talk conversations fromall other servers / only trusted servers
- discuss? feat(federation): Add appconfig options to restrict federation #11503The text was updated successfully, but these errors were encountered: