The Tunnel daemon creates an encrypted tunnel between your origin web server and Cloudflare’s nearest data center, all without opening any public inbound ports.

From https://www.cloudflare.com/products/tunnel/

The good news is that in order to exploit the new vulnerability, the attacker first has to obtain kernel level access to the system somehow - by exploiting some other vulnerabilities perhaps.

The bad news is once Sinkclose attack is performed, it can be hard to detect and mitigate: it can even survive an OS reinstall.

Cloudflare tunnel is an option, you can even scrap your own nginx

I use a PS5 controller paired wirelessly with my deck. I think the touchpad just worked for me with no extra settings (apart from picking a steam input configuration that supports it) but in practice I almost never use it for gaming.

Not sure what chiaki4deck is but I don’t believe it’s necessary for PS5 controller support.

Update: i may have installed something for gyro support at some point but it wasn’t chiaki4deck

Unless you’ve used something secure for formatting or wrote data to the SD after, consider attempting data recovery.

1. I don’t necessarily like the feeling of the button, in my opinion the buttons on the PS controllers are more comfortable. That said, I have zero functional issues with the buttons on my OLED and before that had zero issues with the LCD version.

I think the minimap gets colored in red in such areas but I agree a better indicator or a hint could be nice.

In case of moonrise towers, if you just cross the bridge back to town you can long rest there and come back.

This seems to be implemented in the Steam Deck client update from November 16th

Haven’t tried it myself though.

I keep seeing this comment and I think people are confused about private companies.

Private company is one that’s not publicly listed (traded on an exchange). Private companies still have shareholders, they may still have board of directors with shareholders representatives sitting in them. And these shareholders can still demand returns on their investment. There’s a whole industry around this called private equity.

Now it doesn’t look like Gabe Newell ever took Private Equity funding and according to the internet he owns 50% of the Valve shares but that still means that a large pile of shares is owned by other people who get some say in the company’s direction.

So saying that Valve makes this or that decision because they are private is wrong. Most companies are private and you don’t see them being all charitable and investing in open source.

You could argue that Valve is allowed to make certain decisions more freely because he’s a co-founder who still owns the majority stake though. And the company being private means that unless he sells his shares he gets to retain that control.

The way I understand it, disabling FSR is supposed to make performance worse, or at least GPU more busy. That and increasing some settings from medium to high has the potential to slow things down to unplayable level. But maybe if you decrease the FPS to 30 it’ll be okay, dunno.

For me changing the FSR mode from the default was more of a way to get rid of the blur.

Eagerly waiting for FSR2 which I’ve heard is going to be implemented in one of the patches.

• Everything on “medium”
• SMAA instead of TAA to avoid blur
• FSR set to Quality to avoid blur
• cap FPS to 40
• vanilla stable SteamOS with no tinkering

Works really well so far in act 1. With the above settings GPU seems to be the bottleneck. But, as the others pointed out, later acts are more demanding.

AirPods Pro gen 2 are problematic with Steam deck: https://steamcommunity.com/app/1675200/discussions/1/3370405530896320680/?tscn=1689301955

Dozens of people reports issues, most commenters are able to pair but experience various stability issues on top of the headphones not connecting automatically.

With no visible response from Valve, the hope is that kernel and relevant Bluetooth and pipewire packages upgraded in the upcoming SteamOS 3.6 contain some fixes.

AirPods Pro gen 1 are not affected.

I’m running Arch on my RPI 4b+ and quite happy with it.

The installation was pretty simple IIRC - I did run into some issue with uboot which was easily solved by searching for the error on the internet.

Arch Linux ARM ships with a mainline aarch64 kernel and uboot by default, but if you are interested in running the RPI kernel and their boot loader, there’s a custom pacman repo and instruction on the forums: https://archlinuxarm.org/forum/viewtopic.php?t=16144

All in all I don’t think arch needs that much maintenance on a non-critical home server - just make sure to check for config updates every now and then and reboot after kernel upgrades.