logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-03 22:53:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update as per discussion

Browse Source
This commit is contained in:
fryorcraken 2025-06-30 15:44:12 +10:00
parent bce4813c9c
commit 6eaff61eca
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
FURPS/application/signal_network.md
View File

@ -4,13 +4,13 @@ TODO: Update in deliverable
## Functionality ## Functionality
1. Advertise intent to join a given session. 1. Establish direct connection to remote peer using their public key as identifier.
2. Discover remote peers willing to join a given session.
3. Establish direct connection to remote peer with same intent to join a given session.
## Usability ## Usability
1. Developers selects discovered nodes to connect to. 1. Developers can implement their own application-level discovery method.
2. Only remote peer's public key is needed to initiate connection.
3. Hook is provided for developer to filter inbound connection requests.
## Reliability ## Reliability
@ -21,8 +21,9 @@ TODO: Update in deliverable
1. Developers can use this protocol in web application, imported from npmjs.com. 1. Developers can use this protocol in web application, imported from npmjs.com.
2. Developers can use this protocol to initiate WebRTC connections. 2. Developers can use this protocol to initiate WebRTC connections.
3. Only 1:1 direct connections are supported.
## + (Privacy, Anonymity, Deployments) ## + (Privacy, Anonymity, Deployments)
1. Network observers cannot retrieve node connection details without knowing session identifier. 1. Network observers cannot retrieve node connection details; forward secrecy is **not** included.
2. STUN and TURN servers may be required for WebRTC usage. 2. STUN and TURN servers may be required for WebRTC usage.