Dead Space 1 remaster. I categorically refuse to give any money to EA (even before the Saudi buyout), and that’s their only game I’m even remotely interested in that isn’t available through alternative channels.

You spent the better part of the week spewing contrarian nonsense. What are you trying to achieve? Are you farming downvotes?

I’m going to guess (this is speculation) that Shotbolt & co. are sanctimonious, self-serving ambulance chaser dipshits. Wolfire and Epic opened the sluice gate and they wanted a slice of the cake in a different jurisdiction. Whatever payout the “gamers” might ever receive (this is NOT speculation) will amount to literal pennies while the lawyers barristers take home millions.

Absolute hogwash.

I’ve had good experiences with Rustdesk. The client is open-source and the no-cost server components (ID and Relay servers) are self-hostable. The remote server works on X11 and Windows. I use this script to run XFCE+Rustdesk in a headless session:

export SERVERNUM=69
export SCREEN_SIZE='-screen 0 2560x1440x24'
export DISPLAY=":${SERVERNUM}"
export XDG_SESSION_TYPE=x11

xvfb-run --server-num="${SERVERNUM}" --server-args "${SCREEN_SIZE}" startxfce4 & disown
sleep 1
flatpak run com.rustdesk.RustDesk & disown

Sunshine + Moonlight is also a good choice. I have Sunshine installed on a box at home and use Tailscale to connect to it from the Moonlight client. At 1440p 60 FPS it has no visible compression artifacts and responsive enough for gaming.

Even HDR is still “beta” on KDE iirc.

That’s a weird comparison because HDR is never going to happen on X.org (nor probably in the X11 protocol or clients). Wayland is being actively developed and the developers took it from something that can be made to work with some effort and some concessions to something that will reliably work in most cases. The year isn’t 1987 – software isn’t being written by nerds for nerds who can tinker and fix issues or add new features as a patchwork of unmaintainable code.

My home PC, about once a week, or whenever I have to install new software. My work PC, about once a month because the nvidia driver takes fucking ages to update because of DKMS.

As for the servers under my professional care… it depends. Most of the servers that I made run Debian that I update three times a year whenever the downtime is acceptable for the university (spring break, late summer, early december) or if a CVE needs fixing (e.g. xz-utils). One internet-facing server that I inherited still runs Ubuntu 16.04 because some teachers can’t possibly live without some legacy software and will throw a tantrum if upgrading is even mentioned – that one gets zero updates, and I got the dean’s promise in writing that I wouldn’t be held responsible for it.

The big virtualization server still runs ESXi 6 because the university didn’t want to pay for a lifetime license when it was available, doesn’t want to pay for a subscription now, and doesn’t want the downtime required to fully migrate to Proxmox VE. So it gets no updates. Plus it has a bad SSL cert and I need Chromium’s thisisunsafe to bypass the error.

It’s fucking rough out here.

That was the UK.

Wayland has an actual future. It is being actively developed. Issues are being fixed and new features are added at least somewhat frequently. X11 might survive past the heat death of the universe, but it will be a stale, fossilized codebase maintained entirely by a small group of opinionated people.

My work PC has a 3080 and the latest nvidia-dkms in the Arch repo. I haven’t had a single display-related issue for probably a year.

c/linuxmemes

deleted by creator

The 10.0 is Wine’s version that the Proton release is based on, the -4 is the version of Valve’s patches on top of Wine. Steam doesn’t keep individual patch versions around, only the latest available patch for each major version.

Look up where the word comes from if you want to be unreasonably angry.

That is the same kind of pedantry as claiming that ketchup is a smoothie because the tomato is a fruit.

Why do hikers travel to different mountains to conquer?

The concern: “Why aren’t we in on it?”

It’s not a bug, it’s an unimplemented feature. The !community@instance syntax is not part of any Markdown flavour, so every client has to implement it independently, and it’s possible that it collides with some other kind of token (e.g. with the @user tag).

I know. I was responding to the comment, not the video.