@Coyote yeah I did run into a fair share of issues, my biggest simply being the controller configuration being reset to default whenever steam is running. There's some kind of background service that handles the controller with right trigger and touchpad as a fake mouse, but it's not nearly as useful as the custom configurations.
Apparently Valve disabled the keyring in pacman? I went into pacman.conf and all of the Valve repositories had signing disabled and trying to update from the AUR or default repos just failed every time because the keyring was read only. I'm not sure why they did that.
Otherwise it's been mostly smooth sailing. The minor annoyances are things I can deal with I guess
@Coyote Yeah I already got the controller part down, the issue is just that it doesn't keep the custom bindings when Steam isn't left open
I did try repopulating the keyring and disabling steamos-readonly mode (whatever that is) but it didn't work, so I resorted to turning off package signing entirely. I've been using flatpak for mostly everything so far wherever possible
I think I had to run "pacman-key --populate" and "pacman-key --refresh-keys" to be able to update and install packages; you also need to run "sudo steamos-readonly disable" to get rid of the read-only errors. Valve's website, https://help.steampowered.com/en/faqs/view/671A-4453-E8D2-323C, also said that they might nuke everything that isn't a Flatpak in an update, though you might be safe if you configure pacman to work entirely out of your home directory; I haven't tried myself.
My only real grip is the nfs standby issue which means I've got to run mount anytime I want to access my NAS, and I have to restart my Deck after I'm done with it.