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

Allow messages to be marked as "don't store" #985

Closed
jm-clius opened this issue May 31, 2022 · 0 comments · Fixed by #1119
Closed

Allow messages to be marked as "don't store" #985

jm-clius opened this issue May 31, 2022 · 0 comments · Fixed by #1119
Assignees
Labels
good first issue Good for newcomers

Comments

@jm-clius
Copy link
Contributor

This forms the implementation part of vacp2p/rfc#441

Problem description (copied from: vacp2p/rfc#441)

Sometimes the application might produce messages that don't need to be stored, an example would be a ping to show that you are online, or for example messages that are time sensitive (say a push notification, through our current push notification system, which would be ignored if retrieved at a later date).

In those cases it would be useful to mark them as "don't store", so that they are not stored by store nodes. This would improve bandwidth performance of the overall network and of the clients, at the cost of some metadata leaking (though can be optional).

@jm-clius jm-clius added the good first issue Good for newcomers label May 31, 2022
@jm-clius jm-clius added this to the Release 0.11 milestone May 31, 2022
@jm-clius jm-clius removed this from the Release 0.11 milestone Jun 22, 2022
@jm-clius jm-clius added this to the Release 0.12 milestone Aug 26, 2022
@jm-clius jm-clius added this to Waku Sep 2, 2022
@jm-clius jm-clius moved this to In Progress in Waku Sep 2, 2022
@jm-clius jm-clius moved this from In Progress to Done in Waku Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants