Turtle. A hard-fork of atuin, focusing on a more minimal feature set http://git.foss-syndicate.org/bpeetz/forks/atuin/atom/atuin-client/src/record?h=main 2024-04-18T15:41:28Z 2024-04-18T15:41:28Z Ellie Huxtable ellie@elliehuxtable.com 2024-04-18T15:41:28Z urn:sha1:95cc472037fcb3207b510e67f1a44af4e2a2cae9 I'd like to tidy up the root a little, and it's nice to have all the rust crates in one place 2024-04-17T13:06:05Z Ellie Huxtable ellie@elliehuxtable.com 2024-04-17T13:06:05Z urn:sha1:cb19925011d889c513e1bbedc446e399597e38a0 1. Start on a home page, can sort onboarding/etc from there 2. Introduce zustand for state management. It's nice! Did a production build and clicked around for a while. Memory usage seems nice and chill. 2024-04-05T14:51:57Z Yaroslav Halchenko debian@onerussian.com 2024-04-05T14:51:57Z urn:sha1:28b0b490f93fe9f7964d0593b9ba600f4b24663e * Add github action to codespell main on push and PRs * Add rudimentary codespell config * ignore crate, inbetween etc * [DATALAD RUNCMD] run codespell throughout fixing typo automagically but ignoring the failure due to ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w || :", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * [DATALAD RUNCMD] Do interactive fixing of leftover ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w -i 3 -C 2", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ 2024-02-12T09:25:06Z Eric Long i@hack3r.moe 2024-02-12T09:25:06Z urn:sha1:5a805dc22c99050db0a54f35e660516c57fa4b94 Low-end devices like RISC-V SBCs are sometimes too slow to initialize SQLite in 0.1s. Option to specify a higher value allows check to pass on such devices with relaxed restrictions. 2024-02-08T13:34:41Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-08T13:34:41Z urn:sha1:8460210202af4e48ea55c997bf2739a6f0570e4a Replace lots of logging with some progress bars. This looks much nicer I'd like to move it out of the atuin-client crate and into the atuin crate. But first, I want to decouple a lot of the record moving, so it can wait until that's done. 2024-02-04T20:06:47Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-04T20:06:47Z urn:sha1:3ff2e2552f5b4db9c8b8e127ff833873902258c0 2024-02-02T18:01:09Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-02T15:18:50Z urn:sha1:374255dd5856465b30d4c90d5882b150fa6c47de This allows the user to 1. Specify that they want to sync, but ONLY pull new data 2. Specify that they wish to force pull, which will wipe the local store and download it from the remote With the other set of changes, this allows the user to perform sufficient maintenance to recovery from most errors I can think of right now. 2024-02-02T18:01:09Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-02T14:27:23Z urn:sha1:754f17ddb4969973b9332a5324af42886e503c0f This command will delete all records from the local store that cannot be decrypted with the current key. If a verify fails before running this, it should pass _after_ running it. Required afterwards: - A `push --force`, to allow ensuring the remote store equals the local store (deletions have now occured!) - A `pull --force`, as once remote has been forced then local needs the same Nice to have: - Provide "old" keys to purge, in case the are not lost. Or maybe rekey. 2024-02-02T18:01:09Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-02T14:05:13Z urn:sha1:212dc928c9c4cc8b03b9cad83f9b8b81044c2b02 This ensures that the local store can be decrypted with the current in-use key. If it cannot, we can go on to perform maintenance operations and get back into a happy state. 2024-02-01T15:00:46Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-01T15:00:46Z urn:sha1:a6f1fe2c10ea9f7bb08d2344df62fee4a996cd69 * feat: add record re-encrypting * automatically re-encrypt store when logging in with a different key * fix * actually save the new key lmao * add rekey * save new key * decode bip key * "add test for sqlite store re encrypt"