Live data from Hacker News

Dotfiles feel too personal to share

hamatti.org

41–50 of 153 posts

Re: Dotfiles feel too personal to share

#42

My dots are open to anyone who cares to view my GitHub. I do tend to keep employer specific aliases/stuff in an `.employer.zsh` file that is sourced by my main `.zshrc`. But my NeoVim config is completely open for inspection. I'm not doing anything all that extraordinary though. I don't share my dots on Reddit simply because I don't feel like using my real identity on that platform. When it comes to consuming the dot…

That actually looks pretty cool. Might have to play around a bit with Caelestia as well.

Re: Dotfiles feel too personal to share

#43
post #29

Too personal to share, but maybe too personal and important to share even with the members of the cloudy cartel, i.e. the Providers. Is exactly why I wrote myba that does full contents and paths encryption before syncing with the lapsable remotes ... https://kernc.github.io/myba/ Some things are better public. Some are not ...

this reminds me of public repos of pass [1] i've seen in the wild

same issue of intimacy, the paths aren't encrypted.

[1] https://www.passwordstore.org/

Re: Dotfiles feel too personal to share

#46
I have like 7500 stars on my dotfiles over the last 15 years or so; it's definitely weird. It's kind of a different open source project entirely; the goal isn't really to make good software... it's to make good software for me. Most of the time in open source those overlap completely, but with dotfiles I'll get pulls that make sense, that can be helpful, but... at the end of the day they're my dotfiles and I don't really make large changes to them anymore. It's just a lot different from my other projects I manage.

That said, mine also started before things like Oh My Zsh popped up, which are better frameworks to share and collaborate on these things. I think frameworks like that are great, and I think seeing someone's more "intimate" dotfiles is helpful, too- you get a look at how someone sets up their environment, which tends to be private unless you're doing a lot of pair programming. So yeah, just interesting all around.

Re: Dotfiles feel too personal to share

#48
I've been keeping my personal .dotfiles publically for the past decade. https://github.com/cmcdragonkai/.dotfiles-nixos.

But I do agree that secrets need to be handled carefully. Look at my list of `.gitignore`! But (I'm biased of course) I would recommend using Polykey to manage your secrets instead leaving any trace of things on disk.

Re: Dotfiles feel too personal to share

#49

The first UNIX account I ever got was on a BSD, and the first thing I saw in the first file I learned how to open was: # A righteous umask umask 22 I'll never forget those lines because they seemed so mysterious and cool. And they informed my philosophy on how the internet should be. People should be able to see other people's stuff by default. It's nice for us to be able to learn from one another. It's harder to rel…

Not just the internet but communities too. High trust societies are great to live in, digitally and physically. Leave the doors unlocked, leave keys in the ignition, leave valuables on the table when you walk away.

But high trust societies only work when the price of ongoing admission is not violating that trust.

When you accept/tolerate/expect the violation of trust the doors lock.

Re: Dotfiles feel too personal to share

#50
post #23

I think the key is that dotfiles are a different genre of (code) writing than production code, with different investment, different motivations, different pain points and histories, and a sensitivity to the author that's not required when analyzing production code. You're looking into someone's daily writings, not their polished releases. I think the fear is scrutiny, rejection, mockery for something that clearly wor…

I'm sure I have stupid and weird stuff in my dotfiles. At one point I had bash set up so if I typed something like "gi tlog" it would fix it for me; this is obviously not something that everybody needs because it's due to my idiosyncratic typing-too-fast.

I've been using Unix systems since last century; my standard way to do a find-and-replace in a file is still 'perl -pi -e s/foo/bar/ filename.txt'; I've been writing that for 25 years and I'm unlike to stop any time soon unless perl stops working. I'm sure there's a better way to do this, but :shrug:?

Post reply on HN