Build some houses. Stop the phone thefts. Tackle the fare dodging. Allow somewhere to open so we can get a drink after 11 pm.
Stop your absurd virtue signalling nonsense. DO YOUR JOB
@tom_nafo@patrickmclemor2@davidbellow The area is constant across both approaches (โ number of cars going the restricted way) but the greater length does lead to it impacting others as you suggest
Anthropic co-founder Chris Olah was invited to speak at today's presentation of Pope Leo XIV's encyclical "Magnifica humanitas."
Read the full text of his remarks: https://t.co/CoBfkVOVcy
SHE SAVED MILLIONS IN TAX. HE SET THE TAX RULES. HMRC SAW NO PROBLEM.
Rishi Sunak (@RishiSunak) was running the nation's finances. Raising taxes on working people. Telling the country there was no alternative.
His wife, Akshata Murty, was quietly using non-domiciled status to avoid paying UK tax on her overseas earnings, including roughly ยฃ11.6 million a year in dividends from her father's company, Infosys.
The estimated saving: around ยฃ2.1 million per year. Over several years, sources told @Independent that figure could have reached ยฃ20 million.
Non-dom status is legal. But when the man setting tax policy for 67 million people has a wife saving millions under that same policy, most organisations would want that conflict documented and scrutinised.
There is no evidence HMRC (@HMRCgovuk) treated it with any urgency.
Then someone inside Whitehall decided the public had a right to know. A source passed details to @Independent in April 2022, right in the middle of Partygate. The story blew up.
Sunak was forced to ask for a ministerial interests review. Murty announced she would voluntarily start paying UK tax on worldwide income.
What happened to the whistleblower?
A leak inquiry was launched. @Channel4 noted it could lead to criminal prosecution, because disclosing someone's personal tax information is illegal in the UK.
The source was never publicly identified. No prosecution ever came.
So the person who told the truth about a potential conflict of interest at the heart of the Treasury faced a criminal investigation.
The conflict of interest itself got a press release and a polite apology.
Source: @Independent, @guardian, @BBCNews, @thetimes
Weโre reimagining a 50-year-old interface - the mouse pointer - with AI. ๐ฑ๏ธ
These experimental demos show how people can intuitively direct Gemini on their screens using motion, speech, and natural shorthand to get things done ๐งต
@sama More sophisticated modelling/control of when to ask for my guidance/preference/give me an early summary vs when to press on (a la "I'm feeling lucky")
A tricky LLM interview question:
Your RAG system scores 90% retrieval accuracy on 5k company docs.
But scaling to 500k docs drops the accuracy to just 50%, with the same embedding model and retriever.
Why did this happen?
The simplest answer is that more documents mean more competition for the top-k retrieval slots. That is true, but it doesn't explain why accuracy drops this dramatically.
The answer comes down to how enterprise docs are distributed in the embedding space.
Today, a single product decision in a company generates meeting transcripts, Slack threads, Confluence docs, Jira tickets, and email threads.
They are related to the same event, so they all land in a similar region of the embedding space.
As the company operates over months, this pattern repeats for every project/customer/roadmap, and the embedding space fills up with clusters of closely related documents.
But all related docs don't contain the same facts.
โ Slack thread covers the decision made
โ Jira has the implementation deadline
โ Confluence has the technical spec
โ Email thread has the customer request
When a query is about a specific fact (like a deadline), the answer lives in one of those docs.
At a 5K corpus size, there might be 3-5 docs touching that topic, and the correct one easily lands in the top-k results.
But at a 500K corpus size, there could be 40-60 total docs, and the one containing the actual answer can easily get pushed out of the top-k by other topically relevant docs, degrading retrieval.
A recent research paper from Onyx documented this.
The researchers used their newly open-sourced EnterpriseRAG-Bench dataset.
It has 500k+ synthetic enterprise documents spread across Slack, Gmail, Jira, GitHub, Confluence, Google Drive, HubSpot, Fireflies, and Linear, with realistic noise like misfiled documents, near-duplicates, and conflicting versions.
They ran the same retrievers at five corpus sizes from 5K to 500K.
โ Vector search accuracy dropped from 90.7% at 5K documents to 50.6% at 500K docs.
โ BM25 degraded more gracefully, from 85.8% to 68.4%.
โ At every scale, higher neighborhood density in the embedding space monotonically correlated with lower recall.
The practical implication here is that retrieval accuracy on a 5k test set tells you almost nothing about production-scale performance.
Always test at a realistic volume to measure the neighborhood density in your embedding space to estimate how much headroom the retriever actually has.
The entire EnterpriseRAG-Bench dataset (500K docs with questions, and the whole evaluation harness) is open-source.
Run your retriever against it at 5K, then at 500K, and see where your own accuracy curve breaks.
I have shared the GitHub repo in the replies.
I'm a big advocate for the Oxford comma. I'm, also an advocate for, the, Shatner comma. You should, try it sometime. It really, makes your, sentences more, exciting!