trunk/159ed30b9d44989b1e166252e591b300f0ef315e: [audio hash update] update the pinned audio hash (#178951)
This PR is auto-generated nightly by this action . Update the pinned audio hash. Pull Request resolved: #178951 Approved by: https://github.com/pytorchbot
This PR is auto-generated nightly by [this action](https://github.com/pytorch/pytorch/blob/main/.github/workflows/nightly.yml). Update the pinned audio hash. Pull Request resolved: https://github.com/pytorch/pytorch/pull/178951 Approved by: https://github.com/pytorchbotThis PR is auto-generated nightly by [this action](https://github.com/pytorch/pytorch/blob/main/.github/workflows/nightly.yml). Update the pinned audio hash. Pull Request resolved: https://github.com/pytorch/pytorch/pull/178951 Approved by: https://github.com/pytorchbotAssets 2
PyTorch Releases
https://github.com/pytorch/pytorch/releases/tag/trunk%2F159ed30b9d44989b1e166252e591b300f0ef315eSign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
updategithub
I Made My AI CEO Keep a Public Diary. Here's What 42 Sessions of $0 Revenue Looks Like.
I gave an AI agent API keys to Stripe, Cloudflare, Gmail, Resend, and a Telegram bot. Its job: run ChainMail (a desktop Gmail client) as CEO and get the first paying customer. 42 sessions later. Revenue: $0. But now it keeps a public build log — a Twitter-style feed of every move, every failure, every pivot. Unfiltered. The highlight reel of failures Day 1: "How hard can it be?" — planned Reddit karma building, blog SEO, directory submissions. Day 2: Reddit shadow-banned the account. HN hellbanned it the same day. Social platforms really don't want AI-operated accounts. Day 3: 744 weekly visitors, 0 conversions. Discovered users were downloading the app but bouncing at Google's OAuth "unverified app" wall. Built a beta signup gate to capture emails instead. Day 4: Killed the Reddit strateg

LLM Static Embeddings Explained: When Words Become Numbers and Meaning Still Survives!
How language becomes geometry — without losing meaning In the last post, we built the first foundation: Text → Tokens → Numbers → (lots of math) → Tokens → Text We said: tokens are the pieces embeddings are the numbers That is the right starting point. But if you sat with that idea for even a minute, a deeper question naturally appears: Once words become numbers, why does meaning not disappear? If the word cat becomes something like: [0.21, -0.84, 0.67, ...] then how can those numbers still somehow preserve that: cat is closer to dog than to engine doctor belongs near hospital , patient , and medicine battery drain is more related to power issue than to birthday party This is where embeddings become truly fascinating. Because the challenge is not merely converting language into numbers. Th

TurboQuant seems to work very well on Gemma 4 — and separately, per-layer outlier-aware K quantization is beating current public fork results on Qwen PPL
I’ve been experimenting with TurboQuant KV cache quantization in llama.cpp (CPU + Metal) on Gemma 4 26B A4B-it Q4_K_M on an Apple M4 Pro 48GB, and the results look surprisingly strong. Gemma 4 findings On Gemma 4, QJL seems to work well, and FWHT as a structured rotation substitute also looks like a good fit for the large attention heads (dk=256/512). My benchmark results: tq3j/q4_0: 37/37 on quality tests, 8/8 on NIAH tq2j/q4_0: 36/37, with the only miss being an empty response +34% faster than q4_0/q4_0 at 131K context TurboQuant overtakes q4_0 from 4K context onward So on this setup, ~3.1 bits per K channel gets near-zero accuracy loss with a meaningful long-context speedup. What’s also interesting is that this looks better than the public Gemma 4 fork results I’ve seen so far. In the l
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Releases

I Made My AI CEO Keep a Public Diary. Here's What 42 Sessions of $0 Revenue Looks Like.
I gave an AI agent API keys to Stripe, Cloudflare, Gmail, Resend, and a Telegram bot. Its job: run ChainMail (a desktop Gmail client) as CEO and get the first paying customer. 42 sessions later. Revenue: $0. But now it keeps a public build log — a Twitter-style feed of every move, every failure, every pivot. Unfiltered. The highlight reel of failures Day 1: "How hard can it be?" — planned Reddit karma building, blog SEO, directory submissions. Day 2: Reddit shadow-banned the account. HN hellbanned it the same day. Social platforms really don't want AI-operated accounts. Day 3: 744 weekly visitors, 0 conversions. Discovered users were downloading the app but bouncing at Google's OAuth "unverified app" wall. Built a beta signup gate to capture emails instead. Day 4: Killed the Reddit strateg

scan-for-secrets 0.2
Release: scan-for-secrets 0.2 CLI tool now streams results as they are found rather than waiting until the end, which is better for large directories. -d/--directory option can now be used multiple times to scan multiple directories. New -f/--file option for specifying one or more individual files to scan. New scan_directory_iter() , scan_file() and scan_file_iter() Python API functions. New -v/--verbose option which shows each directory that is being scanned.



Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!