Skip to content
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

Closed
7 tasks done
nickvergessen opened this issue Dec 19, 2023 · 12 comments
Closed
7 tasks done

🌐 Federated invitation handling 💌 - API #11278

nickvergessen opened this issue Dec 19, 2023 · 12 comments
Assignees
Labels

Comments

@nickvergessen
Copy link
Member

nickvergessen commented Dec 19, 2023


@nickvergessen
Copy link
Member Author

  • Boolean - Allow incoming
  • Boolean - Allow outgoing
  • Array - List of groups allowed to federate
  • Boolean - Filter federation servers by trusted server list of server

@SystemKeeper
Copy link
Contributor

public function jsonSerialize(): array {
return [
'id' => $this->getId(),
'user_id' => $this->getUserId(),
'state' => $this->getState(),
'local_room_id' => $this->getLocalRoomId(),
'access_token' => $this->getAccessToken(),
'remote_server_url' => $this->getRemoteServerUrl(),
'remote_token' => $this->getRemoteToken(),
'remote_attendee_id' => $this->getRemoteAttendeeId(),
];
}

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:

image

I assume we should add that to the invitation endpoint as well?!

@SystemKeeper
Copy link
Contributor

SystemKeeper commented Feb 1, 2024

Same invitation can be accepted multiple times:

image

Inviting the same user does add a new system message each time (although no push notification):

image

@SystemKeeper
Copy link
Contributor

SystemKeeper commented Feb 1, 2024

Please split subject and message:

$notification->setParsedSubject(str_replace($placeholders, $replacements, $message));
$notification->setRichSubject($message, $rosParameters);

As we did for recording:

if ($notification->getSubject() === 'record_file_stored') {
$subject = $l->t('Call recording now available');
$message = $l->t('The recording for the call in {call} was uploaded to {file}.');
} elseif ($notification->getSubject() === 'transcript_file_stored') {
$subject = $l->t('Transcript now available');
$message = $l->t('The transcript for the call in {call} was uploaded to {file}.');
} else {
$subject = $l->t('Failed to transcript call recording');
$message = $l->t('The server failed to transcript the recording at {file} for the call in {call}. Please reach out to the administration.');
}

So push notifications can correctly show a subject and a message

@nickvergessen
Copy link
Member Author

nickvergessen commented Feb 2, 2024

Please split subject and message

I think we should at least have the inviter in the subject

Suggestion:

{user1} invited you to a federated conversation

{user1} invited you to join {roomName} on {remoteServer}

@SystemKeeper
Copy link
Contributor

Sounds good to me 👍

@nickvergessen
Copy link
Member Author

nickvergessen commented Feb 2, 2024

@SystemKeeper
Copy link
Contributor

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?

@mahibi
Copy link

mahibi commented Feb 5, 2024

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

@SystemKeeper
Copy link
Contributor

SystemKeeper commented Feb 5, 2024

same for room name

Should be fixed with #11505 already

@nickvergessen
Copy link
Member Author

Inviting the same user should not result in a new system message each time

@nickvergessen
Copy link
Member Author

Assuming all is done for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants