logos-storage/logos-storage-docs-obsidian
1
0
Fork 0
mirror of https://github.com/logos-storage/logos-storage-docs-obsidian.git synced 2026-01-02 13:23:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

add link to Waku requirements PR

Browse Source
This commit is contained in:
gmega 2025-07-22 18:30:34 -03:00
parent 47afbac9e8
commit 7ddc92d12a
No known key found for this signature in database
GPG Key ID: 6290D34EAD824B18
3 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
10 Notes/Codex Use Cases - Status.md
View File

@ -3,7 +3,7 @@ From the initial chat with Volo, we got two main use cases, which might actually
* overcoming Waku message size limitations for long messages (why can't they just break those up and send multiple messages though?);
* implementing file sharing, with images (and I suppose audio?) being the main use case; i.e., that gives us a ballpark in content size;
* Jacek
* Jacek mentioned they use bittorrent in some part of their infrastructure, which we could replace with Codex.
### Requirements
**Codex has to run on mobile.** This might be a big deal as mobile networks are notoriously unsuitable to P2P software. Good news is that we got Waku and they seem to have worked around this, so we should start by examining their solution.

3
10 Notes/Codex Use Cases - Waku.md
View File

@ -1,3 +0,0 @@
To be defined. Other than the message size limitation - which to me seems like a bit of a strange use case, as the client could just break up the big message into several smaller messages and reassemble on the other end - I do not have anything very concrete.
Action item for me is to dig deeper into this with Hanno/Franck.

2
10 Notes/Codex Use Cases.md
View File

@ -4,7 +4,7 @@
#### Project Use Cases
* [[Codex Use Cases - Status]]
* [[Codex Use Cases - Waku]]
* [Codex Use Cases - Waku](https://github.com/waku-org/pm/pull/328)
#### Misc
* [[Codex Use Cases - Václav's Thoughts]]