dirname(3) is really one of the worst part of POSIX, portability-wise. Implementors can decide to either modify the passed string or return a pointer to an internal storage. The current code fails when dirname returns a pointer to an internal storage because between the strcmp call and the mkdir we go into a recursion that can modify `path'. We can't use copy either because *some* implementation of dirname would have changed that. How to escape from this hell? Take yet another copy of the path!

Use XDG-compliant paths unless ~/.telescope already exists. Provide a script to migrate to XDG-style directory for users who wish to do so.

it's been a while since we're using a lockfile to protect against multiple telescope instances.

During safe_mode the fs process shouldn't open or unlink the crashed_file.

When enabled with the -S (or --safe) flag, prevent telescope from writing files to the disk.