IIRC it just hardcodes the release date and complains if it is more than 2 or 3 years later.
It’s somewhat reasonable. I agree Debian should patch out phone-home and autoupdate (aka developer RCE). They should have left the xscreensaver local-only warning in, though. It is not a privacy or system integrity issue.
jwz however is also off the rails with entitlement.
They’re both wrong.
People unfamiliar with code base can easily screw it, here is SimplePie example:
https://news.ycombinator.com/item?id=44061563
I don't think that approach is reasonable. When you are effectively making a fork, don't freeload on existing project name and burden him with problems you cause.
No, the most important thing about Denuvo is that PC gamers are forced to upgrade their hardware because Denuvo is such a performance hog. All you have to do is wait until Denuvo is stripped and the game will run much faster.
Frankly, it wouldn't surprise me if there's a conspiracy between Denuvo and Intel/AMD/NVIDIA where Denuvo goes out of their way to hurt performance on a really popular title, thus forcing people to upgrade.
Idiot writers at gaming websites claim a new patch to a game that's been out for a while has "optimizations" and lauds the developers for slaving away to make an already-finished game faster. The reality is that they just stripped out Denuvo.
> One can see that Denuvo does indeed intervene from time to time, but what one can clearly see: It doesn’t do that very often, definitely not every frame.
> It’s only once every few seconds. Even less, sometimes it doesn’t do anything.
> To me personally, it tells that Denuvo executes checks so infrequently, that the likelyhood of it causing major performance issues seems rather low.
https://momo5502.com/posts/2024-03-31-bypassing-denuvo-in-ho...