By now you've all probably heard about the latest shenanigans from Google and their love for in-browser AI features (if you don't, this is the story: https://www.theverge.com/tech/924933/google-chrome-4gb-gemini-nano-ai-features).
-
@tay @lazza @Vivaldi Surely there will be some people who use it. We can't eliminate them. But there is absolutely no place for it in our browsers, in software we use, etc. much less giving websites we visit backdoors to our data and interactions via some "AI API".
Once the bubble finishes imploding (it's well along the way already), there will not be new gigantic models. The astronomical costs don't justify it. They don't even justify continuing to offer the existing ones at affordable prices. The existing public models you can run client-side will of course still exist but will be increastingly outdated. This will not be a complete wipe-out, but it will be close.
> much less giving websites we visit backdoors to our data and interactions via some "AI API".
I'm not entirely up to date on the Chrome AI APIs, but I was under the impression it's just stuff like a translation API, text summarisation, etc. If there is actually stuff that can leak information like such, I agree that is a genuine concern
And regarding the implosion and lack of future development, good. I sincerely hope that happens sooner rather than later. But I feel that while we are still in the VC money burning phase, we should encourage development of on device models to redirect resources away from cloud models, so that, when the funding dries up, we will have something we can use on our own terms, just so we would have SOMETHING to come out of the VC funded wrecking ball instead of just the destruction
-
By now you've all probably heard about the latest shenanigans from Google and their love for in-browser AI features (if you don't, this is the story: https://www.theverge.com/tech/924933/google-chrome-4gb-gemini-nano-ai-features).
Our team has been inspecting the Chromium code and disabling stuff from the very first version of Vivaldi (we have some posts about this in our blog, such as https://vivaldi.com/blog/news/alert-no-google-topics-in-vivaldi/ or https://vivaldi.com/blog/no-google-vivaldi-users-will-not-get-floced/).
We've also been very outspoken about our dislike of the built-in AI trend in the browser industry, but in case there's still any doubts: yes, we disable all Gemini-related features, and we've been doing it for a while.
@Vivaldi I would not call it „Feature“.
-
> much less giving websites we visit backdoors to our data and interactions via some "AI API".
I'm not entirely up to date on the Chrome AI APIs, but I was under the impression it's just stuff like a translation API, text summarisation, etc. If there is actually stuff that can leak information like such, I agree that is a genuine concern
And regarding the implosion and lack of future development, good. I sincerely hope that happens sooner rather than later. But I feel that while we are still in the VC money burning phase, we should encourage development of on device models to redirect resources away from cloud models, so that, when the funding dries up, we will have something we can use on our own terms, just so we would have SOMETHING to come out of the VC funded wrecking ball instead of just the destruction
-
@tay Regarding the second part, we DON'T WANT "something we can use on our own terms" from "AI". There is nothing useful to be had here. It's all malicious, every last bit of it. The only thing "high quality" local models would enable is massive automated spam, scam, and deception/disinformation campaigns without the perpetrators having to pay for it.
-
-
@tay Regarding the second part, we DON'T WANT "something we can use on our own terms" from "AI". There is nothing useful to be had here. It's all malicious, every last bit of it. The only thing "high quality" local models would enable is massive automated spam, scam, and deception/disinformation campaigns without the perpetrators having to pay for it.
@tay We specifically WANT these awful things to depend on the subsidized massive data centers, so that when the bills come due and it all crashes, as much as possible is GONE.
-
@Vivaldi will you consider making it optional rather than fully removing it? Like an opt-in feature?
I know Vivaldi is very friendly when it comes to user choice.
@lazza Can't see why they would when they're opposed to integrating any form of LLM into the browser, they are friendly but they're not about to renegotiate on their principles either.
-
@lazza @kimcrawley What do you expect when you show up in someone's mentions advocating for the "AI" industry's interests?
@dalias well, if I did that, maybe... but given that I didn't, the point is freaking moot.
I asked Vivaldi what they plan to do about users' choice. Given that Vivaldi is one of the most customizable browser in the world, that is a very valid question.
Anyway, it's always funny to see how anti-AI zealots get triggered. More or less the same as far-right extremists when we try to explain to them that immigrants and LGBT individuals are people, too.
-
@dalias well, if I did that, maybe... but given that I didn't, the point is freaking moot.
I asked Vivaldi what they plan to do about users' choice. Given that Vivaldi is one of the most customizable browser in the world, that is a very valid question.
Anyway, it's always funny to see how anti-AI zealots get triggered. More or less the same as far-right extremists when we try to explain to them that immigrants and LGBT individuals are people, too.
@lazza Wow, showing your true colors...
-
By now you've all probably heard about the latest shenanigans from Google and their love for in-browser AI features (if you don't, this is the story: https://www.theverge.com/tech/924933/google-chrome-4gb-gemini-nano-ai-features).
Our team has been inspecting the Chromium code and disabling stuff from the very first version of Vivaldi (we have some posts about this in our blog, such as https://vivaldi.com/blog/news/alert-no-google-topics-in-vivaldi/ or https://vivaldi.com/blog/no-google-vivaldi-users-will-not-get-floced/).
We've also been very outspoken about our dislike of the built-in AI trend in the browser industry, but in case there's still any doubts: yes, we disable all Gemini-related features, and we've been doing it for a while.
@Vivaldi Thank you.
-
@tay Regarding the second part, we DON'T WANT "something we can use on our own terms" from "AI". There is nothing useful to be had here. It's all malicious, every last bit of it. The only thing "high quality" local models would enable is massive automated spam, scam, and deception/disinformation campaigns without the perpetrators having to pay for it.
@dalias I mean, I feel like we're past that point, so unless you EMP every hard drive with a .GGUF file on it, we will continue to see slop articles clogging up search results. Which is deeply frustrating but, given that I've found _some_ use from LLMs (admittedly not much, and wouldn't complain too much if they did all just vanish), I would like to keep those on my own terms
But anyway, I think I've said as much as I care to for now, I thank you for being at least willing to hear what I have to say, but in all honesty I am overdue for some rest, and wouldn't mind doing something more productive. Maybe I could update musl et al on all my systems, I'm sure my horrible patching hygiene isn't doing your good work justice.
-
-
@Vivaldi I’d like to be able to hide the AI summary on Google’s search results page. This feature is very inaccurate and often gets things wrong. Plus, there’s no option to turn it off. It forces the summary onto users who don’t want it and wastes electricity.
@kyu3a unfortunately that's because you visit google.com. If you don't visit google.com this wouldn't be a problem.
-
By now you've all probably heard about the latest shenanigans from Google and their love for in-browser AI features (if you don't, this is the story: https://www.theverge.com/tech/924933/google-chrome-4gb-gemini-nano-ai-features).
Our team has been inspecting the Chromium code and disabling stuff from the very first version of Vivaldi (we have some posts about this in our blog, such as https://vivaldi.com/blog/news/alert-no-google-topics-in-vivaldi/ or https://vivaldi.com/blog/no-google-vivaldi-users-will-not-get-floced/).
We've also been very outspoken about our dislike of the built-in AI trend in the browser industry, but in case there's still any doubts: yes, we disable all Gemini-related features, and we've been doing it for a while.
@Vivaldi I went ahead an updated the flags suggested in the news articles, anyway. An extra bit of guard never hurt!
-
sure, some people choose AI
some people choose not to get vaccinated
rather the same phenomenon to me: poor choices
and likewise, you don't have to use Vivaldi. that's your real choice here
Vivaldi has ripped out the AI cruft, which most of us cheer, so go use your Chrome and enjoy yourself elsewhere
you dig?
-
sure, some people choose AI
some people choose not to get vaccinated
rather the same phenomenon to me: poor choices
and likewise, you don't have to use Vivaldi. that's your real choice here
Vivaldi has ripped out the AI cruft, which most of us cheer, so go use your Chrome and enjoy yourself elsewhere
you dig?
@benroyce @Vivaldi you should open the "Privacy and Security" panel in the settings... you will find some surprises. Like the fact that some Google services are enabled by default in Vivaldi, unless the user opts out.
And you are getting mad because one person is suggesting that LLM integration should be opt-in.
Priorities, I guess.
-
@benroyce @Vivaldi you should open the "Privacy and Security" panel in the settings... you will find some surprises. Like the fact that some Google services are enabled by default in Vivaldi, unless the user opts out.
And you are getting mad because one person is suggesting that LLM integration should be opt-in.
Priorities, I guess.
"And you are getting mad because one person is suggesting that LLM integration should be opt-in"
yes, precisely. and i'm quite comfortable with that hard stance
-
By now you've all probably heard about the latest shenanigans from Google and their love for in-browser AI features (if you don't, this is the story: https://www.theverge.com/tech/924933/google-chrome-4gb-gemini-nano-ai-features).
Our team has been inspecting the Chromium code and disabling stuff from the very first version of Vivaldi (we have some posts about this in our blog, such as https://vivaldi.com/blog/news/alert-no-google-topics-in-vivaldi/ or https://vivaldi.com/blog/no-google-vivaldi-users-will-not-get-floced/).
We've also been very outspoken about our dislike of the built-in AI trend in the browser industry, but in case there's still any doubts: yes, we disable all Gemini-related features, and we've been doing it for a while.
@Vivaldi why do you choose to fight with your foundational technology instead of rolling your own? I refuse to use anything Chromium solely so that there are other engines that may survive, why don't you?
-
-
R relay@relay.mycrowd.ca shared this topic
-
By now you've all probably heard about the latest shenanigans from Google and their love for in-browser AI features (if you don't, this is the story: https://www.theverge.com/tech/924933/google-chrome-4gb-gemini-nano-ai-features).
Our team has been inspecting the Chromium code and disabling stuff from the very first version of Vivaldi (we have some posts about this in our blog, such as https://vivaldi.com/blog/news/alert-no-google-topics-in-vivaldi/ or https://vivaldi.com/blog/no-google-vivaldi-users-will-not-get-floced/).
We've also been very outspoken about our dislike of the built-in AI trend in the browser industry, but in case there's still any doubts: yes, we disable all Gemini-related features, and we've been doing it for a while.
@Vivaldi Thank you! This is why Vivaldi is my browser of choice. keep up the good work!
