Conversely, ads are now one of the primary vectors how malware is distributed, so you still have at least 3 viruses on your computer. 👍

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. 🙃)

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

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.

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?

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”.

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.