I’ve always hated it and thought it was a stupid untuitive mechanic that didn’t map to anything in real life. It also looks equally stupid in multiplayer when you see player character models spasm their way up a ledge during a crouch jump. It’s an old school mechanic that I am glad is going out of fashion due to better vault controls.

like a simulation of pulling your legs up in real life.

You don’t pull your legs up in real life though, you use your hands to vault onto something. You can’t just swap stances in mid air without holding onto anything. Even if you were talking about box jumps, like the kinds you normally do at a gym, it still isn’t anything remotely like a crouch jump. Also anyone doing a box jump in an actual combat situation just looks goofy.

Any time a game explicitly has a tutorial for crouch jump, my immersion is completely broken. I am instantly reminded that it is a game.

Performance parity? Heck no, not until this bug with the GSP firmware is solved: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/538

My issue with skins is that it is completely immersion breaking. You have Homelander and Gaia running around Call of Duty now. It’s comical and just destroys my enjoyment of the game.

The skins get worse and worse because to continue the money machine they have to make more and more unique skins that just destroy the cohesion of the world they’ve built.

This. It all boils down to value for money. 5 dollars for a skin cosmetic is bullshit. 5 dollars or more for DLC with meaningful content is okay.

Valve should totally hook her up with one of those dev accounts that have access to games so she doesn’t have to pay for it themselves or get gifted them. She’s doing valuable work for the ecosystem.

Yeah, in a Reddit comment, Hector Martin himself said that the memory bandwidth on the Apple SIlicon GPU is so big that any potential performance problems due to TBDR vs IMR are basically insignificant.

…which is a funny fact because I had another Reddit user swear up and down that TBDR was a big problem and that’s why Apple decided not to support Vulkan and instead is forcing everyone to go Metal.

I’ve heard something about Apple Silicon GPUs being tile-based and not immediate mode, which means the Vulkan API is different compared to regular PCs. How has this been addressed in the Vulkan driver?

Huge fucking deal, especially for Nvidia users, but it is great for the entire ecosystem. Other OSes have had explicit sync for ages, so it is great for Linux to finally catch up in this regard.

You’re correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they’re slower code paths.

The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.

I’ve tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.

I love Nextcloud Talk, but my biggest annoyance with it is that text chats don’t properly scroll to the bottom when new messages come in.

No port forwarding though :(

I used to use Mullvad but after they disabled port forwarding I switched over to Proton.

Interesting solution! Thanks for the info. Seems like Nginx Proxy Manager doesn’t support Proxy Protocol. Lmao, the world seems to be constantly pushing me towards Traefik all the time 🤣

I truly believe the answer to this question is going to be yes around the May - June timeframe when Nvidia releases their explicit sync enabled drivers. All aboard the Wayland hype train babyyyy!

I see. And the rest of your services are all exposed on localhost? Hmm, darn, it really looks like there’s no way to use user-defined networks.

I am guessing you’re not running Caddy itself in a container? Otherwise you’ll run into the same real IP issue.

I see! So I am assuming you had to configure Nginx specifically to support this? Problem is I love using Nginx Proxy Manager and I am not sure how to change that to use socket activation. Thanks for the info though!

Man, I often wonder whether I should ditch docker-compose. Problem is there’s just so many compose files out there and its super convenient to use those instead of converting them into systemd unit files every time.

Yeah, I thought about exposing ports on localhost for all my services just to get around this issue as well, but I lose the network separation, which I find incredibly useful. Thanks for chiming in though!

Pasta is the default, so I am already using it. It seems like for bridge networks, rootlesskit is always used alongside pasta and that’s the source of the problem.

They’re at different layers of the audio stack though so not really replacing.

My biggest issue with Syncthing is that it becomes unusable for large amounts of data due to the lack of selective sync (ignore lists are cumbersome as hell) and lack of virtual file system support. I have about 8TB of data on my NAS that I want to access remotely and it is not feasible to have duplicate copies of that much data on all of my devices.