Firefox 147 Will Support The XDG Base Directory Specification
50 points by MarkAssPandi
50 points by MarkAssPandi
I'm so much more excited about this than the AI stuff they've been doing.
Incidentally, people who like this would probably also like this very cool script which will help you move things into .config: https://github.com/b3nj5m1n/xdg-ninja
This being addressed fixes one of my two major pain points with Firefox. The other is keybinds being hardcoded, which has been a pain in the ass since at least 8 years ago but there's definitely an older issue. Good job Mozilla.
So much yes. Hitting ^w to try to erase a word and instead instantly closing the tab is my rage fuel.
I won't be reading the whole bug report, so I'll post my doubt about how they will handle this, given that there's information I would not like to be tracked in my git backup. One example is extensions. Where is the list of installed (and enabled ones stored)? Where do they save their own configuration? And the most important example is bookmarks. History and bookmarks are all saved in a SQLite DB, and both are confidential information. Is there anything that is innocuous enough in the browser configuration that can be safely saved in a public repository?
I'm struggling to understand what you mean here.
My understanding is that the only thing changing here is that instead of everything being shoved into ~/.mozilla, browser config will be stored (by default) in ~/.config, tabs and history in ~/.local/share, browser state files in ~/.local/state, and so on. If anything, that should make it easier to manage in a git repo.
Worst case, you can keep your tracked files somewhere else and symlink to them from the XDG directories?
That's exactly what I wanted to hear; .mozilla currently hosts a lot of files and directories that are not config files, and I wonder if they can actually find the right place for each one. And then, will they make the config safe to track? prefs.js seems to change too often, since it includes keys like lastUpdateTime.
Sorry for the rant, cause maybe I'm just letting myself go, and this feature is surely an improvement, but as you mention, it's not as easy as to move everything to .config and the article does not mention how Mozilla will implement this.
My understanding is that the only thing changing here is that instead of everything being shoved into ~/.mozilla, browser config will be stored (by default) in ~/.config, tabs and history in ~/.local/share, browser state files in ~/.local/state, and so on.
Is it, though? From cursory reading of the patch it would seem they only do ~/.cache for cache and ~/.config for everything else (i.e., the profile proper). It doesn’t seem like anyone is going to substantially change the profile structure.