5.6 Luna was already discounted at half the price on OpenRouter. Looks like they made it permanent.
76 karma · joined July 2, 2012
What they're proposing now, is voluntarily staggering the pace of development.
IMO, we don't need to trust Dario or his bedfellows, to do this out of their goodness of their heart. Even assuming (for good reasons) that they are selfish and care only about short-term profits for their investors, this is still purely a business decision. The exponential pace of AI and its impacts ARE short-term. And so, the negative consequences that they might face is also short-term.
For the large majority of users, phones are THE primary (if not only) device for their interaction with the internet. You can complain "them-lazy-brainrotting-GenZs" but some people don't have a choice. There are plenty of countries where a smartphone is the cheapest internet enabled device that a person can afford.
Secondly, the UX for "web browsing" on the phone is strictly worse compared to (well-made) apps. In fact, apps are the reason for the explosion in popularity of smartphones. And also the reason only android and iphone have survived the OS race (see windows phone and linux phones). So — much to my own disappointment — it does make sense for companies to treat mobile (app) users as first class citizens. You need to understand that you are not the target user anymore. And, yes it sucks.
That said, it does not justify the gradual enshittification, dark patterns and dopamine hacking that have been normalized in modern apps.
I installed it and it's none of that. It is a mere wrapper around small local LLM models. And, it's not even multi-modal! Anyone could've one-shotted this in Claude in an hour (I'm not exaggerating).
What's the target audience here? Your average person doesn't care about the privacy value proposition (at least not by severely sacrificing chat model's quality). And users who do want that control can already install LMStudio/Llama.cpp (which is dead simple to setup).
The actual release product should've been what's described in "What's next" section.
> Instead of general chat, we shape Ensu to have a more specialized interface, say like a single, never-ending note you keep writing on, while the LLM offers suggestions, critiques, reminders, context, alternatives, viewpoints, quotes. A second brain, if you will.
> A more utilitarian take, say like an Android Launcher, where the LLM is an implementation detail behind an existing interaction that people are already used to.
> Your agent, running on your phone. No setup, no management, no manual backups. An LLM that grows with you, remembers you, your choices, manages your tasks, and has long-term memory and personality.
> It’s doubly hard to distinguish valid statements from invalid ones when you don’t have any examples labeled as invalid. But even with labels, some errors are inevitable. To see why, consider a simpler analogy. In image recognition, if millions of cat and dog photos are labeled as “cat” or “dog,” algorithms can learn to classify them reliably. But imagine instead labeling each pet photo by the pet’s birthday. Since birthdays are essentially random, this task would always produce errors, no matter how advanced the algorithm.
> The same principle applies in pretraining. Spelling and parentheses follow consistent patterns, so errors there disappear with scale. But arbitrary low-frequency facts, like a pet’s birthday, cannot be predicted from patterns alone and hence lead to hallucinations. Our analysis explains which kinds of hallucinations should arise from next-word prediction. Ideally, further stages after pretraining should remove them, but this is not fully successful for reasons described in the previous section.
It is a relief to hear that I'm not alone in experiencing this.
Lately, I've been realising that it might be because I'm neurodivergent (as to the exact pathology, I can only guess it's in the spectrum of ADHD). It'd probably explain a lot of things in my life.
That sounds careless. Any such change would need to have a impact analysis (which should be part of the team/org/company's SDLC). In this case, communication should be sent out to the clients of that endpoint, with a reasonable deadline, before enforcing any rate-limit.