• 1 Post
  • 81 Comments
Joined 5 months ago
cake
Cake day: March 22nd, 2024

help-circle








  • They can cycle a some biases (dozens?) and test them all. Detokenization is super cheap to run, its not AI or anything.

    I’m trying to think of a good analogy for how this would work, and I kinda came up with one. This would be kinda like an image encoder that biases itself towards coding RGB values (0-255) as even numbers. Subtly, say 30% odd 70% even.

    That’s totally imperceptile to humans. And even a “small” sample of the image would carry this bias if pasted into a larger image verbatim, since the sample size is so large (just as the sample size for a bunch of tokens in text is pretty big.

    And I’m not saying its fullproof… but if thats indeed what they’re doing, I think its a decent way to detect “lazy” OpenAI abusers who aren’t working so hard to scramble and defeat it.




  • This has been known in the ML space forever. LLMs don’t actually output words/tokens, but probabilities for a long list of tokens, and the sampler picks one (usually the mostl likely token). And if you arbitrarily weigh these probabilities (eg 50% of possible token outputs are more likely than the other 50%, as a random example), it creates a “signature” in any text thats easy to measure. The sampler randomizes it a tiny bit, but that averages out in long texts.

    It’s defeatable. I’m sure if you maken enough OpenAI queries, you can find the bias. I think a paper already tackled this. But this likely will stop the lazy absures, aka 99% of abusers, who should just use some other LLM if they really care.

    Another open secret in LLM land is that OpenAI is actually falling behind open research efforts, hence its hilarious it took them this long to implement something so simple.



  • Mozilla management was paid millions to develop a new “vision” of a theoretical future with AI chatbots

    Is this llamafile?

    The thing about LLMs is that no one knows how to write the ultra low level optimizations/runtimes, so they port others (llamafile largely borrows from llama.cpp AFAIK, albeit with some major contributions from their own devs).

    Performance is insanely critical because they’re so darn hard to run, and new models/features come out weekly which no sane dev can keep up with without massive critical mass (like HF Transformers, mainly, with llama.cpp barely keeping up with some major jank).

    So… I’m not sure what Mozilla is thinking here. They don’t have many of those kind of devs, they don’t have a GPU farm, they’re not even contributing to promising webassembly projects like mlc-llm. They’re just one of a bazillion companies that was ordered to get into AI with no real purpose or advantage. And while Gemma 2B may be the “first” model that’s kinda OK on average PCs, we’re still a long way away from easy mass local deployment.

    Anyway, what I’m getting at is that I’m a local LLM tinkerer, and I’ve never touched or even looked at anything from Mozilla. The community would have if anything of theirs was super useful.