I like all these new use cases for SQLite, which appears to be a new platform itself
I quit my job to work full time on my open source project
61–70 of 190 posts
Re: I quit my job to work full time on my open source project
#62Off-topic: there is a “wtf” domain extension?!
We're up to ~1500 TLDs.
At this point I just auto-assume there's a domain for every word I'm interested in, though some are not open to registration or prohibitively expensive.
Re: I quit my job to work full time on my open source project
#63What should I be using shell history for? I've never wanted to go back in my history but obviously people are getting a lot of value from it.
I often hit CTRL-R to reload a services config. I press `CTRL+R`, enter `reload`, and continue to hit `CTRL+R` until the right service appears. Enter. Done. Usually way quicker, especially when switching between distros. As one calls it httpd and one apache, once it's systemd and once it's and init script, and so on.
Yes I'm using this command occasionally. While clearly the demo of Atuin (https://atuin.sh/) looks cool and more powerful than ctrl+r, I must say that ctrl+r has always been enough to me.
Re: I quit my job to work full time on my open source project
#64What should I be using shell history for? I've never wanted to go back in my history but obviously people are getting a lot of value from it.
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 use [Shuttle](https://fitztrev.github.io/shuttle/) for that ssh issue which often comes in handy. Should solve for most of those CLI command issues.
Re: I quit my job to work full time on my open source project
#65Earlier quoted context omitted.
You don't need any of it. History is useful enough to exist as a feature, I up-arrow routinely, but it doesn't actually matter when it doesn't exist. I find the idea of going out of your way to preserve and migrate years of shell history and make it searchable in a db about like: You have a problem that water is flooding your kitchen floor. Normally you deal with a spill with a mop or towels. There is now too much wa…
History can also contain potentially sensitive things like hostnames of non-public systems, usernames, filenames, URLs. I would not want that stuff to hang around indefinitely.
This is one thing that atuin announced to solve: ignore patterns, keys, passwords. From the announcement I got that it's going to be far more useful than HISTIGNORE. Both out of the box and in abilities.
Re: I quit my job to work full time on my open source project
#66What should I be using shell history for? I've never wanted to go back in my history but obviously people are getting a lot of value from it.
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.
Re: I quit my job to work full time on my open source project
#67I keep my shell history in sqlite database since 2017. Around 120k records at this point. Never synced history from the work laptops. Only personal history. In 2017 wrote my own bash script (later optimized for zsh) to just record everything in sqlite with hooks on prompt. [1] I mostly work right now on Mac, don't need to support Linux anymore, so wrote an app for Mac, that syncs the history over iCloud, and has a GU…
Do you know any way to accomplish the same thing but keeping the history in plaintext? Would love to still be able to run SQL over it.
Write to two places in the hook?
Re: I quit my job to work full time on my open source project
#68What 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.
> If you are running servers passing passwords as command line arguments in that device, they have all that. I make a point out of never doing that. It’s way too easy to accidentally expose things. For instance, doing a live demo with an audience, and using Ctrl-R out of muscle memory? Suddenly you flashed your password in front of everyone. Generally, I’d recommend using a tool like Unix `pass` or your default OS ke…
This is a good approach. Thx for sharing.
Re: I quit my job to work full time on my open source project
#69This 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. I can think of several apps that macOS users are paying for, such as Bartender, Alfred, or MailMate. Clearly, there's a market for utilities, but only with scarcity.
Re: I quit my job to work full time on my open source project
#70I'm curious about the calculus involved in dedicating oneself to a full-time open-source project. Could someone with prior experience share insights on generating income or potential future exits solely through open-source contributions?
Freelancers typically make money by coding up solutions, leaning heavily on open-source, for individual clients (as opposed to mass-market software) or other forms of consulting. Sometimes they will become the caretaker of one or more "projects" that multiple clients rely on. That maintenance is billable. It's not uncommon for contract programmers to become small businesses. If they think they can get support from th…
[dead]