Skip to content

Conversation

@nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Oct 9, 2024

☑️ Resolves

🛠️ API Checklist

🚧 Tasks

  • Add access token to email link
  • Should show that we identified the email in the "Guest name dialog"
  • Using the email as actor id might cause GDPR, need to hash at least?
    • Still need a reliable email address to attendee way
  • Don't abuse user_status line for sending the email to moderators in the participant list
  • Many places assume guests are actorType = Attendee::ACTOR_GUEST while it should be participantType = Participant::GUEST || participantType = Participant::GUEST_MODERATOR ?
    • Email users are not counted or listed in call summary
    • Auto complete search plugin and mentioning
    • ParserSystemMessage::isCurrentParticipantChangedUser
    • Parse SystemMessage when the guest is modified (promoted/demoted/poll/…)
    • System messages generated by the email-user can not find a display name and use wrong actor id
    • Reference provider
    • Cleaning up sessions by last ping?
    • Message::isReplyable
    • Notifier
    • Search result display name
    • Banning should disinvite
    • Check bots
    • Email guests should never expire?
    • ParticipantService::getGuestCount check usage whether email/display names should be expended instead of count the emails as well
    • Signaling participantsModified and roomInCallChanged excludes by actorType
  • ⚡ Test HPB
  • ☎️ Test SIP

🏁 Checklist

  • ⛑️ Tests (unit and/or integration) are included or not possible
  • 📘 API documentation in docs/ has been updated or is not required
  • 🔖 Capability is added or not needed

@nickvergessen nickvergessen marked this pull request as draft October 9, 2024 04:38
@nickvergessen nickvergessen added this to the 🖤 Next Major (31) milestone Oct 9, 2024
@nickvergessen nickvergessen added 2. developing enhancement feature: api 🛠️ OCS API for conversations, chats and participants feature: meetings 📅 Covering the webinary usecase incl. Lobby feature: conversations 👥 labels Oct 9, 2024
@nickvergessen nickvergessen self-assigned this Oct 9, 2024
@nickvergessen nickvergessen force-pushed the feat/6098/recognize-email-invited-guests branch from c2c1274 to a673b3a Compare October 15, 2024 12:45
@nickvergessen nickvergessen marked this pull request as ready for review October 18, 2024 21:57
@Antreesy
Copy link
Contributor

Antreesy commented Oct 21, 2024

For quick test without receiving actual e-mail:
https://<NC_instance>/call/<token>?email=<email>&access=<access_token_from_DB>

For Julius docker setup: https://mail.local also works

Copy link
Contributor

@Antreesy Antreesy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, tested with inviting, banning, chatting

@DorraJaouad
Copy link
Contributor

Tested ✅

@nickvergessen nickvergessen force-pushed the feat/6098/recognize-email-invited-guests branch from 4e2476f to 644c3fa Compare October 23, 2024 04:24
@nickvergessen nickvergessen merged commit fbdbd56 into main Oct 23, 2024
@nickvergessen nickvergessen deleted the feat/6098/recognize-email-invited-guests branch October 23, 2024 12:02
@nickvergessen
Copy link
Member Author

/backport to stable30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review enhancement feature: api 🛠️ OCS API for conversations, chats and participants feature: conversations 👥 feature: meetings 📅 Covering the webinary usecase incl. Lobby

Projects

None yet

Development

Successfully merging this pull request may close these issues.

recognice people invited by mail when they join the conversation

5 participants