I've been using Niri for a little under a year now on both my desktop and laptop, I like it a lot compared to regular tiling window managers (I used QTile for 2-3 years on my desktop and Hyprland on my laptop for about a year until I found out about vaxry).

Personally, I usually group my workspaces by app category (e.g. browser, system-related, chat windows, games, etc.) which works really well with a scrolling model since you can have multiple "fullscreen" apps per workspace, or a fullscreen apps and half-width app like a file explorer for dragging files over to the main app. It also works well for me since I am unlikely to have more than 2-3 full-width apps in the same category.

I like organizing things that way because it makes my hotkeys consistent for the thing I'm trying to do. For example, if I have a chat window open, my hotkey to get there will always be meta+3 regardless of what app it is and how many other chat apps I have open.

It could be. It could also just be that the engineers had to rush to meet a deadline. Last year during the initial Pixel 10 release the pixels were using a bunch of out-of-tree patches until QPR1 (which also didn't have its source code released until December) because the initial launch was timed right with Android 16. That meant that Pixel 10s couldn't boot anything other than the stock Pixel ROM because no one else had those patches. GrapheneOS couldn't support them until that release in December happened. This could end up being something similar.

Apparently it's likely that the SoC does support MTE, but that Google had disabled it in firmware at launch because of some issues and is going to re-enable it for QPR2. Who knows whether that is actually the case though

Few things:

• does the issue happen in handheld mode?
  • if so, this is probably an issue somewhere with your switch, either with the game files or the hardware itself.
• does the issue happen in other games?

If both of these questions are "yes", it's probably an issue with your switch.

If the second question is no, your cartridge is probably busted. It could also be the updates, so you could try deleting and reinstalling just the update data. If the update data is on an SD card (is that possible for cartridges?) it could also be an issue with the SD card.

If the first question was no, it's probably a hardware issue somewhere between your switch and your monitor: the dock, the HDMI cable, your monitor, or the display port signal chip inside the switch itself.

• Try with a different HDMI cable. If this fixes it, the cable is the problem.
• Are you using a capture card? If so, try without that. If this fixes it, your capture card is the problem.
• Try connecting the monitor with a different device and playing sounds (e.g. a laptop)
• If your monitor has multiple HDMI ports, try a different one.
• If you know anyone else with a switch, ask if you can plug your switch into their dock and see if the issue still happens with their dock.

The problem could be any range of things from the cable or port breaking to the HDMI encoder breaking. Those steps might at least help narrow it down more

Worth noting that when you buy a pixel from a carrier in the US the bootloader is typically locked anyway, at least for the big ones. This even includes versions where the SIM is unlocked to support other carriers

I imagine the work will make its way over to Eden at some point which is a more actively-developed yuzu fork

If you have Aurora installed that is still being done. If you don't want to send that list then don't use any play services.

It runs as an unprivileged user app and uses randomized accounts.

Google play services under graphene are all also unprivileged.

You can add all apps you dont want Google to know of to your blocklist, so the unique fingerprint from your app list is extremely reduced

I wouldn't say extremely, as you still need to keep all of the apps which you install from the store itself unblocked to get updates. Anecdotally for me, that list is all of the niche apps which I can't use FOSS alternatives for, like banking, work, transit, etc. so it's very likely still uniquely identifying. If you're hiding system services in Aurora that you don't want it touching, that makes it even easier to identify you, because Google play doesn't do that.

Aurora is WAY better for privacy

I'm not a security researcher and am basically regurgitating what the Graphene team has said about it, as I think they know a lot more about how the play store works under the hood and the information that is required to send to Google than I do. I think they have a blog post about it somewhere.

The GrapheneOS team explicitly recommends against installing the aurora store for that exact reason. If you can install the stock play store with a burner email then the aurora store doesn't actually give much of a privacy benefit (you are still uniquely identified either way) but aurora store is playing a game of whack-a-mole with Google.

My understanding from the blogs is that the extra load of maintaining so many downstream patches (both for rust support and all of the reverse engineered hardware support) ended up being one of the main reasons M3/M4 support isn't in Asahi yet. Now that a lot of the patches are finally getting merged into the kernel a lot of their other work can start moving forward

The dremmel is for the thing you plug the battery into

I didn't make it 😭 Gonna have to try harder for the next one