all 11 comments

sorted by: hot top controversial new old
[–] 22 points 11 months ago* (6 children)

It's important to note that apparently there's no automatic migration path and this will be only used for new profiles, so you have to migrate manually.

  • source
  • hideshow 6 child comments
  • [–] 10 points 11 months ago (4 children)

    In practice that should mean running mv ~/.mozilla ~/.config/mozilla.
    Of course the old directory will still be detected and used if present, probably for a long time to come.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 11 points 11 months ago* (3 children)

    they are not following the spec if this is the solution.

    • data files (like extensions, sessions, etc) need to go in XDG_DATA_HOME.

    • config files (user preferences) need to go in XDG_CONFIG_HOME.

    • cache files need to go in XDG_CACHE_HOME.

    • log files need to go in XDG_STATE_HOME.

    also hopefully they do check the variables and not just hardcoded ~/.config, ~/.local/share, etc

  • source
  • parent
  • hideshow 3 child comments
  • [–] 8 points 11 months ago (2 children)

    I think they mostly are.
    Cache is already in .cache/mozilla, so usually there is no change hence I didn't mention it. They did move the cache to the XDG_CACHE_HOME by default. And yes they are using the XDG variables including the recommended fallback values.

    The line between data and config has always been blurred, Most data in the browser is "data" until a user overrides it. Even extension files presence is linked with their configured state of being installed.
    For log files I'm not sure anyone follows that. Besides firefox barely has any plain logs, I think having those in the profile is fine.
    Currently it's all in XDG_CONFIG_HOME

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 11 months ago (1 child)

    Always good to know that after sitting on it for 2 decades, shipping some half-assed shit was the best they could do.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 11 months ago

    The implications would be massive and I do not think most power users would benefit from it being broken up like that. Being able to backup or sync your entire Firefox profile by copying one directory is quite useful.

  • source
  • parent
  • [–] 14 points 11 months ago

    Good gawd, finally.

  • source
  • [–] 11 points 11 months ago

    https://specifications.freedesktop.org/basedir/latest/

    The XDG Base Directory Specification is based on the following concepts:

    There is a single base directory relative to which user-specific data files should be written. This directory is defined by the environment variable $XDG_DATA_HOME.

    There is a single base directory relative to which user-specific configuration files should be written. This directory is defined by the environment variable $XDG_CONFIG_HOME.

    There is a single base directory relative to which user-specific state data should be written. This directory is defined by the environment variable $XDG_STATE_HOME.

    There is a single base directory relative to which user-specific executable files may be written.

    There is a set of preference ordered base directories relative to which data files should be searched. This set of directories is defined by the environment variable $XDG_DATA_DIRS.

    There is a set of preference ordered base directories relative to which configuration files should be searched. This set of directories is defined by the environment variable $XDG_CONFIG_DIRS.

    There is a single base directory relative to which user-specific non-essential (cached) data should be written. This directory is defined by the environment variable $XDG_CACHE_HOME.

    There is a single base directory relative to which user-specific runtime files and other file objects should be placed. This directory is defined by the environment variable $XDG_RUNTIME_DIR.

  • source
  • [–] 0 points 11 months ago (1 child)

    I tried it and moved the directory. Results:

    • Firefox opens, settings from the profile are still there.
    • Empty ./mozilla/extensions directories are recreated on startup.
    • Firefox cannot show any websites anymore.

    Yikes.

  • source
  • hideshow 1 child comment
  • 14 comments in c/firefox@lemmy.ml view that post
    [–] [S] 23 points 11 months ago (1 child)

    Though, it looks like it won't auto-migrate. So it'll stay directly in your home dir unless you reinstall or move it yourself.

    https://hg-edge.mozilla.org/integration/autoland/diff/8a6d6c094cb5a842d415c60bb8395db03b36e531/xpcom/io/nsAppFileLocationProvider.cpp#l1.73

  • source
  • hideshow 1 child comment
  • [–] 14 points 11 months ago*

    Wow! Now that is something that's nice to see!

    Instead of "we've inserted AI into your AI so that you can run more AI while you're running AI".

  • source
  • [–] 10 points 11 months ago (2 children)

    Heck yes!! One of three remaining dotfiles in my ~ (the other ones are .ssh and .XCompose, I suspect I can get rid of the latter nowadays too). Can't wait for this to land in librewolf.

  • source
  • hideshow 2 child comments
  • [–] 1 point 11 months ago (1 child)

    Depending on the input method you use, you might be able to move your .XCompose file to ~/.config/X11/xcompose. Don’t let the X11 in there confuse you, I am using this with fcitx5 under Wayland.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 11 months ago

    I tried this a couple times already: once when initially moving most of my stuff to XDG, the second a couple years ago. Both times most apps followed it, but there were some that didn't (don't remember the details - maybe it was GTK related). I didn't bother to investigate more, since it seemed like a chore. I guess I'll try again when I get some free time.

  • source
  • parent
  • [–] 7 points 11 months ago (1 child)

    This is super nice. Still a few left out but one less is good. Anyone looking to clean up their home directory can use xdj ninja .

  • source
  • hideshow 1 child comment
  • [–] 4 points 11 months ago (1 child)

    From the bug report:

    [...] will require moving some config & data files from ~/.phoenix to probably $XDG_CONFIG_HOME/phoenix and [...]

    According to Wikipedia, the browser was already renamed to "Firefox" when that bug report was opened, but still wild to see that even back then, they already had some technical debt for the name of that directory.

    Unfortunate that they did not go straight from ~/.phoenix to $XDG_CONFIG_HOME/mozilla, but hard to say, if that was as obvious of a choice back then...

  • source
  • hideshow 1 child comment
  • [–] 3 points 11 months ago (2 children)

    To be honest, I don't know why this was an issue at all. I speak for myself, when I say it never actually bothered me much, as long as it is hidden and in my home directory. I will change directory to .config/firefox (or whatever is the new default), but I don't know if that makes a difference at all.

  • source
  • hideshow 2 child comments
  • [–] 15 points 11 months ago (1 child)

    It's not the biggest pain in the world, but having all state and config in predictable folders is wonderful for backups. You don't have to copy each random dotfile in your home directory, you just have a well-defined folder and can back up everything at once.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 11 months ago

    Yeah, I guess that's a good point. I do my (with custom scripts) backup and have to add additional directories like Firefox profile manually to the list. I guess breaking up the cache and temporary files from the configuration would be a nice bonus. I didn't think of this before posting my reply.

    +1 I changed my mind.

  • source
  • parent
  • [–] 2 points 11 months ago