Live data from Hacker News

I quit my job to work full time on my open source project

ellie.wtf

141–150 of 190 posts

Re: I quit my job to work full time on my open source project

#141
post #44

Earlier quoted context omitted.

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.

You can tell your shell to ignore commands started with a space HISTCONTROL=ignorespace Or you can use HISTIGNORE to always ignore specific patterns.

You can also use

    HISTCONTROL=ignoreboth
to use both ignorespace and ignoredups

Re: I quit my job to work full time on my open source project

#142
Eventually I suspect someone will abuse this for the free (and encrypted) storage, and then they'll have to fight that battle, which won't be fun, and likely end up charging. Probably should start charging for storage sooner rather than later, and just allow self hosting free.

Re: I quit my job to work full time on my open source project

#143
post #142

Eventually I suspect someone will abuse this for the free (and encrypted) storage, and then they'll have to fight that battle, which won't be fun, and likely end up charging. Probably should start charging for storage sooner rather than later, and just allow self hosting free.

> which won't be fun

Says who?

Re: I quit my job to work full time on my open source project

#144
I have some local setup replicating what Atuin does, but I'm realizing I don't use it at all even though I thought it'd be useful, and I don't use my shell history much overall. I have an alias "aled" to edit my aliases quickly, so it's easy for me to add new ones, and that's where I put the commands I want to use regularly, or even the ones I'd like to be able to find if I ever need them again in years. It's easier to add documentation in a .zshrc than in a shell history in any case.

Global aliases (which you can use anywhere, not only at the beginning) are also nice to compose aliases with each other.

Re: I quit my job to work full time on my open source project

#145
im one of those who disable shell history persistance, since i first found peoples user folders on misconfigured apache servers in the 90s, complete with .bash_history containing passwords and hostnames.

dont recall i needed to dig up old commands typed, like ever.

i dont think this one is for me, but good luck!

Re: I quit my job to work full time on my open source project

#146

This 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…

In terms of making money, I feel like the sweet spot might be a closed source app with a rich open source ecosystem around it, such as Raycast or Obsidian Notes.

The apps themselves are closed source and making money, but the extensions and add-on functionalities are mostly open source.

Re: I quit my job to work full time on my open source project

#147
post #45

Earlier quoted context omitted.

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)

Shell history is wiped out after user logged out for a reason. More details are here - https://www.securityhq.com/blog/security-101-dont-bash-your-... .

Please read the page you linked; it’s flushed to a file, not wiped.

Re: I quit my job to work full time on my open source project

#150

I'm curious to hear what people's usecases are for retaining long shell history. For myself, I never really use it beyond the current work day (up arrow)

for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.
Post reply on HN