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.

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

Jump to bottom

raw RFC(standards): Status 1:1 chat #168

Closed
Tracked by #165
, #187
...
kaiserd opened this issue Jan 25, 2023 · 1 comment
Closed
Tracked by #165
, #187
...

raw RFC(standards): Status 1:1 chat #168

kaiserd opened this issue Jan 25, 2023 · 1 comment
Assignees
@rymnc

Comments

@kaiserd
Copy link
Contributor

kaiserd commented Jan 25, 2023 •
edited by rymnc
Loading

This issue is part of the SeM application protocols roadmap #165 and tracks specifying the current Status 1:1 chat protocol, which runs on 11/WAKU2-RELAY, in a Vac RFC. (named similar to XX/STATUS-1to1-CHAT)

Open PR: vacp2p/rfc#569

Outlook

In the future, XX/STATUS-1to1-CHAT should run over Waku e2e messaging, a protocol that offers secure end-to-end communication channels (see future Milestones of #165)
@kaiserd kaiserd mentioned this issue Jan 25, 2023
Closed
7 tasks
@kaiserd kaiserd moved this to Next/Backlog in Vac Research Jan 25, 2023
@rymnc rymnc mentioned this issue Jan 31, 2023
Merged
@kaiserd kaiserd moved this to Next/Backlog in Secure Messaging (SeM) Jan 31, 2023
@kaiserd kaiserd removed this from Vac Research Feb 1, 2023
@kaiserd kaiserd moved this from Next/Backlog to Now/In Progress in Secure Messaging (SeM) Feb 6, 2023
@kaiserd kaiserd mentioned this issue Feb 21, 2023
Closed
14 tasks
@rymnc
Copy link

rymnc commented Feb 21, 2023

@kaiserd can we close this?

@kaiserd kaiserd closed this as completed Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rymnc rymnc

Labels
None yet
Projects
Secure Messaging (SeM)
Status: Now/In Progress
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kaiserd @rymnc