You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The output of this deliverable is to compile a list of recommendations, for Waku, Status Communities and chat protocols. This should include potential benefits of changes and enable scheduling the work between Status and Waku teams.
Decision on the work to be done and planning it should be part of the output of this deliverable.
The recommendation should be grounded in the output of the previous deliverables of this milestone.
The recommendation is unlikely to encompass the entire chat protocol, and all status message types due to the amount of work it would entailed. Instead, an empirical approach should be taken where changes are prioritised based on the user impact, known limitations and functionalities (e.g. profile backup and device pairing usage of Waku), and telemetry metrics.
This would impact any current usage of Waku by the Status app. Which does include communities, 1:1 chat but profile back and device pairing.
This could include review of discv5 implementation in go-waku and nwaku if bandwidth usage is excessive.
The text was updated successfully, but these errors were encountered:
The output of this deliverable is to compile a list of recommendations, for Waku, Status Communities and chat protocols. This should include potential benefits of changes and enable scheduling the work between Status and Waku teams.
Decision on the work to be done and planning it should be part of the output of this deliverable.
The recommendation should be grounded in the output of the previous deliverables of this milestone.
The recommendation is unlikely to encompass the entire chat protocol, and all status message types due to the amount of work it would entailed. Instead, an empirical approach should be taken where changes are prioritised based on the user impact, known limitations and functionalities (e.g. profile backup and device pairing usage of Waku), and telemetry metrics.
This would impact any current usage of Waku by the Status app. Which does include communities, 1:1 chat but profile back and device pairing.
This could include review of discv5 implementation in go-waku and nwaku if bandwidth usage is excessive.
The text was updated successfully, but these errors were encountered: