max-mapper / max-mapper/voxel-server
Batch diffs when pushing updates to the client
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 76
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
use this to get + apply diffs
https://github.com/substack/voxel-json
Contributor guide
No contributing guide indexed for this repository
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 by reading the linked voxel-json project and tracing how voxel-server currently pushes updates to clients. Identify the existing update path and determine how diffs should be batched and applied. Done means client updates use batched diffs without losing state or synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100