I’ve seen them as low as $220 on ebay with accessories and at least one SD Card, and as high as $400 recently (but most are upgraded storage with +1tb SD).

Definitely look at what the market is selling for.

My wife started playing it today and I put it on Ultra for the hell of it - doens’t even hiccup! I didn’t put the FPS overlay on, but so far there hasn’t been a single issue!

The controller layout mapping can be buggy at times, but it’s REALLY capable at what it does.

I haven’t been stifled by the controller configuration on any game. I’ve been playing RimWorld lately which is heavily menu-driven, selections, etc. I also play some RTS’ like Red Alert.

Also keep in mind the screen is touch capable, so there’s a lot of possibilities.

1. Yep, you can have multiple BT devices connected at once. I typically have my xbox controller, bt headset, and a bt speaker connected at all times! From my understanding the way the Xbox itself handles the audio is through a wifi-direct connection, not bluetooth. Can confirm that BT connected xbox controller does NOT allow audio. Default audio operations in KDE/Gamescope will route to last connected device. If you install qpwgraph you can control audio routing pretty easily in KDE - I usually have game audio going to headset and music from chrome/youtube going to my bt speaker for background noise.

2. A lot of the USB-C dongles like this one have a USBC-PD (Power Delivery) capable port, so you can get away with using that if yours does. Having said that, literally any Steam Deck dock is worth it just for displaying your handheld! You can find them for $20-40USD on Amazon, and right now lots have discounts due to Black Friday sales!

3. Honestly that’s your call… Personally, I play on the TV most of the time, and the LCD still looks pretty damn good when I do play handheld. For me, it’s a “what I don’t know, won’t hurt me” situation, and you can get the LCD version for pretty darn cheap (compared to retail) these days thanks to the OLED release. Unfortunately, and I don’t understand why, the wake on bluetooth doesn’t work on the LCD w/SteamOS 3.5.7.

Feel free to ask any more questions you might have and I can do my best to answer!

Given they said it was “painful” to hit the 64gb model cost, I’d imagine the licensing costs would wipe any possible revenue that would ultimately extend into the software (games) revenue.

So, I’d say 0% chance.

SteamOS is a fantastic distro with all the heavy lifting done, and they’ve advanced Wine/Proton so much that it would be a complete loss to jump over to Windows.

First and foremost, the Steam Deck uses USB-C PD (USBC Power Delivery).

This is a standard between the wall adapter, cables, and hardware requiring the power (i.e., Steam Deck).

You could use a 10000000 Watt capable adapter, but through negotiation the Steam Deck will only ever ask for 45 Watts maximum. I personally have a 100 Watt capable adapter and can verify both on the Steam Deck and with a passthru digital meter that tells me what is being drawn.

So to simply answer your question - literally any Dock, so long as it touts having USB-C PD.

Sure… but literally any type of lookup is vulnerable to MITM without something like DNSSEC, which isn’t too common outside of enterprise or managed DNS servers like cloudflare, etc (which still require configuration). Most users, unless they WORK in InfoSec, literally don’t bother with (or even are aware of) it.

At that point you’re kinda just drawing up what-if’s - and while technically valid, it’s also a very limited concern.

It’s more common to access a computer by hostname on a LAN than it is to have a MITM on your network. If you do, you have bigger concerns.

I think you’re misunderstanding the concept of “.local TLD is considered unsafe.”

It’s not UNSAFE unsafe… It’s unsafe to resolve .local TLD yourself as it’s a protocol specifically to avoid having a DNS server. Resolving yourself on a DNS would result in conflicts, which is the “unsafe” part.

As for the comment you linked to, this directly coincides with why it’s not a DNS Search, and is a “unicast” (actually it’s a multicast, not unicast) protocol.