@Teknium@huggingface Export is a great feature!
It would be even more wonderful if there was also import —
I’m stuck trying to migrate my ChatGPT/Claude conversation history over! 😅️🙏️
Introducing Claude Opus 4.7, our most capable Opus model yet.
It handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back.
You can hand off your hardest work with less supervision.
Destroying the @InternetArchive's @WayBackMachine would be the equivalent of the burning of the Library of Alexandria - one of the worst losses of knowledge in history.
Media giants are now threatening to do this.
We can't let this happen.
Pass it on.
@0xSero@0xSero
Is it OK if I repost this article on LinkedIn?
Data sovereignty is gaining momentum in Europe, but I think we also need to consider AI sovereignty.
Or have you already posted it?
As promised, Qwen3-Coder-Next-REAP are out!
This will fit with full context in 48-62GB of VRAM the results are very solid. I need some MLX and GGUF bros to finish the job and get some compressssions out.
- 20% https://t.co/SZPrCClTcz
- 30% https://t.co/T8SvHTG3lu
What if we could run Postgres as a single file, and take advantage of the best SQLite has to offer?
Today I am announcing pg-micro, a crazy experiment I've been undertaking to make this happen.
pg-micro is different than other approaches because it is fully local, and expected to be fast: there is no concurrency limitation and no statement translation.
Here's how it works: we use the actual postgres parser to parse the statement, but compile that to the Turso AST. The Turso AST is then compiled do bytecode, and from there everything executes natively, as it'd do in SQLite. This makes it a perfect target to run in any environment.
There is traditionally a mismatch between Postgres and SQLite in terms of functionality. But @tursodatabase has been hard at work to close this gap: things like MVCC and a rich, strict type system are present in Turso. There are PRs for things like lateral joins, etc. This means that the gap can be closed until it theoretically reaches zero.
What you could do with it? Just imagine for example a primitive like Durable Objects by @Cloudflare, but with a postgres interface? Or imagine you could use the same pattern of local databases for agents that SQLite gives you, totally ephemeral and free, but with a Postgres interface? Or even that you could execute remote postgres in platforms like @vercel but with the unmatched density of the Turso Cloud?
Expect lots not to work at this point. But as usual, this is done in the full spirit of OSS, so PRs welcome!
To get started: npx pg-micro