• 1 Post
  • 43 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. 🙃)





  • Yeah? You should still make a decision. If you want it possible to watch, star and fork the repo from any of the sub-pages, then that stuff has to live in that top ribbon.

    But then you shouldn’t duplicate it into the Code sub-page. I’d work with split buttons, where you can look at who starred and you can add your own star, all from the same UI element. It would not even take up more space, since they do already display the count in the top ribbon as well.

    Apparently this is how Codeberg does it (see e.g. this repo), so this might be where I have the idea from…


  • I mean, yeah, it can make sense to duplicate information. That screenshot isn’t supposed to say that all of these should be deduplicated.
    But you really gotta be cautious with duplication, because it makes everything else harder to find. And I would absolutely argue that GitHub has crossed the line where they duplicate too much, across the board. It feels like design-by-committee.

    This is entirely anecdotal, but what really dumbfounded me while annotating that screenshot, is that I never actually read the links in that “About” section.
    I’ve seen this page probably a thousand times already, but I had no idea that there’s an “Activity” link there, which actually seems like it could be useful. Nor a link to the README, to the CONTRIBUTING.md or for “Custom Properties” (whatever that is).
    I had no idea how to report a repo until now, even though the link is apparently always on screen.

    There’s just so much info there, and it’s presented like read-only info, not like navigation links, so I always just skipped over the lines that don’t have numbers in them. I also genuinely never tried clicking any of these lines before…



  • 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. ¯\_(ツ)_/¯


  • The section “4. What editing does to the mark” talks about that. Probably best to look at that illustration again, but basically those edits would interrupt consecutive runs of detectable text, but if a run is long enough, it can still be detected with statistical significance.

    So, it doesn’t have to check the ‘color’ of the words from start to end uninterrupted, but rather can also detect color sequences in the middle of the text.











  • I think, something to be aware of is that it’s not just shade. It’s not just cooler below the tree. Trees also store and evaporate water, which cools the whole area. This summarizes the cooling effect quite well:

    Tree implementation reduces peak monthly temperatures to below 26 °C in 83% of the cities. Trees can lower pedestrian-level temperatures by up to 12 °C through large radiation blockage and transpiration.

    https://www.nature.com/articles/s43247-024-01908-4

    And well, ultimately if we accept that climate change is a thing, planting trees now is the cheapest investment we can make to combat the heatwaves in 10+ years from now.
    It will reduce heat deaths. It will reduce AC costs of everyone living there. And it will mean that the city doesn’t lose out on taxes from people choosing to stay inside during a heat wave.