Comment by popcar2
2 hours ago
Been playing it the last few days along with a few races with friends, it's pretty wild that this is even possible. The only downside is that this website isn't legal and now that it's popular it's probably getting a takedown soon.
But NFSU2 is abandonware that isn't available anymore so I hope they just leave it alone.
Also FYI for people on Linux, you need to enable unsafe WebGPU features for this to work. I use this command to make it work on Chromium:
chromium --enable-unsafe-webgpu --ozone-platform=x11 --use-angle=vulkan --enable-features=Vulkan,VulkanFromANGLE
>But NFSU2 is abandonware that isn't available anymore so I hope they just leave it alone.
There is a concept in US law: a trademark can be considered abandoned if the owner does not want to get into legal fights over its use. I am not a lawyer, but I guess something like this can be said about NFS trademark and the game's copyright in general - even if EA doesn't want to fight over this, they should, otherwise they risk losing/diminishing the value of IP. For a company which has IP as its main asset, it'd be bad.
Every time this is brought up I always think why can't the company setup a simple website where you pay 1 dollar and get a license?
Games are bundles of licenses themselves. That music costs money, as do other assets and sometimes engines. And over time some of those licenses can expire or require renegotiation. Sometimes it's easier to just stop selling something than figure all that out.
When you go to enable "Unsafe WebGPU Support" it says the following:
"Convenience flag for WebGPU development. Enables best-effort WebGPU support on unsupported configurations and more! Note that this flag could expose security issues to websites so only use it for your own development."
Can someone who knows about this stuff please guide us in terms of what sort of security risk we would would be exposing ourselves to?
Thanks.
> Also FYI for people on Linux, you need to enable unsafe WebGPU features for this to work.
Browsers on macOS do not require you to enable this feature. Does it mean it's on by default?!
I was gonna respond with the generic large swath of unverified code running on your machine, but I realized your question is more specific and more interesting. If anyone knows, I would love to hear an answer on this as well.
Being new, largely untested code paths in the browser, it's very possible for it to have buffer overflow defects that could be exploited to execute arbitrary code on your system. So, basically, literally anything could happen.
[flagged]