131–140 of 194 posts
Alright, here’s a take I haven’t seen in this thread yet: how could this be used for fingerprinting, beyond an existence check for the API itself?
And that made me realize that Google might start training it with your browser history. Anything is possible at this point.
Man, the bloat is unreal. Can't we just have a browser without all the extra crap?
This doesn't seem useful unless it's something standardized across browsers. Otherwise I'd still need to use a plugin to support safari, etc. It seems like it could be nice for something like a bookmarklet or a one-off script, but I don't think it'll really reduce friction in engaging with Gemini for serious web apps.
Browser extensions should be able to shim or even overwrite the `.ai` object in the window, so it should be possible to add ollama etc to all browsers through extensions with the same API, making it a defacto standard It should be simple enough to do that I believe at least 3-5 people are going to be doing this if it's not done already Hell, if nobody does it I will do it
If this is the API that Google are going with here: const model = await window.ai.createTextSession(); const result = await model.prompt("3 names for a pet pelican"); There's a VERY obvious flaw: is there really no way to specify the model to use? Are we expecting that Gemini Nano will be the one true model, forever supported by this API baked into the world's most popular browser? Given the rate at which models are…
I'm pretty sure that with time, they will be forced to let users choose the model. Just like it happened with the search engine...
Going a touch further: make it a pluggable local model. Browser fetches the first 10 links from google in the background, watches the YouTube video, hides the Google ads, presents you with the results. Now not only can Google front the web pages who feed them content they make summaries from, but the browser can front Google. “Your honour, this is just what Google has been saying is a good thing. We just moved it to…
So they don't standardize things anymore? Look at WebNN [1]. It's from Microsoft and is basically DirecttML but they at least pretend to make it a Web thing. The posture matters. Apple tried to expose Metal through WebGPU [2] then silent-abandoned it. But they had the posture, and other vendors picked it up and made it real. That won't happen to window.ai until they stop sleepwalking. [1] https://www.w3.org/TR/webnn/…
It's a very experimental API and that's why it's only behind a flag and not available to the general web for people to use. We will be taking these through the standards process (e.g the higher level translate API - https://github.com/WICG/translation-api )
https://developer.chrome.com/docs/ai/built-in
This doesn't seem useful unless it's something standardized across browsers. Otherwise I'd still need to use a plugin to support safari, etc. It seems like it could be nice for something like a bookmarklet or a one-off script, but I don't think it'll really reduce friction in engaging with Gemini for serious web apps.
Browser extensions should be able to shim or even overwrite the `.ai` object in the window, so it should be possible to add ollama etc to all browsers through extensions with the same API, making it a defacto standard It should be simple enough to do that I believe at least 3-5 people are going to be doing this if it's not done already Hell, if nobody does it I will do it
I mostly think it's an interesting concept that can allow many interesting user experiences. At the same time, it is a major risk for browser compatibility. Despite many articles claiming otherwise, I think we mostly avoided repeating the "works only on IE6" situation with chrome. Google did kinda try at times, but most things didn't catch on. This I think has the potential to do some damage on that front.
I'm looking forward to see a cross-browser polyfill, possibly as a web extension.