

Oh, that’s interesting. It is pretty distinct.


Oh, that’s interesting. It is pretty distinct.


Like the energy, but Comic Sans is also a war crime.
Depends on the players. Some want to play pretend. Some want to play XCOM with dice.
Very common here in the US as an alternative to “bless you”.
Cronenberg’s Law: For every Garnet there’s a Brundlefly level freak of nature.


Btrfs has a bunch of features and is one of the contenders for the “next” filesystem. Ext4 is utterly bulletproof though and has good enough perf so it’s still your best bet unless you specifically want to use the advanced btrfs features.


It’s always great to see someone scratch their own itch, so kudos. However, I’m curious what the actual pain point is? Does your mouse not sample fast enough? Noticeable input lag on a gamepad? Seems like this would be a bug with the implementation if it needs to be overclocked to fix…
Oh, that makes more sense, but then “unsigned” void?
Okay, U8, sure, but a boolean is U0? Surely U1 if you absolutely must…


I’m with you on rejecting AI being sane, but the idea that gaming wikis should be integrated into wikipedia is kinda nuts. If I search “Iron” on wikipedia I’m looking for facts, not a thousand item long disambiguation cluttered with every game that has iron as a resource. Conversely, on a game wiki my search for “Iron” has an entirely different context and I’m looking for different info.
Not to mention game wikis have way lower editorial standards, their own tone (e.g. making jokes), versioning concerns, their own new user friendly homepages etc.
Wikipedia could tuck this all into a separate namespace, sure, but that’s effectively a separate wiki anyway and then it raises questions like “why is wikipedia hosting a mechanical guide for this porn game?” or “How long do we need to host the content for this game that peaked in 2012 and is now abandonware?” that are conveniently sidestepped by those communities supporting themselves.
An anti-DEI fork by a wingnut and a project that isn’t even half way ready to use starting from scratch in a niche language. Neither of which are capable of dealing with the fundamental problem of X, the protocol itself, without becoming something entirely different.
… I’m not holding my breath.
Agreed. I was an early Wayland convert because once upon a time I started writing a WM and taking an interest in X internals… And then my face melted off like I’d opened the Ark of the Covenant.
Things are so much simpler now.
I use KDE Connect remote input on Wayland all the time…
KMag is broken (simply has not been updated, not like it couldn’t work) but you can zoom the entire screen in KDE with super +/- is that not good enough?
Didn’t they straighten out Wayland support? I thought this was a thing of the past as of 555, but I also haven’t run Nvidia myself in years and years.
Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that’s had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.
It’s fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.
Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.


I have a giant FLAC collection and I sometimes wish I could use these local players because I used Winamp/XMMS/quod libet back in the day, but I feel like I just can’t give up consistent access from outside the house.
I ran Tauon for a while (and have run a few of the others over the years) but I always end up back at my Airsonic setup. Works in any browser, works in a few different Android apps (Subsonic compatible), less of a pain than mpd.
Maybe it’d be different if I was still sitting in front of my computer virtually all the time, but nowadays phone to Bluetooth speaker/car/Chromecast is like 90% of my listening.


Basically, the executing thread might get interrupted in a window of code where the interrupt flags are wrong. Not looking at the specifics, but this could lead to various things from mostly harmless (e.g. potentially holding a lock for many times longer than expected but eventually releasing it) to program crashing (e.g. if taking an interrupt while handling the fault leaves the data structures in an inconsistent state).
This is likely the first one, since it was missed for so long in a very well exercised piece of code.


Are you running the native version or through Proton? When I played Civ VI the Linux native version performed worse than using Proton, ironically. Either way, maybe try switching?
Since you specified multiplayer I’m guessing it’s not time to load from disk or anything.
deleted by creator