linuxmemes
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
In theory this issue can be solved with LD_PRELOAD trick. E.g. redirect all/most/some fopen
calls to "$HOME" to some other directory. But before I try to tackle it myself: is there already a similar solution like that?
Firefox has an issue that's been open for 20 years regarding implementing the XDG Base Directory Specification.
It's one thing when they have legacy hardcode mountains preventing a standardisation, but I really dislike developers who just disagree with the standard and take away the choice as well and justify it with some made up problems with that standard.
https://github.com/minetest/minetest/issues/864
https://bugzilla.mozilla.org/show_bug.cgi?id=735285
etc...
Archlinux Wiki even has an article about those.
https://wiki.archlinux.org/title/XDG_Base_Directory#Hardcoded
who would win?
dozens of conflicting standards on where to store files over years of poorly enforced linux development practice
vs
some symlink bois
for real tho, I discovered gnu-stow the other day and it looks like the ideal solution for this sorta stuff
my favourite part is Steam throwing in a symlink, a broken symlink, and a directory of 4 files and 7 more symlinks that all point to a more reasonable point in ~/.local/share/steam/
lol that's great. Does flatpak Steam do that too? I can't see anything from Steam directly in my home directory, and I use the flatpak version.
Protect your home, use xdg ninja
Ninja can't help if the program does not want to cooperate :(
You can use a wrapper script on PATH that launches the app in a fake home wherever you want.
Haven't used much of Linux before, can someone explain the joke?
The Windows equivilent would be instead of putting application data in the AppData folder, it throws it in Documents, My Games, or just in the home folder directly.
ah so like every fucking game and it's save files for some reason?
Better, it could be literally anywhere and there's nothing you can do about it. Also symlinks practically look like regular folders and files to most apps.
... or just imagine all of it being thrown on the Desktop (the bare user directory is rarely visited in Windows)
Hahahaha oh man I know exactly what you're talking about too 😭 hate when they do that
Yes.
Many applications have configuration files. Historically these files were placed in your home directory aka "on the floor". The variable mentioned defines a directory where these files should go. Many applications ignore this.
A non-linux version of this meme might go,
"Here is the pizza you ordered"
"Great, could you put it in my hands"
"Lol (throws pizza on floor)"
$XDG_CONFIG_HOME is an environment variable that programs can (and should) read to determine the location for storing dotfiles (config files, kind of). Not reading (or caring about) the environment variable, and not adhering to the default of /home/username/.config/ results in them ending up in the home directory.
Most software on Linux is configured to place their config files in ~/.config. Some others, like the ones in the pic, just dump them directly into your home folder.
Pain