Jake Stanger

The alternative to this for anybody stumbling across this who doesn't want to edit code, is to create a symlink at `~/.config/discord` targeting `~/snap/discord/current/.config/discord`

Dura doesn't currently store any metadata about the branches it creates,so yeah currently users are stuck working with the generated hash-based branch names. I think we're best avoiding the last...

Perhaps there could be a system similar to log rotation, 'branch rotation'. Dura could create `dura-0`, `dura-1` `dura-2`, ..., and rotate those after a period of time or number of...

I'd agree it's clear the ring-buffer idea isn't sufficient by itself. I was trying to come up with answers to the ring-buffer questions and basically re-invented your idea of hot/cold...

Thanks for taking the time to draw those out, that does help a lot. Sorry it's taken me a while to get back to it. So let's say someone's been...

I've been exclusively working on it & building it on Linux (Arch) so I know it does work. I've not had to do anything except `cargo build`. You should definitely...

> PS: Hence the fact that I'm not reacting to "_NixOS and it's weird filesystem structure._", the idea here is to make sure that the shipped software works for every...

There's certainly no harm in setting up another action to produce a `musl` build, it sounds pretty easy to do so I'm on board. Their action file has a step...

> Todo for later: Check if running dura serve twice doesn't make issues. It may at the moment, there's some discussion/ideas about preventing it in #2. --- I like the...

I'm thinking `checkout` quite literally just checks out the commit/branch (perhaps in a detached state if it's a commit, I can't remember how Git works...) and doesn't affect your main...