Wait, if I run flatpak list --system --columns=application, it looks like all my Flatpaks are system Flatpaks. Running flatpak list --user --columns=application shoulds just a couple of platform packages. What am I missing out on? What is this needed for:

like forcing crappy electron apps to use wayland

(Either way, thanks for writing up a detailed guide!)

I think you might be looking for tab groups? Which, incidentally, are also coming.

@phanpy@hachyderm.io's "catch-up" feature is basically that.

Keep in mind that having an extensively customised setup makes you more fingerprintable - just the fact that some things are not visible to a website makes you unique. Generally, most of the defaults will be best for everybody - especially when it comes to options that are not exposed in the UI (i.e. through about:config).

What could be interesting for you is just running uBlock Origin and have it block all JavaScript by default. That'll block most of the scripts that potentially do tracking (and that Firefox doesn't block natively, e.g. because they also provide functionality), and you can relatively easily enable them on a per-site and per-script basis.

Almost my entire career I've worked in open source, so it's very easy to see what my technical work looks like. No one has ever looked at it.

When I have been on the other side, I have looked at the GitHub "portfolio" of junior applicants, but TBH, it didn't bring me much. There will always be lots of opportunities for improvements in those examples, but that's the point - I expect them to improve on the job.

More experienced developers will almost never have significant work on GitHub, and if they do, it's not a "portfolio", but just their past work.

Maybe learn to take screenshots first? :P

@janvlug@mastodon.social heeft twee lijstjes: Tweede Kamerleden en politieke partijen. Volgens mij zijn ze een beetje verouderd, maar wellicht dat hij ze binnenkort bijwerkt - volgens mij is hij wel op de hoogte.

Appears to be a mistake, but needs gorhill to appeal to make the reviewer aware of the mistake and to be able to fix it, which he doesn't feel like doing because he thinks it's unlikely to have been a mistake.

Update: now reversed, but gorhill removed it himself just to not have to deal with the review process and the possibility of human error anymore.

This sounds exactly like the type of nontechnical nonsense they're complaining about: attacking a strawman ("they're trying to prevent people from refactoring C code and making them rewrite everything in the current fancy language") even after explicitly calling out that that was not going to happen ("and to reiterate, no one is trying force anyone else to learn Rust nor prevent refactorings of C code").

They've committed to not changing any displayed text ("strings"), so that translators have time to translate everything.

I'll always upvote StreetComplete.

If TypeScript still is a fad at this point, his definition of fad is far lengthier than mine is.

I'm fairly sure TypeScript will remain in popular use longer than whatever project you're working on 😅