pm/FURPS/application/status_private_chats.md
fryorcraken c3c072b4f3
Milestone tidy up
# Conflicts:
#	draft-roadmap/integrate_nwaku_in_status_desktop_relay_mode_only.md
2025-06-10 22:00:16 +10:00

31 lines
973 B
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Status Private Chats FURPS
Waku specific FURPS, **before** integration of the Chat SDK.
## Functionality
1. Features other than one-to-one chats are either removed or can be disabled.
2. One-to-one chats traffic is not impacted by other features.
3. One-to-one chats are functional when rate limited by 100 msg per 10min over Waku or less.
## Usability
1. Features other than one-to-one chat can be removed or disabled.
2. A user with only one-to-one chat enabled can expect limited bandwidth and resource usage and a smooth experience.
## Reliability
1. One-to-one chats implementation behaves as specified (**Vac-QA**).
## Performance
1. 99% of one-to-one user messages are eventually received by their recipient, within 5 minutes of being online (**Vac-DST**).
2. One-to-one chats non-user messages do not consume over 20% of the allocated quota (**Vac-DST**).
## Supportability
1. status-cli/backend
## + (Privacy, Anonymity, Deployments)
1. ...