add use case sketch

This commit is contained in:
gmega 2025-07-21 11:14:24 -03:00
parent 14a7674bbf
commit 8788573e30
No known key found for this signature in database
GPG Key ID: 6290D34EAD824B18
4 changed files with 46 additions and 0 deletions

View File

@ -0,0 +1,21 @@
From the initial chat with Volo, we got two main use cases, which might actually be one use case:
* 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
### 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.
Whatever we come up with here has important value to the project as a whole though, as enabling Codex on mobile and having a workable solution in messy networks would take care of the single most recurrent complaint we have had from users so far.
### Unknowns
* It's clear that status will run a Codex client within the status app, which will require having lib-codex, but where will _storage_ actually happen? Are nodes expected to connect to each? Are we gonna have "storage" nodes operated by status?
* How can whatever we come up with be abused/attacked? As we understand this, this will likely start giving us a glimpse of what are the characteristics for useful altruistic modes.
* Can we live up to the perf/latency standards of a chat app?
### Meeting Transcripts
* [Initial Chat with Volo](https://docs.google.com/document/d/1UJROxEl7GCEAARhJRVOjYCWVyL2nhKeNvN77yMoJdas/edit?tab=t.8t9d24txz7de#heading=h.29nrust7c16y)

View File

@ -0,0 +1,12 @@
My ideal world scenario is that I can use Codex like I have been using it, to exchange chunked datasets. What I have been missing the most:
1. Light clients (mobile, browser);
2. Being able to publish a dataset without a public IP;
3. Pin to a node;
4. Force remove;
5. Range headers would be cool for Podex.
Václav also says:
"... So going with altruistic mode, doing what Ben came up with (constellations) or similar things (like what I did with Qaku Cache) would bring users -> grow the network and awareness -> give us more time to make durability useful for more people ..."

View File

@ -0,0 +1,3 @@
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.

View File

@ -0,0 +1,10 @@
**Goal.** The goal of this page is to serve as an entry point to the use-case information that enters the Codex project. We flesh those out by project when possible. What has not yet been fleshed out goes under
#### Project Use Cases
* [[Codex Use Cases - Status]]
* Codex Use Cases - Waku
#### Misc
* Václav's Thoughts