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

make it generic

Browse Source
This commit is contained in:
fryorcraken 2025-06-12 16:02:54 +10:00
parent 6ceb056f80
commit 29ed937750
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
3 changed files with 37 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
FURPS/application/codex.md
View File

@ -1,26 +0,0 @@
# Codex Archiving PoC
## Functionality
1. Any admin in a Qaku Q&A can publish a backup snapshot of the entire thread to Codex once it's reached 20 responses.
2. The admin can publish the corresponding Codex CID with metadata over Waku to a dedicated snapshot content topic
3. Participants can query the Waku snapshot topic for the latest CID
4. Participants can retrieve the archived Q&A from Codex
5. Participants can perform a Store Query for more recent messages following the snapshot timestamp
## Usability
1. Workflow should be conceptually identical, whether the Codex interaction is via a local node or Codex gateway
2. Publishing or retrieving via Codex should be optional
## Reliability
## Performance
## Supportability
1. Web app
## + (Privacy, Anonymity, Deployments)

25
FURPS/application/codex_archiving.md Normal file
View File

@ -0,0 +1,25 @@
# Codex Archiving PoC FURPS
## Functionality
1. Any end user can publish a backup snapshot of the entire SDS log to Codex.
2. End user (may be privileged) can publish the corresponding Codex CID with metadata over Waku to a dedicated snapshot content topic.
3. Participants can query the Waku snapshot topic for the latest CID.
4. Participants can retrieve the archived messages from Codex.
5. Participants can perform a store Query for more recent messages following the snapshot timestamp and SDS state.
## Usability
1. Workflow should be conceptually identical, whether the Codex interaction is via a local node or Codex gateway.
2. Publishing or retrieving via Codex should be optional.
## Reliability
## Performance
## Supportability
1. Developers can use this protocol in web applications.
## + (Privacy, Anonymity, Deployments)

16
draft-roadmap/formalize_and_expand_waku_web_apps.md
View File

@ -54,12 +54,20 @@ Logos Movement Community Enabling
**Owner**: App/Chat Dev
**Feature**: [Codex Archiving PoC](/FURPS/application/codex.md)
**Feature**: [Codex Archiving PoC](/FURPS/application/codex_archiving.md)
**FURPS**:
- F1-5
- U1-2
- S1
- F1. Any end user can publish a backup snapshot of the entire SDS log to Codex.
- F2. End user (may be privileged) can publish the corresponding Codex CID with metadata over Waku to a dedicated snapshot content topic.
- F3. Participants can query the Waku snapshot topic for the latest CID.
- F4. Participants can retrieve the archived messages from Codex.
- F5. Participants can perform a store Query for more recent messages following the snapshot timestamp and SDS state.
- U1. Workflow should be conceptually identical, whether the Codex interaction is via a local node or Codex gateway.
- U2. Publishing or retrieving via Codex should be optional.
- S1. Developers can use this protocol in web applications.
**Checklist**:
- [ ] Specs: link to specs and/or API definition