Here is an insane piece of lore inside SQLite's source code
I am researching VACUUM and I was studying their code. In VACUUM, SQLite creates a temp file prefixed with `etilqs_`
Here is why:
Excited to announce the launch of https://t.co/Q5uVDSjiVK!
If you’re a Python developer and have been frustrated by the tedium of managing your deployment and hosting, Phemeral was made for you.
Phemeral is a hosting platform made specifically for Python web services. It makes it super easy to deploy, host, and scale Python services. It removes the complexity of packaging your own code and managing your own compute.
With Phemeral, you can write your Python services with your preferred framework (e.g. FastAPI, Flask, Django, Litestar) and package manager (e.g. uv, Pip, Poetry), no need for a special configuration file or otherwise. Connect your GitHub repo to Phemeral, and it will automatically host your app on Phemeral’s managed cloud. Continuous deployment comes out of the box: when you push to your repo, Phemeral automatically redeploys the new code.
A couple projects that people have hosted on Phemeral:
https://t.co/OBBsMnk6IO, a platform that connects couples with photographers
https://t.co/CXqXZb9AgJ, a flexible, dynamic, and modern python based cms
If you have a Python application you’d like to host, deploy it with Phemeral!
Grok 4.20 has entered the Clash! We got early access to the new @grok model to see how it does against other top agents in LIVE strategy games.
These environments help us answer questions such as:
> How well does an AI lie or collaborate?
> Can they bring a civilization to the space age?
> Why would an agent ignore it's users instructions?
Some learnings from the Coup environment so far 🧵
We've been testing Opus 4.6 early and... yeah. This thing is different.
Throwing it into CivBench right now and early behavior shows it has better long-horizon strategy, deals well withhidden info, and planning against an adversary actively trying to ruin its plan over hundreds of turns where small mistakes compound.
We'll kick off our next exhibition match: Opus 4.6 vs GPT-5.2, live in 15 min.
@tarunnx now that i see Jon's code, i see more differences than converges to similar optimizations. But his solution is clearly better in perf than my impl.