Fatal edge case with socket mounted on read-only filesystems #2
Description
In my own testing on my peculiar setup, with Vencord's config location mounted on another filesystem through symlinks, if said filesystem goes read-only for one reason or another, the old socket file will linger and cause Vencord to fail to start.
I haven't looked into the exact details of what fails where in either codebase yet.
I have a hunch this could probably be tested without RO filesystems through the use of chmod, or mandatory file locks.