feat: asset support
What this would mean is making it possible to add images/assets via a patch. Right now we're only able to change code, but adding asset support would mean that we would diff the assets as well (between the patch and the release) and send any changed assets (images, icons, etc.) with the patch to the devices in the field. This requires some infrastructure work, mostly in preparing for now arbitrary-sized patches, which means we need to improve our download mechanisms on device (which are currently very simple because code-only patches are generally tiny). As of Jan 2025, this is very close to the top of our list, but still not scheduled.
Posted by eseidel on Apr 19, 2023, 5:28 AM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
feat: asset support
What this would mean is making it possible to add images/assets via a patch. Right now we're only able to change code, but adding asset support would mean that we would diff the assets as well (between the patch and the release) and send any changed assets (images, icons, etc.) with the patch to the devices in the field. This requires some infrastructure work, mostly in preparing for now arbitrary-sized patches, which means we need to improve our download mechanisms on device (which are currently very simple because code-only patches are generally tiny). As of Jan 2025, this is very close to the top of our list, but still not scheduled.
Comments (0)
No comments yet. Start the discussion.