What is the security of this? 1. If someone steals my laptop & breaks in, can they get access to all my history 2. After breaking, if they run `atuin key` will get them the key for my history which they can use from any device (if they know the userid) 3. If you are running servers passing passwords as command line arguments in that device, they have all that.
What do you have in the history that’s sensitive? Keys, passwords should not be in shell history anyways (e.g. I delete them from bash history if I enter by mistake)
I quit my job to work full time on my open source project
71–80 of 190 posts
Re: I quit my job to work full time on my open source project
#72Earlier quoted context omitted.
Here are some of my often use cases: Long kunernetes commands, or ssh into an ip you don’t have remembered, curl commands when testing an api. Anything on the CLI that is long and either hard to remember or just annoying to type.
I tend to write scripts or docs when things are annoying and hard to remember. shell history is usually littered with sensitive stuff, I usually go way out of my way to prevent my machines from saving any of it, but to each their own.
Atuin is trying to solve this one too :)
By default it won't save history containing AWS credentials, slack credentials, etc. The list of things to ignore is configurable with regex
While it's not difficult to avoid putting credentials into your shell, ik most people will just paste things in that perhaps they should not
Re: I quit my job to work full time on my open source project
#73I love the idea of Atuin but it's just way too slow with large history files. I've synced my history on my own for the past decade and have like 170k lines and the history search the ctrl-r search just crawls. I don't need most of the history, but there's 0 chance in hell I'm auditing that many lines to decide what I need and what I don't need.
hey! what issues were you having here? slow to open or slow to search?
we have a whole bunch of people with way more than 170k lines, so that shouldn't be happening :/
Re: I quit my job to work full time on my open source project
#74Happy to answer any questions :)
Re: I quit my job to work full time on my open source project
#75Atuin: https://atuin.sh/ Note: I am a user, and not the author (Ellie Huxtable)
I’m an atuin user too, and think it’s great. It’s a significant improvement over the bash history configurations (incantations?) I used previously. Where atuin really shines is in keeping a single unified history across multiple shell windows, which my incantations could never get to work correctly on all the platforms I use (zsh/bash on OSX/Linux/msys/cygwin/babun). I’ve also enjoyed running SQL queries on my atuin-…
> I’ve also enjoyed running SQL queries on my atuin-history to learn more about my own workflows to see where I can optimize.
if you could share more about what you found useful there, that would be amazing
Re: I quit my job to work full time on my open source project
#76Re: I quit my job to work full time on my open source project
#77I think it's great to see more women moving into full time open source careers. We don't have many!
Re: I quit my job to work full time on my open source project
#78Is it possible to sync existing shell history? Fish history, precisely.
- zsh - bash - fish - nushell
Re: I quit my job to work full time on my open source project
#79Anyone know what were the big inflection points in 2022 and 2023 for star growth?
2023's one may be HN: https://news.ycombinator.com/item?id=35839470 Ellie's Show HN was in 2021: https://news.ycombinator.com/item?id=27079862 2022's must be somewhere else.
Atuin tends to get shared more readily on Mastodon/Twitter than it does HN, which explains everything other than the 2023-HN-spike. We've also been on a few podcasts and newsletters
Re: I quit my job to work full time on my open source project
#80This is the dream for many of us, but I hope she comes up with a good business model that doesn't rely on the goodwill of people (e.g., open core) because FOSS is terrible for earning money. The reason is that FOSS is essentially part of the commons, but without being maintained by taxes. In general, people just want free stuff, companies rarely pay for support, and SaaS providers will steal your business if they can…
https://opensource.guide/getting-paid/
https://www.state.gov/supporting-critical-open-source-techno...
https://new.nsf.gov/tip/updates/nsf-invests-over-26m-open-so...