I similarly have been using Gitea for some years. I use it as my main forge and mirror to Github for discoverability and community reports and contributions.
For public projects I have workflows that can publish and push containers to both Gitea and Github.
I don't see companies using open source lining up to support the developers. Good for developers to come up with some monetization strategies to keep their software alive.
From what I remember, next-auth is kind of dead and Better Auth developers have been maintaining security of next-auth for some time now. (or was it Vercel that did the maintaining?)
Better Auth is the go-to solution for many people using Nextjs, so it makes sense that Vercel puts some effort in maintaining it.
I have never had issues running Nextjs in regular containers, it is just a good open source solution, I don't see why it would be any different with Better Auth.
Last time I was in London for a day, I simply reserved a table at one of the restaurants at Sky Garden and got in without any queues. Maybe I booked it on the previous evening, but not much earlier than that.
I doubt that. But they clearly thought that people should have a choice. And it is great. But fractured community using different tools for the same task makes slower progress. Each approach has its positives and negatives.
I think it is great that we have wayland and systemd. It will eventually lead to something greater in the future.
When it comes to incorrect profiles, I suggest making a pull request to alsa-project/alsa-ucm-conf with correct configuration. I had similar issue with my audio interface a couple years ago but it was quickly merged and now it works better than on Windows or macOS.
Before that I did have custom config, it was not that hard to set up, there are great examples and explanations on Arch wiki: https://wiki.archlinux.org/title/PipeWire
Where none of the desktop environments offer the same feature set. And the more compositors there are the harder it is for apps to use those new protocols, and guaranteeing a ton of bug reports from users using an unsupported compositor. That just hinders Linux desktop app development.
I think it came from the necessity for rapid integrations between different parts of the OS. And if it is handled as a single project it takes less time to improve it, since you don't have to align with 10 different projects and their release cycles.
With unified kernel images there is no need for grub or any other bootloader anymore. And UKI simplifies boot configuration and helps improving security in some aspects.
Yes, but people learned from issues that pulseaudio had and then came pipewire. Everyone is happy now.
I don't know about the philosophical aspects, but from pure technical point of view systemd brought some order into the mess. Before systemd it seemed like most distros were barely holding together with duct tape. Systemd standardized a lot of things.
I am fine with a little bit of controversy if the result is a much better desktop OS experience for the user. And as a relatively long time Linux user, I can certainly say it is much better now than it was 20 years ago.
It depends on how you set it up, but main doesn't have to be the stable release branch. From what I have seen, in most public projects it is the staging area for the next release.
If you have to go back to previous releases you have tags.
Still unable to get any repair manuals for cars, firmware locked down by PIN. For US VINs for the same car model you can purchase access to that easily. Meanwhile in EU you need to be an authorized service to get that.
When will EU/EEZ introduce right to repair? So much talk about freedom in EU but you can't even fix your own EU made car. All we get are stupid cookie prompts.
I made a custom Payload CMS block that allows to create and update excalidraw diagrams within the CMS. It supports dark and light mode switching and rendering inline or as external SVG.
And last weekend I added MCP server with Oauth so I could generate and update those diagrams and add them to post drafts from Claude. I think it is more convenient since I don't have to use API billing model and don't need to build a custom UI.
Originally I wanted to sync posts from Obsidian but it doesn't have good enough image handling which I sometimes need and I needed extra metadata to unlist or password protect or noindex some posts.
For public projects I have workflows that can publish and push containers to both Gitea and Github.