It’s not what the buttons look like, it’s what they do. In Krita, making an ellipse involves clicking the ellipse button and dragging it somewhere. You now have an ellipse, and you hold shift if you want to make it a circle instead.

In GIMP there is no direct ellipse tool, there’s only an ellipse select tool, likewise you hold shift to make it a circle. Then you use a menu item to select the border of your selection, getting a popup to let you determine how much pixels you want. And then, you use the fill tool or fill menu item to fill it. That’s a surprising amount of clicks to accomplish what’s most likely the single most common task for anyone opening a screenshot in an image editor. I’m not aware of any easier/faster method to do it. Feels like it should exist, but this is also what you get if you search for how to draw a circle in GIMP, so if it exists everyone’s missing it.

GIMP’s method gives you more power, but you rarely ever need that power. But when you do, Krita also has ellipse select, border select and various fill tools that can be strung together in the same way.

Login isn’t necessary, but there is no :latest tag published so you need to pull a version that exists. The current version is at codeberg.org/forgejo/forgejo:1.21.8-0 or at :1.21 if you want one that tracks patch updates (as found in the container registry).

Within 15 days of making the account, to add. If you missed it or decided you’d rather not give them the password to your previous email account (the alt objective for the Gmail-specific thing) you don’t get a second chance.

I get that it’s free but I trust them much less because of the way they handle that.

Note: The HTTP/3 QUIC module is not enabled by default and is considered experimental

Do note that despite not being enabled by default, it is enabled in the official binary packages.

There’s a funny amount of layers to this thing but as far as I’m concerned, if it’s a feature you ship in the default binary packages on your site, that is definitively enough for a CVE even if it’s disabled by default.

Everything was forked and should eventually end up on F-Droid, but most things haven’t had a release yet. My understanding is that they’re hoping to do everything right immediately, including having proper new branding and all the shared functionality from Simple Thank You.

The F-Droid versions of SMT apps are perfectly safe and shouldn’t be going anywhere. (But if you have Google Play versions, I wouldn’t trust those anymore, those are owned by ZipoApps now.)

“Open source” has more or less always meant something very specific as defined by the Open Source Definition. Adding restrictions on top like no commercial use or no lawsuits turns it into “source available”.

As pointed out, the DNS issue was fixed, and the other point made about Python wheels has also been addressed; quite a good chunk of packages on PyPi have had a musl wheel added in the past 6 months or so, including numpy & scipy. I’m also not certain if the Go part is true; probably somewhere around half of the Go apps I’m running as a container are running or were built on an Alpine base.