But what if it's the liquid that remains after you've washed up?

•••

Ah yeah, that was dumb, I should've specified that you can do that, if you're looking at the post in the Lemmy web-UI.

The button would take you to the webpage of the original post, so before it got federated. Images often load when I do that, because my instance has an image proxy that's sometimes at fault for loading errors. If I'm interpreting your screenshot correctly, slrpnk.net has an image proxy, too.

Maybe your app has a different button to open the original post, or a button to open the Lemmy webpage for the post in your browser and then you can click the rainbow pentagon there...

Click the rainbow-colored pentagon...

I do enjoy how many number sets are referred to as "normal numbers":

• Natural numbers
• Rational numbers
• Real numbers
• "Integer" is Latin for "hasn't been fucked with"
• And of course, the most normal numbers: https://en.wikipedia.org/wiki/Normal_number

It's Starship with the Gruvbox Rainbow preset (with customization to fit my needs): https://starship.rs/presets/gruvbox-rainbow

Since you're already using a Nerd font, this shouldn't be too difficult for you to set up, if you want it.

A rebase rewrites the history of your branch, so that it's as if you just branched off and then coded all your changes in one sitting.

It will go through each of your commits and try to apply them one after another. If something changed on the base branch that conflicts with your changes, it will prompt you to adjust your commit. You adjust it so that looks as if you just coded it on top of the base branch.

When you have lots of commits on your branch, this can mean that while you're rebasing, you have to then also change your following commits which happened to touch the same lines as a previous commit. This can mean additional, stupid work.

As such, a workflow using rebases ("trunk-based workflow") works best, if you can rebase often and merge back early. You won't get merge conflicts when merging back, nor merge commits, because you resolved these while rebasing.

In particular in smaller teams where you have tight-knit communication, this workflow is absolutely stellar. It completely bypasses so many pain points that folks have with Git.
Merge conflicts are significantly reduced when you merge often and a trunk-based workflow removes the ceremony that typically prevents teams from doing just that.

I have not yet jumped into theming everything with Gruvbox yet, but man, I do default towards it hard. Recently I needed to pick a theme for Newsboat (terminal RSS reader), because its default theme wasn't legible with a light terminal background, so I randomly select their universal-color theme to check out first and it hits me with this beauty:

(Bonus gruvboxy shell prompt in terminal below. 🙃)

I didn't even look at the other themes anymore, to the point where I realized only just now that they actually have a dedicated gruvbox theme. Unfortunately, it actually looks less gruvboxy...

Typically, touchpad gestures (particularly multi-touch gestures) will work better on Wayland, because it has libinput.

In a less extreme sense, I find there's also an inverse relationship between skill and marketing effort, because:

• Marketing activities take time away from honing your skills. Even if you "just" (in very fucking big air quotes) build something useful that you release as open-source, you'll still spend time answering user questions, reviewing PRs, writing documentation, ensuring backward compatibility etc..
  These are also useful skills, but they still prevent you from exercising your coding skills.

• The most popular platforms for marketing yourself are also the most rapey platforms. People with high technical skill will be aware of this. The most privileged of them may not need to care.
  But those that worked their asses off, because they had to start from an unprivileged position, those need to care. Because they will be disadvantaged and harassed, when people see that they're from a minority or women.
  You miss out on those with the highest work drive. You miss out on skills that people build when they need to protect their privacy. And you miss out on a culturally rich workforce and get a fragile monoculture instead.

Yeah, it didn't have CI runners or complex project management features. Pushing code can be done later. Looking at open-source issues can be done later.

I'm neither Scottish nor ultra-deeply embedded into the trans community, so I doubt I would've heard of politician statements or the like. But yeah, I do think I would've heard of it, if the ruling got repealed, and I did not hear of that, unfortunately.

I guess, the main aftermath is that it got reported pretty much globally, because it is clever and there are boobs involved, so even clickbait newspapers can print that. Well, and hopefully it got people talking and reevaluating their preconceptions.