Great release. However I'm still waiting for snapping/alignment/distribution to be usable. Right now, some things override others (even when holding a modifier to constrain node to an axis, it will snap to things that are not aligned with the axis), and because of visual vs geometric bounding box when resizing things it will snap to align with other shapes but when you let go of LMB, the object won't be aligned anyway (so what was the point of snapping in the first place). Also sometimes things will snap to a guideline from a mile away, when things I'm trying to move are nowhere close to a guideline. I'm coming drom other software (specifically, Corel Draw) and understand it's not fair to compare different tools and demand from one to mimic the other, especially when Inkscape is FOSS and Corel Draw is a commercial product made by paid developers. And you could also say most of things I'm complaining about are muscle memory things because I've been using Corel for years and need to let go of old habits and get used to Inkscape if I want to switch to it rather than demand Inkscape to be more Corel like. But I still believe Corel does some things just right. I pretty much never needed to turn off snapping in Corel and "it just worked", objects would never snap to a guide on the other side of the screen and constrained nodes (when holding Shift) would still both be constrained to axis and snap to objects, meaning it snaps on the intersection of the other object and the axis I'm moving along. Also if I'm resizing a box and the edge snaps to a guide, when I let go, in Corel the edge of the box will 100% be aligned with the guide, unlike in Inkscape. I'm pretty sure some of these issues are because of Geometric vs Visual bounding box differences, and it's good we can at least choose between the two: Corel can't even deal with visual bounding boxes IIRC. You work with geometric bounding box only. I think adding the toggle somewhere in the toolbar would be a great thing so that we don't have to go into the menu and find it every time, maybe even a hotkey to toggle between the two.

microG is an open source, reverse engineered replacement for Google Play Services on Android. It still connects to Google servers, though. GrapheneOS doesn't use it because they came up with an effective Sandboxing solution, and microG requires spoofing the signature to make applications believe that the service was signed by Google, which introduces a potential attack vector.

Right, but you could have just made one yourself And then there would be a bus factor of one. It's not just about making a helm chart for myself, it's about having something that can be shared with the community, that doesn't depend on any single person to be maintained and updated. It's about having an organization that provides "packages" for Kubernetes, for people/orgs that don't have the time, expertise, and energy to maintain them. I greatly respect Ananace, who is in the comments of this post, and mentioned their Helm charts. The work is excellent. But looking through the commits, it's just one person, doing something that primarily consists of bumping version numbers. Contrast this to the Matrix ESS helm chart, where the commits consist of many more contributors, and also include feature additions to the helm chart.

Geez I'd be pretty shocked if the IC in Europe depended on a third party for their maps

OrganicMaps GitHub repo was blocked due to contributor being geolocated in a US-sanctioned place https://mastodon.social/@organicmaps/114155428924741370