• 1 Post
  • 34 Comments
Joined 6 months ago
cake
Cake day: April 20th, 2026

help-circle

  • You can still move your folder from .config/librewolf/ to .librewolf/ and it will use it from there. At least, it works like that in Firefox (potentially to be removed in the future, but there’s no real reason to remove it any time soon).

    But yeah, I don’t know how that works together with KeePassXC. I mean, if it worked on LibreWolf before, then presumably moving the folder back to .librewolf/ should fix it until KeePassXC is updated…

    (And yes, the .config/ directory is specified by the XDG standard.)

    (Also, good shout about the directory being relevant. I guess, that’s also why the extension is currently broken for me, because I was a bit too eager to switch to the .config/ dir. 🙃)






  • Just to kind of confirm this:

    ls -l does not show them like hard links, but rather like soft/symbolic links.

    But when I do tail -f /path/to/file.txt on a file (to keep it open in a process) and then delete the file, I get this output in ls -l:

    3 -> '/path/to/file.txt (deleted)'
    

    The 3 seems to just be an incrementing number for each file opened by the process. And then, well, obviously the file isn’t now called “file.txt (deleted)”. That is just a name the kernel makes up when ls -l asks it what’s in that directory.

    So, presumably the kernel keeps a separate copy of that file in memory until the process closes the file or is terminated. And then exposes it through this pseudo-softlink rather than making use of hardlinks.


  • I feel like a patent would’ve run out by now. From what I’m finding online, US patents generally only last 15-20 years. They might’ve filed it in a different country, and yesterday I read of a media codec patent lasting 25 years in Brazil.
    But yeah, I believe that feature was in there before 2000 already, and they didn’t innovate on it since, which might’ve allowed for a new or renewed patent.

    It might also just be a pain to implement…


  • I’ve heard before that powders/solids are generally easier to mix than liquids, because you can just have all the active parts go when water is added.

    With liquids (or really water-based solutions), there’s already water in there, so you have to design the reactions, so that they only start when a certain water concentration is reached, which is a lot more fickle and limits you in what you can do.

    I could imagine that giving powder an advantage, but I also don’t have scientific evidence. ¯\_(ツ)_/¯



  • You’d also need some way to automatically install the right package, if a dependency is missing. And you’d need to make this work seamlessly on all distros.

    As a dev, I want my users to be able to use my software with as few clicks as possible. Ideally, just one. I’ll also accept two (download + run). For expert users, we can talk about 4 clicks, where they’d still unpack an archive after download.

    But anything beyond that, especially if they have to first troubleshoot what dependency is missing on their system, that’s just not happening. They’ll just give up and delete my program, because they don’t want to invest time into getting it to run, when they don’t even know yet, if it does what they want. I know, I would.


  • Have you considered just rewriting the cryptography parts in Rust and calling those from JavaScript? In the projects I’ve seen so far, it was always possible to move the cryptography stuff into a standalone library.
    And then with a WebAssembly wrapper, you could call that from JS: https://opensource.com/article/19/3/calling-rust-javascript

    Don’t get me wrong, I’m a big fan of Rust. I also think the WebAssembly GUI frameworks are cool. But at this point in time, I’d say they’re cool for people who don’t want to write JS.
    If you’re happy with JS, then the ecosystem of web component libraries will very likely make you more productive than you’ll be with Dioxus or Leptos.