LAION-AI / LAION-AI/Open-Assistant
Re-work the concept of postID to taskID
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 37.4k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
Originally, the frontends were supposed to be stateless, but it turns out more and more that it might be a better path to make the frontends minimally stateful, specially with the way discord works. This means, the entire mapping of postID to taskID that the backend has to do now might be less useful.
The goal of this issue is to conceptually clarify how the protocol would look like if everyone remembers the relevant task IDs (that are initially created for a task, i.e. the ones sent in the ACK messages), what the consequences of that would be and what it would mean in terms of trusting frontends to behave well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's description of the postID-to-taskID mapping and the task IDs sent in ACK messages. Document the current protocol, compare it with minimally stateful frontends, and capture the consequences and frontend-trust implications; done means the protocol choices and trade-offs are clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100