Your daily dose of chart crime. Why can’t we have simple charts where you invert the axis or have columns out of scale. Bring back the good old charts!
Ingest — Aggregate — Charge 💫
Polar is the financial layer for a new generation of intelligent software.
Ingest LLM Usage events, Aggregate into billable units & Charge your customers automatically.
Get started with Usage Billing today → https://t.co/tBTBEBUctO
@JinjingLiang They had 80x annualised growth in Q1 I hardly think they are panicking. Their biggest issue is that they can’t serve enough compute. This will be solved with their new partnership with XAI
In his defence, they announced it yesterday. But I am yet to hear any third party verify it. I also requested early access but have not heard anything yet.
Ozempic reducing food demand by 850,000+ truckloads a year is insane. At some point this stops being a healthcare story and starts becoming a grocery, snack, and beverage earnings story.
The biggest issue I keep seeing with Opus models is the “pre-existing issue” excuse.
If the code is broken, fix it.
Don’t tell me everything passes when tests are failing just because this session didn’t touch that file.
Broken is broken.
I’ve used Claude Code + Opus every day for months.
Brutally honest take: GPT-5.5 finally made me switch.
Claude still feels better to talk to. It’s warmer, chattier, more natural.
But the performance gap with 5.5 is now too big to ignore. It just gets more real work done.
Still don’t like the codex app though. I am only using the CLI.
“But traditional backend have auth bugs too”
Yes of course they do. But a traditional DB has a server between the user and the database. To leak data, the server has to actively hand over data through a route you wrote.
With RLS the route is already exposed, to leak it you just have to forget to lock it. The default state is open.
Lovable just leaked source code, DB credentials and chat histories for all projects created before November 2025.
Here is my take;
The root cause is not a Lovable problem, it is RLS.
Row Level Security; a SQL policy that you stable to table that says “ only show rows this user owns”. What happens if you forget to staple it? Full access, no error or warning.
Here is how Supabase works under the hood;
Your anon key ships in the client bundle. Visible to everyone, the browser talks to Postgres over HTTP.
The only thing between a user and SELECT * FROM users is an RLS policy you may or may not have written.
Missing one table? That table is now public.
Missing one operation? That operation is now public.
This is not security by default. It is security by remembering.