Applications should use this directory for communication and synchronization purposes and should not place larger files in it, since it might reside in runtime memory and cannot necessarily be swapped out to disk.
An assumption was made early in the project that this could be used for a limited amount of runtime state, due to the then upstream of this project doing it, as well as other major projects like systemd doing it as well.
Since there is nothing preventing the use of SharePath, and it has generally a more stable path format, it should be used here instead.
For $XDG_RUNTIME_DIR, according to the spec:
> Applications should use this directory for communication and synchronization purposes and should not place larger files in it, since it might reside in runtime memory and cannot necessarily be swapped out to disk.
An assumption was made early in the project that this could be used for a limited amount of runtime state, due to the then upstream of this project doing it, as well as other major projects like systemd doing it as well.
Since there is nothing preventing the use of `SharePath`, and it has generally a more stable path format, it should be used here instead.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For $XDG_RUNTIME_DIR, according to the spec:
An assumption was made early in the project that this could be used for a limited amount of runtime state, due to the then upstream of this project doing it, as well as other major projects like systemd doing it as well.
Since there is nothing preventing the use of
SharePath, and it has generally a more stable path format, it should be used here instead.