Besides the vendor, you can fingerprint the extensions list, as well as various limits https://browserleaks.com/webgl. Also webgl isn't fully deterministic across vendors (similar to audiocontext, which is affected by compiler/FPU implementations), so you'll get minor differences in output due to differences in rendering pipeline/implementation.
The comment timestamps already show how old the posts are[1]
Putting politics aside, technical chatter is scarce in large‑model discussions here.
Take the K3 release as a case study: out of more than 1,200 comments, how many actually delve into topics like LatentMoE, KDA, or attention residuals? And how many are offering guesses about per‑head Muon or SiTU?
Users interested in this should look at imageboards
Are you saying it's possible to detect VMs in the browser without using the WebGL vendor? Mind sharing some resources?