Upgrading to 42 on my Kinoite work laptop is too easy it's basically boring. Suffering from success .

Quoting: ZlopezI tried the Monster Hunter World and after first hour it started to feel like just a grind. The start was awesome cinematic epic story introduction, but after that you will get so many confusing things to do and for everything you need to grind your way to it.

If you hope for some epic story like God of War you will not find it here, even the battles with the monsters weren't that interesting. Most of the time it feels like Live service game, but without trying to get more money from you (I can see how this could be easily added to the game).

• 1. The game is grindy by design, and designed to be an enjoyable grind with a strong focus on the enjoyment arising from the sense of progression, which is impeded for new players in the case of see 2.


• 2. Did you use the Guardian Armor and Weapons? Those will kill the experience for new players in particular because you don't get into the progression feedback loop. The Guardian equipment is intended for returning or replaying hunters that want to rush into Iceborne.


• "Given the opportunity, players will optimise the fun out of a game."


• 3. The story was never the focus, the early games didn't even have a story to speak of outside of lore bits sprinkled into item descriptions and similar.

I should also note that the next major driver version (525) will include a partial fix for PRIME systems only. In that case, since Xwayland will be using the open-source drivers which do support general-purpose implicit sync, we only need to ensure we wait for / signal the implicit fence during presentation which can be done in a performant manner.

Quoting: anewsonI wonder if someone could dumb this down a bit; on the driver-side issues things don't actually seem that bad. VDPAU is nice but there are other decoders, and as far as I understand it everyone has issues with screen capture on wayland (sway does, anyway). I don't have VR, and I don't understand the remaining driver-side things.

I imagine the nvidia team is inclined to present their driver as not the stumbling block, insofar as that's possible, and I'm wondering if that's a fair takeaway.

Anyway, are you really a Linux nerd if you don't distro-hop at least once a year?

Quoting: marcus

Quoting: HoolyDoesn't matter, the private key has to get there somehow. And how would you verify server-side that the client uses a specific individual TPM? The client could just lie to the server and then reroute the attestation request again.

The private key is generated by the TPM and never leaves it. The public key transmitted to the server for encryption is signed with the private key from the TPM vendor and thus cannot be "spoofed". The server knows all "known good" TPM vendors and their (public) signing keys.

Quoting: HoolyIf your security model involves placing trust onto the client in any shape or form, then it is deeply flawed, period.

Then FPS are basically impossible to make cheat proof. You *need* to trust the client to actually render walls ...

Quoting: marcusThe standard way to combat this in a normal TPM / remote attestation scenario is to encrypt the communication with a key where only the TPM has the private key to decrypt it. So only the trusted non-manipulated software can read the communicated data. However, routing FPS gaming network traffic through a TPM admittedly is prohibitive ;)