Next Up
duration
2 Months
Switching from Arvo's current "depth-first" move order to "breadth-first" intends to improve the reliability of parts of the kernel, including upgrades and breach handling, by switching to chronological ordering of intra-event delivery of moves to vanes.
Next Up
duration
2-4 Months
An optimization would be to ensure that any page of memory inside the "loom" (noun memory arena) stores only cells (pairs) or atoms (numbers).
Next Up
duration
1 Month
Urbit should be able to serve websites at custom URLs efficiently to support serving websites to the old web from a single ship without needing to configure caching reverse proxies such as nginx or varnish.
Next Up
duration
2-4 Months
Experimenting with different designs for the jet dashboard could improve performance, security, and general simplicity of the codebase.
Next Up
duration
1-2 Months
A more memory-efficient implementation of `|meld` should reduce dangerous memory pressure. This would reduce maintenance burden.
Next Up
duration
1-2 Months
The "Fine" remote scry protocol will form the foundation of scalable content distribution in Urbit, by allowing many subscriber ships to read data efficiently from a publisher ship without incurring excessive load on the publisher.
Next Up
duration
1 Week
Typed paths should improve performance and developer experience, and it could unblock a typed interface to publications.
Next Up
duration
1 Month
One of the first things we can do to begin protecting against DoS is to validate packets in Vere before injecting them as Arvo events. This will make it harder for an attacker to lock up a victim's event loop, and it should be a straightforward project.