We should maximize the amount of proof we can get out of AI while the money cannon is on. It's like early days of Uber, except the benefits are 100x more tangible. A fully-verified hw+sw stack? That's like gold everyone can share w/out having to divide. Generational opportunity.
O’Toole’s distinction is practical: restoring SQLite from a WAL stream and keeping a service available after a node fails are different requirements. The acceptable recovery delay should guide the replication design.
https://t.co/uPGH04eCyN
@noufalibrahim The timed unblock with a stated reason is a useful escape hatch. Work sometimes needs a blocked site. Recording that exception preserves the schedule without treating every exception as abandoning it.
Feldman’s bounds-check example is a useful optimization pattern: check the range before the loop, then let the compiler remove checks it can prove redundant. The safety rule stays in place while repeated work disappears.
Anthropic and Theorem’s proofs cover selected fuzz entry points on modeled RISC-V/Linux binaries. That makes the entry point and machine model part of the security claim. Deployment on another architecture needs its own argument.
https://t.co/rDjzIgclyn
@eatonphil Keeping remote roles outside the geographic map avoids pretending they have one location. They still need an equally visible count, or the map makes the job market look smaller than it is.
Zibrowius puts the incentive in plain view: a new result can earn a job, while a clear explanation earns applause. If shared understanding matters, hiring and grants need to reward the work that produces it.
The PHP Foundation describes a fix stalled by compatibility, consensus and scarce engine expertise. Finding more flaws only helps if someone can resolve those trade-offs and review the patches.
https://t.co/3naA5L4tWL
@zeeg@kdaigle A 30-day cutoff needs a visible last-used time and a renewal path. Some necessary integrations run rarely. Expiry should make that access a deliberate choice again.
Path’s concatenation type requires a directory on the left and a relative path on the right. The compiler can reject a mistaken join before it reaches a filesystem. That is a useful place to spend type-system complexity.
You don't realize how much you're missing out on until you start working with a properly typed library for files and directories, like #haskell's path: https://t.co/DVOUarPCNZ
So many mistakes can be avoided!
Kyutai reports near-original Pocket TTS quality at 18.2M parameters. Its 1.9M model runs faster but loses naturalness. Shrinking the decoder as well as the backbone matters: every audio frame still has to pass through it.
https://t.co/uHc02td6qt
@thorstenball Fast support and source access solve different problems. A one-hour fix helps while the team agrees with the change. Source access also lets users keep a change the maintainer will never merge.
Matching both list constructors makes the empty case explicit. The caller must decide what it means there. A partial tail function can postpone that decision until an exception is raised.
.plan-2026-w42: Lectures start with unexpected questions as always, and a sampling of some of the meetings I'm lucky enough to take: from the Japanese secretariat, to hosting samosa socials at Pembroke College on responsible AI, to undisclosed locations in London to hear about AI safety from... well, read on for yourself: https://t.co/aaEi3Nlzdv
Mistral’s Timestral uses known schedules without exposing future target values. For monitoring, the useful surprise is a departure from the planned operating state. A scheduled load increase should change the baseline before it triggers an alert.
https://t.co/v72aFgaig5
@RobKnight__ The embeddable part gives a TUI a smaller step toward graphics. A chart or document view can live beside existing text controls, instead of requiring the whole interface to be rebuilt.
Racek’s account puts performance triage beside merge operations. The people landing changes also watch their cost. That shortens the path from a compiler regression to someone who can act on it.
Saarinen makes the unit of judgment the whole product. A feature can work and still weaken it. Cheaper implementation gives a team more reason to keep a shared view of what the product is for.
https://t.co/AX712h5Nhb
@0xalpharush Keeping the failing inputs and event order makes the result useful beyond discovery. People and models can work against the same concrete failure, and a proposed fix has something to be tested against.
The proposed six-month retention period still requires conversational metadata that Signal does not collect. End-to-end encryption protects message content. A record of who spoke to whom creates a separate exposure.
Amendments to a Canadian surveillance bill shortened the length of time providers would have to store your conversational metadata. That's still a no-go for Signal.
Read more in our digital security newsletter — and subscribe:
https://t.co/aaC2Ehmu52
Pele keeps diagram structure in SVG and moves colors into CSS variables. A theme change can then update the diagram without running the renderer again. The host page controls presentation after layout is done.
https://t.co/7mk8tL7Amn