slickytail

Not really relevant in the case of embedding models. We might note that compressing a lossless PNG to 99% quality JPEG will also give you a different embedding. You don't care about bit for bit equality, just the distance in embedding space. And the same text embedded on CPU vs GPU will give very very similar embeddings.

You seem to misunderstand what full screen mode is. It doesn't just make the terminal fullscreen, it causes pi to maintain its own scrollback buffer and a UI around it, rather than letting the terminal emulator handle scrolling (ie, letting the session context actually live in the terminal history)

Reminder that job postings for jobs in California are legally required to include a salary range.

As a non Emacs user, I would be really interested in a full writeup of how this works.

Two different groups of people commenting different things.

In what sense is this 64KB? Clearly there's more than 64KB of code in the repo. And since it's typescript it's not like there's a binary that could be 64KB.

In a discrete Fourier transform, the number of frequencies you get out is the number of datapoints you have as input. This is because any frequencies higher than that are impossible to know (ie, they are above the sampling frequency).

But in the continuous Fourier transform, the output you get is a continuous function that's defined on the entire real line.

I think the biggest sign of a potential crash is that Meta has frozen AI hiring. Such a quick reversal from just a few months ago.

The relative unimportance of the exact SDPA attention in use in modern transformers is already known: https://arxiv.org/abs/2111.11418

The FFN, normalization, and residual connections are absolutely irreplaceable -- but attention can be replaced with almost any other layer that shares information between tokens, such as pooling, convolution, random mixing, etc.

The linked wikipedia article below says that they asked you for your email password specifically -- is there any evidence that they would try to use your linkedin password itself?

Generally the problem with this type of argument is that the two sources are not volume-matched. Try out an ABX test here, of lossless vs various lossy codecs: https://abx.digitalfeed.net/