Esme Povirk @madewokherd@computerfairi.es

@zigg@queer.garden I suspect that when you oppositely shift your clocks and schedule, even though technically you're doing everything at the same time as before, you still "know" that it's nominally a different time and it has a subconscious effect. UTC avoids this (though if your local timezone were closer to UTC you'd probably get something similar when switching to it).

@zigg@queer.garden Oh we opted out in November. But instead of shifting the times in our schedule (which hasn't worked in the past), we set all our clocks to UTC and converted our schedule to that. A nice side-effect is that we avoid jet lag when crossing one timezone, and we never have to adjust a clock even then. It is more work communicating with the locals, but working with other time zones (which we do a lot) is easier.

@recursive I have to wonder how much that general realization is the result of improved communication leading to people having more/better resources they can use to figure their own shit out. -Menderbot

https://twitch.tv/madewokherd I went on a long trip but now I'm back and I'm ready to probably suck at BIT.TRIP Runner today.

@b0rk I tend to do a lot of "git branch -f" because I work with submodules which leads to not having a branch checked out.

If you do have a branch checked out, then I feel like moving it would involve some combination of branch -f + checkout, which would probably be a lot safer and more intuitive than git reset, come to think of it..

I guess you'd do something like
git checkout [flags] commit && git branch -f branch commit && git checkout branch

@b0rk Another wrinkle I've noticed to this is lists: sometimes replies show up on those as well.

I'd need to experiment but my hypothesis based on what I remember happening would be: Replies are shown if they do not start with a mention, the first mention is someone you follow (or maybe someone on the particular timeline you're looking at?), or the first mention is you.

@lioness we like to call those triggers

@b0rk I mentioned commit.verbose already. I also like core.pager=cat (don't want it to auto-page), merge.conflictStyle=diff3 (I want to see what the merge base looks like when resolving conflicts), and I like to make an alias ff for "merge --ff-only"

I didn't know about init.defaultBranch, that's useful.

@b0rk A good practice that makes #2 less likely is "git config --global commit.verbose true" and reviewing the contents of every commit you make before writing the commit message. If you notice it has things you don't want, you can close the file without a commit message (or delete the commit message if there is one), and the commit will be aborted with your index left as it was.

@lioness Put something in there that's appealing to you? I have hex-tiled ropes and a spinny chair inside to play with.

Or, our trick when learning hypnosis was to work on something unfalsifiable so we couldn't be sure it wasn't working. -iore

no spoons; didn't read

@hollie Dunno. Too long ago to figure out, I think.

@lioness But if you're not motivated by future outcomes none of that matters.

@hollie We did a daily art challenge (5 minute doodles, on a timer) for a while and it was hard. I think it helped that the goal was just "put down at least one mark and work on it for exactly 5 minutes", but we still gave up after a while because we stopped doing anything new.

Anyway, hope you have more success and above all fun making stuff. Don't be too hard on yourself.