There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

davel ,
@davel@lemmy.ml avatar

This would just further complicate things for me. It assumes that 1) the system even has a windowing system/desktop environment or 2) all the installed software is XDG-aware. Most of the time I’m fiddling with headless environments.

exu ,

It’s not too hard to check for XDG support first and use a few hardcoded directory paths if that is unavailable.

davel ,
@davel@lemmy.ml avatar

It’s even easier to ignore it altogether, which is what I do. I don’t use “a few” non-XDG-aware things; I use lots an lots of them.

hallettj ,
@hallettj@leminal.space avatar

Are you saying that you don’t want to write your software according to the XDG spec, or that you don’t want to set the XDG env vars on your system? If it’s the second that’s fine - apps using XDG work just fine if you ignore it. If it’s the first I’d suggest reconsidering because XDG can make things much easier for users of your software who have system setups or preferences that are different from yours; and using XDG doesn’t cause problems for users who ignore it.

OP’s recommendation is aimed mostly at software authors.

davel ,
@davel@lemmy.ml avatar

I meant the second. But as to the first: I generally write in-house software for headless server environments, and my peers are going to push back if I add irrelevant XDG foo to my PR.

hallettj ,
@hallettj@leminal.space avatar

So yes, “XDG” stands for “Cross-Desktop Group” - but I don’t agree that using the spec assumes a windowing system. The base directory spec involves checking for certain environment variables for guidance on where to put files, and falling back to certain defaults if those variables are not set. It works fine on headless systems, and on systems that are not XDG-aware (I suppose that means systems that don’t set the relevant env vars).

OTOH as another commenter pointed out the base directory spec can make software work when it otherwise wouldn’t on a system that doesn’t have a typical home directory layout or permissions.

eager_eagle ,
@eager_eagle@lemmy.world avatar

The spec doesn’t make those assumptions at all, idk where that’s coming from.

I have headless machines with XDG vars configured and ones without them. XDG compliant software works in either case, but I’m less likely to use a piece of software that clutters my $HOME.

MonkderDritte , (edited )

Where did i read this… basically, the .file being hidden being a bug in the early unix filesystem, which got misused to hide configuration files.

Offenders despite XDG-variables set and with no workaround:

  • .android: hardcoded in adb and i guess something in mtp too
  • .pki: some tool/library Firefox and Chromium sometimes use.
  • .steam: yes, that

Btw, wiki.archlinux.org/title/XDG_Base_Directory

daniyeg ,

حق

mactan ,

there’s no place like 127.0.0.1

there’s no place like XDG_CONFIG_HOME.

Telorand ,

I didn’t know about this (and thankfully, haven’t written anything public). I’ve been trying to fix an install script for an OSS project that doesn’t work on immutable distros, and using the XDG Base Directory specs might just be the panacea I was looking for!

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •