Is the camera capture support on mobile devices (perhaps loads video frames into texture map)? I assume this is what webxr is doing somehow?
Chrome ships WebGPU
301–310 of 405 posts
Re: Chrome ships WebGPU
#302This is very exciting! (I had suspected it would slip to 114) WebGPU implementations are still pretty immature, but certainly enough to get started with. I've been implementing a Rust + WebGPU ML runtime for the past few months and have enjoyed writing WGSL. I recently got a 250M parameter LLM running in the browser without much optimisation and it performs pretty well! ( https://twitter.com/fleetwood___/status/16384…
Oh great!
I am one of the contributors for Burn (Rust Deep Learning Framework). We have a plan adding a WebGPU backend (https://github.com/burn-rs/burn/issues/243).
Here is more about the framework Burn: https://burn-rs.github.io/
Re: Chrome ships WebGPU
#303I remember when WebRTC was introduced, it was found that it became very popular and was used by almost every page. But closer inspection showed that its use was to get user's IP address for better fingerprinting. I predict that WebGL/WebGPU will be mainly used for the same purposes. Nobody needs new fancy features, what people really need is more reliable fingerprinting (this is proven by number of uses of WebRTC for…
I was reading that WebGPU leaves you open to fingerprinting by your hardware info, particularly your GPU. It seems that it is even possible to distinguish between GPUs of the same model through tolerances in frequency.
Re: Chrome ships WebGPU
#304Earlier quoted context omitted.
There are too many APIs that need to put behind permissions for permissions to be useful. No idea how to solve this though.
i want the chrome apps model to come back - put your permission requests in a manifest, and when the user clicks and install button the app gets its permissions. so "web apps" that the user cares enough about to install get useful features, but pages that you just visit briefly don't.
> i want the chrome apps model to come back - put your permission requests in a manifest, and when the user clicks and install button the app gets its permissions.
So you will get the Android case where flashlight apps where asking for everything, including location data and contact access, and people were giving it to them
Re: Chrome ships WebGPU
#305Earlier quoted context omitted.
I can only quote Johnathan Nightingale, former executive of Mozilla, from his thread on how Google was sabotaging Firefox [1]: "The question is not whether individual sidewalk labs people have pure motives. I know some of them, just like I know plenty on the Chrome team. They’re great people. But focus on the behaviour of the organism as a whole. At the macro level, google/alphabet is very intentional." [1] Thread: h…
That whole Twitter thread says nothing about fingerprinting or privacy. The first comment is close to gibberish, but seems to be mostly about some kind of Google office development project in Toronto. You are literally following the parody argument schema that I mentioned in my previous comment. You make some vague insinuations that Google is evil, then attribute everything it does to non-specific evil motivations. E…
> That whole Twitter thread says nothing about fingerprinting or privacy.
I should've been more clear. In this case I was responding to this: "The reasoning here seems to be something like "Google is evil; X is an evil reason for doing Y; therefore Google must have done Y because of X". It's not a great argument."
> You are literally following the parody argument schema that I mentioned in my previous comment.
Because you have to look at the behaviour of the organism as a whole. If the shoe fits etc.
Re: Chrome ships WebGPU
#306Earlier quoted context omitted.
“The web” should not first and foremost protect anonymity. It should do what humans need it to do ideally while keeping users private and secure. If there’s a concern, my browser should ask me if I’m willing to share potentially sensitive information with a product or service. I fucking hate this weird angsty idea that the web is only designed for anonymous blobs and trolls.
Letting advertisers identify you through some web accessible GPUs interface so they can track your every move and sell the data to all comers … won’t help you fight anonymous online trolls.
So let me opt in to it rather than neuter it.
Re: Chrome ships WebGPU
#307Earlier quoted context omitted.
Google doesn't benefit because Google has committed not to fingerprint for ad targeting, but their competitors do.
You've got it backwards.
Google Ads, 2020-07-31:
What is not acceptable is the use of opaque or hidden techniques that transfer data about individual users and allow them to be tracked in a covert manner, such as fingerprinting. We believe that any attempts to track people or obtain information that could identify them, without their knowledge and permission, should be blocked. We’ll continue to take a strong position against these practices. -- https://blog.google/products/ads-commerce/improving-user-pri...
Google Ads, 2021-03-03:
Today, we’re making explicit that once third-party cookies are phased out, we will not build alternate identifiers to track individuals as they browse across the web, nor will we use them in our products. -- https://blog.google/products/ads-commerce/a-more-privacy-fir...
(I used to work on ads at Google, speaking only for myself)
Re: Chrome ships WebGPU
#308This is very exciting! (I had suspected it would slip to 114) WebGPU implementations are still pretty immature, but certainly enough to get started with. I've been implementing a Rust + WebGPU ML runtime for the past few months and have enjoyed writing WGSL. I recently got a 250M parameter LLM running in the browser without much optimisation and it performs pretty well! ( https://twitter.com/fleetwood___/status/16384…
> WebGPU ML runtime oh cool! will this be numpy-like or will it have autograd as well? We're looking around for a web backend for shumai[1] and the former is really all we need :) [1]: https://github.com/facebookresearch/shumai
Autograd would be a whole new adventure, just inference for now :).
Re: Chrome ships WebGPU
#309This is very exciting! (I had suspected it would slip to 114) WebGPU implementations are still pretty immature, but certainly enough to get started with. I've been implementing a Rust + WebGPU ML runtime for the past few months and have enjoyed writing WGSL. I recently got a 250M parameter LLM running in the browser without much optimisation and it performs pretty well! ( https://twitter.com/fleetwood___/status/16384…
Looking forward to your WebGPU ML runtime! Also, why not contribute back to WONNX? ( https://github.com/webonnx/wonnx )
Hi Tommy!
I sent you an email a few weeks back - would be great to chat!
WONNX is a seriously impressive project. There is a few reason I didn't just contribute back to WONNX:
1. WONNX does not parse the ONNX model into an IR, which I think is essential to have the freedom to transform the model as required.
2. When I started, WONNX didn't seem focused on symbolic dimensions (but I've seen you shipping the shape inference recently!).
3. The code quality has to be much higher when it's open source! I wanted to hack on this without anyone to please but myself.
Re: Chrome ships WebGPU
#310This is very exciting! (I had suspected it would slip to 114) WebGPU implementations are still pretty immature, but certainly enough to get started with. I've been implementing a Rust + WebGPU ML runtime for the past few months and have enjoyed writing WGSL. I recently got a 250M parameter LLM running in the browser without much optimisation and it performs pretty well! ( https://twitter.com/fleetwood___/status/16384…
How would WebGL matmul fare in comparison?
This blog post breaks it down pretty well: https://pixelscommander.com/javascript/webgpu-computations-p...