Yeah, but you have compared top-of-the-line Ryzen model vs. Intel’s high-medium tier. That’s not gonna really help.

Were you booting to Windows between first successful boot and one with this error? Are you sure you have secure boot disabled?

I think most modern laptops output to display via integrated GPU even if it’s dedicated GPU doing the work. I know there are laptops with much chips that let user select which GPU is directly connected to display, but I guess those are mostly high-end models.

Yeah, not sure if it’s my ROM (DivestOS) or just Android 13, but in Settings > Screen lock I have Enhanced PIN privacy toggle that does just what you’ve described.

I have had some problems with PipeWire as JACK replacement, mostly it was some tearing artifacts that were very annoying. Recently though I learned how to use PipeWire (which is great for general desktop audio usage + works with Bluetooth really good) with JACK for pro-audio applications. By using the JACK DBus detect module it is possible to turn PipeWire into JACK client when ever the latter one is started.

So this way it is not required to use PulseAudio at all with JACK. There’s also possibility to use PipeWire as JACK server because it also provides such API.

I use Grist for this purpose. Check out this template, this may be just what you want and using widgets it is quite easy to create a form to append to the expenses database (just like here). Grist works really nice on mobile too and is also pretty easy to self-host if you need an extra degree of privacy, but you can use the official instance as well.

If you want I can send you my Grist template that does pretty much all things you want.

Google is intrusive. The story where Google literally send police on a dad that had stored photos of his son on Google Drive that he meant to show to a doctor or countless stories with scanning emails. For the first one a mitigation could be to encrypt files before hand, but it’s not at all convenient for regular people that want to have their photos automatically synced and backed up. For the second one, you could also encrypt emails beforehand using PGP, but yeah, pretty much no one does that. And none of this potential mitigations make Google any less intrusive. And I think I could even argue they allow themselves to be like that because they are this big.

That being said, I’m not arguing that Google Workspace, that integrate tools, storage and emails for way cheaper that other alternatives, is not great value for companies. But it’s still Google, so no matter how you look at it, it’s still bad choice for privacy. But the other choice being Microsoft, there’s hardly a better way.

In my setup I still use reverse proxy even though all of my services are inside a VPN. IMO it is just more convenient to have services accesible as subdomains or subdirectory than as different ports.

But pretty much in the same way as the YouTube’s frontend requesting content from YouTube’s backend. This is an equivalent of you loading a video on YouTube then going to developer tools and copying links from the Network tab. AFAIK all tools (Invidious, Piped, yt-dl) work this way.

I’ve fully switched to Wayland some time ago (it could be already a year) after I learned about how insecure X really is and I honestly do not experience any issues that I sometimes see on the internet. I’ve been using Gnome for few months, but now I switched to KDE. I think a lot of apps are working natively on Wayland, but for other cases you have XWayland that also works flawlessy in my opinion.

One of things that was issue for me was that I couldn’t use Auto-Type feature in KeePassXC, because Wayland doesn’t let apps pretend to be a keyboard or capture windows as easily as X does. Funnily enough, I’ve managed to get it working by running keepassxc --platform xcb, but it stopped working some time ago and I’m not entirely sure why. Other thing that is a problem for me is screen sharing. Wayland doesn’t allow apps to capture screen as I mentioned earlier so it heavily relies on PipeWire for this and PipeWire has its own sets of problems. It seems working correctly for the most part, but I couldn’t really figure out how to share screen with sound. Not a dealbreaker for me, and a workaround would be to route audio as a microphone input for example, but it is an issue nonetheless. This is only a problem on Discord, in OBS you can easily select video and audio sources.

If you’re using KDE already, you could just select Plasma (Wayland) in your display manager and play with it a bit to see if you like it and experience any issues.