Skip to content

[stable30] feat(email): Recognize guests invited via email #13617

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.

Sign up for GitHub

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

Merged
nickvergessen merged 14 commits into from
Oct 23, 2024
Merged

[stable30] feat(email): Recognize guests invited via email #13617

Changes from 1 commit
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
95fbabb
feat(email): Recognize guests invited via email
nickvergessen Oct 9, 2024
dd4ca2d
fix(email): Use a hash for the actor ID for better GDPR compliance
nickvergessen Oct 15, 2024
2a3abc2
fix(email): Treat email guests like normal guests in some cases
nickvergessen Oct 15, 2024
94982d3
fix(email): Allow mentioning email guests
nickvergessen Oct 17, 2024
69ba9f1
fix(email): Fix handling of email guests in system messages
nickvergessen Oct 17, 2024
91104cc
feat(email): Handle mentioned email guests
nickvergessen Oct 17, 2024
b67d2f1
feat(emails): Allow banning email guests
nickvergessen Oct 18, 2024
a34e94d
fix(emails): Expire the session but not the attendees for email guests
nickvergessen Oct 18, 2024
d3f4239
fix(calls): Count email guests as guests in the call summary
nickvergessen Oct 18, 2024
25e5a4e
docs(bots): Clarify the random guest actor id
nickvergessen Oct 18, 2024
4de1a98
fix(emails): Use dedicated key in API response
nickvergessen Oct 18, 2024
53b5cfe
fix(emails): Fix integration tests assuming the email is the actorId
nickvergessen Oct 18, 2024
a5644be
chore(openapi): Recompile openapi
nickvergessen Oct 18, 2024
b0df6a3
fix(ban): Allow email guests to bypass bans on their IP
nickvergessen Oct 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs(bots): Clarify the random guest actor id 
Signed-off-by: Joas Schilling <[email protected]>
  • Loading branch information
@nickvergessen @backportbot
nickvergessen authored and backportbot[bot] committed Oct 23, 2024
commit 25e5a4e9a638bd26344d599e54b7c91759f59e6f
2 changes: 1 addition & 1 deletion docs/bots.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ The content format follows the [Activity Streams 2.0 Vocabulary](https://www.w3.

| Path | Description |
|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| actor.id | One of the known [attendee types](constants.md#attendee-types) followed by the `/` slash character and a unique identifier within the given type. For users it is the Nextcloud user ID, for guests a sha1 value. |
| actor.id | One of the known [attendee types](constants.md#attendee-types) followed by the `/` slash character and a unique identifier within the given type. For users it is the Nextcloud user ID, for guests and email invited guests a random hash value. |
| actor.name | The display name of the attendee sending the message. |
| object.id | The message ID of the given message on the origin server. It can be used to react or reply to the given message. |
| object.name | For normal written messages `message`, otherwise one of the known [system message identifiers](chat.md#system-messages). |
Expand Down