Live data from Hacker News

No AI* Here – A Response to Mozilla's Next Chapter

waterfox.com

311–320 of 344 posts

Re: No AI* Here – A Response to Mozilla's Next Chapter

#311
post #291

Earlier quoted context omitted.

You're making a huge leap here. I'm raising only had signaling intentionally rather than automatically has made me pay more attention to others on the road. You're claiming that that action which has proven to make me pay closer attention will kill someone.

There is no such thing as not signaling. By not using the turn signal, you are lying to anyone around that you might not see, signaling that you are going straight forward when you aren't.

Spot on.

Re: No AI* Here – A Response to Mozilla's Next Chapter

#312

Earlier quoted context omitted.

That's true, but as a Waterfox user, I'm not worried! If firefox really completely fails, and nobody is able to continue the open source project, I'll just find a new browser. That's not a huge hassle- Waterfox does what I need in the here and now, that's my only criterion.

> I'll just find a new browser. The problem is that if Firefox dies, there are no browsers left. I don't want to use a re-skin of Chrome.

Luckily there is ladybird in the making

Re: No AI* Here – A Response to Mozilla's Next Chapter

#313
post #255
post #234

Earlier quoted context omitted.

I think the point here is that, while such a translation wouldn't be admissible in court, many of us already used machine translation to read some legal agreement in a language we don't know.

> many of us already used machine translation to read some legal agreement in a language we don't know. Have we? Most of us? Really? When?

Most people don't have to deal with documents in foreign languages in the first place.

But for those that do, yes, machine translation use is widespread if only as a first pass.

Re: No AI* Here – A Response to Mozilla's Next Chapter

#314
post #267

Earlier quoted context omitted.

I mean, fluid dynamics is an unsolved issue. But even so we know *considerably* less about how LLMs work in functional terms than about how combustion engines work.

I outright disagree; we know how LLMs work

We know how neural nets work. We don't know how a specific combination of weights in the net is capable of coherently asking questions asked in a natural language, though. If we did, we could replicate what it does without training it.

Re: No AI* Here – A Response to Mozilla's Next Chapter

#315

Earlier quoted context omitted.

This is not a thread comparing Mozilla to Google. This is a thread where we worry about how a non google browsing alternative stays alive. Of course none of us posting here trusts Google.

> we worry about how a non google browsing alternative stays alive > This is just FUD. Ublock Origin is still working and will be working. Full customization is still there and isn't going away.

> This is just FUD. Ublock Origin is still working

Correct.

> and will be working.

How do you know?

> Full customization is still there

Correct.

> and isn't going away.

How do you know?

How do you know this new "AI" CEO won't let both support for Manifest V2 and extensive settings rot because "AI can do it for you" for example?

Or as I said earlier, because they'll run out of money to pay for non "AI" features?

Re: No AI* Here – A Response to Mozilla's Next Chapter

#316

Earlier quoted context omitted.

> we worry about how a non google browsing alternative stays alive > This is just FUD. Ublock Origin is still working and will be working. Full customization is still there and isn't going away.

> This is just FUD. Ublock Origin is still working Correct. > and will be working. How do you know? > Full customization is still there Correct. > and isn't going away. How do you know? How do you know this new "AI" CEO won't let both support for Manifest V2 and extensive settings rot because "AI can do it for you" for example? Or as I said earlier, because they'll run out of money to pay for non "AI" features?

> How do you know?

Extrapolation. Also, because it's FLOSS and can be modified by anyone.

Re: No AI* Here – A Response to Mozilla's Next Chapter

#317

Earlier quoted context omitted.

By not signaling you are robbing others on the road the opportunity to avoid a potential accident should you not have seen them. It's maximum selfish fuck everyone else asshole behavior.

Did you read any of my comments? I signal when anyone is around and don't signal when there is no one to notify of my upcoming turn.

Yes, I read your comments, but you apparently didn’t read mine. I specifically said for the case where you don’t notice someone.

It’s pretty clear that you believe that you are perfect and will never make a mistake. It’s at the very least arrogant if not outright delusional.

Re: No AI* Here – A Response to Mozilla's Next Chapter

#318
post #174
post #151

Earlier quoted context omitted.

I'd wager there's 95% of the benefit for 0.1% of the CPU cycles just by having a "search transcript for term" feature, since in most of those cases I've already got a clear agenda for what kind of information I'm seeking. Many years ago I make a little proof-of-concept for displaying the transcript (closed captions) of a YouTube video as text, and highlighting a word would navigate to that timestamp and vice-versa. S…

Searching the transcript has the problem of missing synonyms. This can be solved by the one undeniably useful type of AI: embedding vector search. Embeddings for each line of the transcript can be calculated in advance and compared with the embeddings of the user's search. These models need only a few hundred million parameters for good results.

Yeah, but they fail surprisingly hard on grepping. So the best systems use both simultaneously:

https://www.anthropic.com/engineering/contextual-retrieval

Re: No AI* Here – A Response to Mozilla's Next Chapter

#319
post #264

Earlier quoted context omitted.

It's ridiculous that all those things aren't just config in a plain text file.

I think you can with a user.js file, unless they changed that?

Nah, [BetterFox](https://github.com/yokoffing/Betterfox) still works fine

Re: No AI* Here – A Response to Mozilla's Next Chapter

#320
post #267

Earlier quoted context omitted.

I outright disagree; we know how LLMs work

We know how neural nets work. We don't know how a specific combination of weights in the net is capable of coherently asking questions asked in a natural language, though. If we did, we could replicate what it does without training it.

> We know how neural nets work. We don't know how a specific combination of weights in the net is capable of coherently asking questions asked in a natural language, though.

these are the same thing. the neural network is trained to predict the most likely next word (rather token, etc.) — that’s how it works. that’s it. you train a neural network on data, it learns the function you trained it to, it “acts” like the data. have you actually studied neural networks? do you know how they work? I’m confused why you and so many others are seemingly so confused by this. what fundamentally are you asking for to meet the criteria of knowing how LLMs work? some algorithm that can look at weights and predict if the net will output “coherent” text?

> If we did, we could replicate what it does without training it.

not sure what this is supposed to mean

Post reply on HN