Paul Butler
Paul Butler
In order to allow something like a Kanban board, we would want to have multiple data structures that items could be moved between. The best way to accomplish this would...
Aper should have a `Tree` data structure that would represent nestable data structures, such as: - Elements in a vector graphic that supports nested grouping (e.g. SVG, geojson) - Comments...
This is something I've wanted to do to reduce cold start times when we know we have the image locally, and has also been requested by @mycaddev via Discord.
Previously, all DNS records for a given cluster went to the same subject. The cli fetches DNS records using `DeliverPolicy::LastPerSubject`, so it only gets the last message sent to a...
We currently generate NATS subjects from message contents, but we don't verify that a message was received at the appropriate subject, so a connected client with access to publish on...
Rather than requiring that developers use NATS directly, which may be unfamiliar, and construct their own messages, which loses the benefits of typing, we could provide a TypeScript API that...
Open issues potentially resulting in schema changes: - [ ] #128 - [x] #132 - [x] #129 - [ ] #137 - [ ] #117 - [x] #139 - [...
The Ava suite had a test that tested certificate generation, the agent, and the proxy all working together. The Rust test should have this as well.
We should standardize subjects as follows: `cluster..*`: cluster-level messages `cluster..drone..*`: drone-level messages `cluster..drone..backend..*` backend-level messages This allows us to permission pub/sub to various levels: cluster-wide, drone-wide, backend-only. It also means...