31–40 of 72 posts
The sync feature is great, though there are many oddities with search sort order, unnecessary terminal cleanups, odd timeouts, etc. In some aspects it's a big upgrade from fzf, in some aspects it's a downgrade.
I see it also supports fish. That's been my shell for many years, it just works really well and, as far as I can tell (couldn't find a demo on their website), it doesn't add much to fish beyond syncing? Has anyone used fish + autuin? What are your thoughts? I'm curious to know if it is worth the extra tool, maybe I should just try it :)
`workspaces = true`
in your config, to limit your history to the current git repo.
Thank you very much atuin team. Can't work without atuin installed.
For zsh users who like this idea and don't want to have to worry about anything leaving the device (not to insinuate that Atuin is doing anything below board, I don't think they are) I built my own version of this for myself called raven: https://github.com/tylersaunders/raven Raven has no sync component, stores your history in a sqlite, and never tries to move data off the device. It has a similar / large overlap in…
our sync is opt-in + optional, e2e encrypted, and self-hostable. if that's not enough, you can disable all network features via a feature flag at compile time if you don't care for sync, there are a bunch of other projects doing this (and supporting several shells), eg: - mcfly: https://github.com/cantino/mcfly - resh: https://github.com/curusarn/resh
if you have someone outright cloning your entire project just to skip this opted-in privacy gap feature, it's a good indicator it's an issue to be mindful of!
I've been using Atuin for at least a year and a half, and I think it's definitely the tool I'd been looking for the most in my entire dev career. It has made me much more confident with my hazy memory. Before it I'd struggle consistently to remember most of my recent commands. bck-i was always a bit obtuse to me and I honestly never grokked it until I had Atuin wired into my workflow (hard) and ran into bck-i instead…
(dev here!) thank you so much! I love to hear things like this <3
Earlier quoted context omitted.
our sync is opt-in + optional, e2e encrypted, and self-hostable. if that's not enough, you can disable all network features via a feature flag at compile time if you don't care for sync, there are a bunch of other projects doing this (and supporting several shells), eg: - mcfly: https://github.com/cantino/mcfly - resh: https://github.com/curusarn/resh
this is my only quip with atuin, despite my endorsement in a sibling comment. this should absolutely be opted-out BY DEFAULT. not defaulted to opt-in. if you have someone outright cloning your entire project just to skip this opted-in privacy gap feature, it's a good indicator it's an issue to be mindful of!
Opt-in means that the user needs to actively decide to use the feature, it's OFF by default. That's currently the case for atuin (happy user without sync here).
Opt-out would mean the feature would be ON by default and users would need to actively decide NOT to use it.
Earlier quoted context omitted.
our sync is opt-in + optional, e2e encrypted, and self-hostable. if that's not enough, you can disable all network features via a feature flag at compile time if you don't care for sync, there are a bunch of other projects doing this (and supporting several shells), eg: - mcfly: https://github.com/cantino/mcfly - resh: https://github.com/curusarn/resh
this is my only quip with atuin, despite my endorsement in a sibling comment. this should absolutely be opted-out BY DEFAULT. not defaulted to opt-in. if you have someone outright cloning your entire project just to skip this opted-in privacy gap feature, it's a good indicator it's an issue to be mindful of!
Otherwise it’s offline, by default, right after install
Earlier quoted context omitted.
our sync is opt-in + optional, e2e encrypted, and self-hostable. if that's not enough, you can disable all network features via a feature flag at compile time if you don't care for sync, there are a bunch of other projects doing this (and supporting several shells), eg: - mcfly: https://github.com/cantino/mcfly - resh: https://github.com/curusarn/resh
this is my only quip with atuin, despite my endorsement in a sibling comment. this should absolutely be opted-out BY DEFAULT. not defaulted to opt-in. if you have someone outright cloning your entire project just to skip this opted-in privacy gap feature, it's a good indicator it's an issue to be mindful of!
For zsh users who like this idea and don't want to have to worry about anything leaving the device (not to insinuate that Atuin is doing anything below board, I don't think they are) I built my own version of this for myself called raven: https://github.com/tylersaunders/raven Raven has no sync component, stores your history in a sqlite, and never tries to move data off the device. It has a similar / large overlap in…
you could just disable sync in atuin