![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
I believe that one was patched a while ago
I believe that one was patched a while ago
That is usually more incompetence than malice. They write a game that requires different operation on amd vs Nvidia devices and basically write an
If Nvidia: Do x; Else if amd: Do Y; Else: Crash;
The idea being that if the check for amd/Nvidia fails, there must be an issue with the check function. The developers didn’t consider the possibility of a non amd/Nvidia card. This was especially true of old games. There are a lot of 1990s-2000s titles that won’t run on modern cards or modern windows because the developers didn’t program a failure mode of “just try it”
It’s like grifting, but also a pyramid scheme.
TL/DW for those of us who don’t learn well from video content?
I have so many questions
I think most of us blocked it out
You would expose a single port to multiple vlans, and then bind multiple addresses to that single physical connected interface. Each service would then bind itself to the appropriate address, rather than “*”
You should consider reversing the roles. There’s no reason your homelab cannot be the client, and have your vps be the server. Once the wireguard virtual network exists, network traffic doesn’t really care which was the client and which was the server. Saves you from opening a port to attackers on your home network.
There is also the argument that it’s more complicated under the hood and harder to troubleshoot, particularly because of it’s inherent parallelism and dependency-tree design, whereas initv was inherently serial. It was much more straightforward to pick the order in which services started and shut down on an initv system.
For example, say I write a service and I want it to always be the first service stopped during a shutdown, and I want all other services to wait for it to stop before shutting down. That was trivial to do on an initv system, it’s basically impossible on systemd.
For those wondering, yes I did run into this situation. My solution was clobbering the shutdown, poweroff, and restart binaries with scripts earlier in path search that stop my service, verify that they’re stopped, and then hook back to systemd to do the power event.
Sorry I should have said “carbons and carbons related qol extensions”
Did you ever get carbons working properly? (As in, mobile and desktop clients of the same user both getting messages and marking as read remotely between them)
*privacy from everyone except us, which conveniently makes our ad revenue line go up.
I actually had one of these myself. I worked at a college help desk as a student, and I got a call and the guy said “every time I flush the toilet, Xbox live disconnects”
My first thought was that it was a joke, the absurdity of the thing right? I unironically asked if I was being pranked, and he said he knew we wouldn’t believe him so he made a video. Sure enough, he walks into the bathroom, flushes the toilet, and like 5s later his Xbox shows a disconnection message on the TV.
Absolutely dumbfounded, I sent the networking guys up to his room, and like all of these stories, it does have a reasonable explanation. They ran the xbox’s Ethernet cable under a rug that was in front of the bathroom. Every time someone went to the bathroom, they would step on the cable, and the Xbox would disconnect. The timeout was 30s or so, just long enough that they’d pee or flush the toilet or whatever before they noticed the disconnection.
I support your position in principle, but canceled my own nitro when they did the android app redesign. It went from really snappy (respecting system animation scale settings) to completely ignoring them. It feels like molasses compared to every other phone app that operates at the system set 0.25 animation scale.
They also completely broke foldable support, and if your device changes aspect ratios inside a chat, you have to restart your client to get it to behave correctly again.
The enshittification is real and I am voting with my wallet.
Xmpp is by design, an extensible protocol. There just doesn’t seem to be any motivation to develop for it.
I actually did, because once I bought it they couldn’t shut down the dlc servers on me when they released the next one.
sheryl crow - you were meant for me
They probably would. As the value of a dollar drops disproportionate to the value of goods/services, the cost in dollars for the same good/service goes up.
buy it from somewhere that has a 14 or 30 day “no questions asked” return policy. A competent retailer will have that baked into their margins so don’t feel bad doing it. I think that’s your best bet.
Okay, I’m hooked, I have to know the non-clickbait story