

Oh, I think, you’re right. It was a patch by openSUSE at first, but then they integrated it in about:config.


Oh, I think, you’re right. It was a patch by openSUSE at first, but then they integrated it in about:config.


Just saw this while flicking through the changelog and hadn’t heard of this when it was released. Perhaps too niche to report on for news pages. So, I figured, I’d post here. ¯\_(ツ)_/¯


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 could rant a lot about the GitHub UX, so here’s just the fairly obvious stuff on the repository page:

Red arrows mean duplicated information or duplicated navigational elements.
Green arrow means why the fuck do I have to tell our customers to click a random link in the middle of bumfuck nowhere, in order to download our software?


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.


Yeah, they can’t easily rotate keys, because the text can’t tell you which key was used.
They could switch to a new key e.g. every month and then just check every previous key during detection. But that would slowly increase the likelihood of false positives, so no idea if that’s a good idea either.


Funnily enough, Firefox basically has it, with its Tracking Protection. The vast majority of ads use tracking, so get blocked by it.


With “refine”, I would guess they’re talking about refining a task, so breaking it down into smaller, more concrete/actionable tasks.
Because that’s usually meant in dev lingo, and because the other possible meaning of improving already-written code/docs is kind of already covered by “review”.


I believe, the right term to call that, is abuse of their dominance in one market to force their way into another…


I believe, they chose a different behaviour for RMB, because otherwise you can’t right-click the background anymore to create subfolders etc., when you’re looking at a folder with lots of files/subfolders inside.
I don’t know, if Windows has a solution for this. I certainly wouldn’t be surprised, if they don’t.


Looks like it’s this one: https://makertube.net/c/veronicaexplains/videos
I used SepiaSearch to find her videos: https://sepiasearch.org/
(Which did actually lead me to her old tinkerbetter.tube instance at first, but there it has a deprecation notice saying that she’s now on makertube.net.)


I also really wouldn’t get my hopes up that it’s particularly different from GTA 5. The setting is still just realism, so they can’t change much in terms of gameplay or art style, not even the storytelling can go too far off the rails.
The graphics and world simulation will likely be more, uh, realistic, but you’d really need to get a lot of enjoyment out of fine details for that to make much of a difference…


If we’re talking just text content with not really any interactive elements (beyond a navigation menu), then look into “static site generators”.
They allow you to write your blog posts or whatever in Markdown. You can pick out a theme. And then they’ll generate HTML+CSS+JS, which you can push onto a web server.


Yeah, it’s happening for me, too. There’s a hidden debug menu in the Fennec settings and when I enable that, there’s a “Nimbus Experiments” menu where I can turn on the tab groups.
But in the tab group UI, it says “Beta”. Not sure, if it also does that on official Firefox Stable.
My best guess is that Mozilla was A-B-testing tab groups on Nightly or Beta, which is why this Nimbus Experiment exist. And now their backend is getting confused by Fennec.
Maybe there’s some build flag to permanently enable the tab groups, which Fennec is missing in their own build, and so the backend sees “unsigned build v153” and is really confused why that doesn’t have tab groups active yet or something?
Edit: For what it’s worth, I found this bug ticket for Fennec: https://gitlab.com/relan/fennecbuild/-/work_items?show=eyJpaWQiOiIxOTUiLCJmdWxsX3BhdGgiOiJyZWxhbi9mZW5uZWNidWlsZCIsImlkIjoxOTU4MTE0NzF9


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.


Trees are quite effective at slowing down winds, so planting more trees than before is exactly the right response. 👍


I use “Air Hockey Saloon” by Chris Zabriskie. Certainly more on the gentle side.
https://archive.org/details/2009_-_2014-16921/Chris_Zabriskie_-_08_-_Air_Hockey_Saloon.mp3
(It’s under Creative Commons: https://chriszabriskie.com/vendaface/ )
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. 🙃)