
My tweets are notes to my future self, YMMV 👦. Trying for positivity! Building: @unraveldottech Alum: @recursecenter, @helpshift https://nitter.cf/t.co/Y1W3sicRXf
Pune, Maharshtra, India
Joined August 2008
- Tweets7.3K
- Following1.9K
- Followers1.6K
- Likes2.4K
Pinned Tweet
🚀 Announcing mcp-clojure-sdk: A Clojure SDK for Model Context Protocol Servers!
I'm excited to open-source our Clojure SDK for building Model Context Protocol (MCP) servers!
github.com/unravel-team/mcp-…
There’s 100% a kind of mania you can get into with coding agents, where it feels like you’re getting a lot done and working all the time but nothing is really happening.
I think it's often a form of avoidance of something else in life.
Vedang (fosstodon.org/@vedang) retweeted
This is probably going to be pretty bad for a while. How long? Nobody really knows yet. The backlog of vulnerable software seems to me to be ~decades in length and we have not yet reached anything like consensus on “Give AI alllll the keys; that will work things out.”
Vedang (fosstodon.org/@vedang) retweeted
As someone who has personally spent $500k / mo+ on Google Ads for years, I can tell you with certainty:
This revenue growth in Search is artificial & extremely unhealthy for Google’s business long term
Search volumes are declining as legacy search is being increasingly cannibalized by non-monetized LLM queries
Google’s response?
Manufacture revenue growth via short-sighted, highly extractive, customer-hostile tactics. I.e. charge advertisers more for lower quality clicks, including clicks they do not want and explicitly did not approve Google to charge them for
A few examples to illustrate:
For all of its history until recently, Google operated on a 2nd price auction model
I.e. if you bid $5 CPC and the next highest bidder bids $1 CPC, Google charged you $1.01 for the click (one penny more than the 2nd highest bidder) rather than the $5 you bid
This was a genius move by Google early on as it incentivizes advertisers to input their true maximum willingness to pay rather than trying to play the game of bidding low and constantly adjusting to try to stay just ahead of the next highest bidder while still not paying too much
However recently, Google silently deprecated the 2nd price auction and began charging advertisers as much as their bid and budget caps allow, regardless of what anyone else is bidding
It’s a short-sighted cash grab at the expense of the long term health of the advertiser ecosystem
Making thing worse, Google also recently nerfed keyword targeting precision
Google previously had precise keyword targeting settings that allowed advertisers pick individual search phrases to bid on, defined down to the character w/ exact match or phrase match targeting
This was one of the core features that made search advertising magic, enabling advertisers to run extremely precise campaigns based on exactly what their target customer typed
But now, even if you bid on a specific term or phrase using the strictest exact
-match targeting settings, Google will show your ad across 1000’s of unrelated keywords, labeling them as as “exact match (close variant)”
The definition of “close variant” means whatever they want it to and changes constantly. The result is advertisers get billed for clicks that are totally irrelevant to their business and that their targeting settings explicitly forbid Google from targeting. Google does it anyway and there’s no ability to turn this off
So now exact match is broad match, and broad match is just meaningless spam
This is all very bad for advertisers, but for Google, it allows them to show your ad and bill you for clicks across 1000x more searches that were previously going unmonetized (mainly because they’re garbage queries no one wants)
This is how you grow revenue atop declining search volumes
Lastly, and perhaps most egregiously, Google quietly stopped respecting budget caps by a factor of 2x. For example campaigns we’ve been running for years with $1000 daily budget caps suddenly began spending $2000+ per day
And the extra spend is entirely on the garbage keywords Google arbitrarily throws in as “exact match (close variants)” which have no value to our business, but can’t be turned off
Google offers no refunds nor any recourse for overspend or spend on keywords you explicitly did not target
These are not the actions of a healthy business. These are the actions of company whose core business is in decline but desperately needs to pump quarterly earnings so Wall Street will continue to fund insane capex while hopefully looking through their rapidly deteriorating negative free cash flow
Google operated a benevolent monopoly for the better part of 25 yrs
Meaning the value Google captured from Search was but a small fraction of the value it created, and that spread produced a potential energy that justified expectations of high earnings growth far, far into the future
This is now no longer the case
At the alter of AI capex, Google is sacrificing the golden goose
Q2 was an amazing quarter, with our AI investments redefining what’s possible across every part of our business.
Alphabet revenue grew 24% YoY and Google Cloud accelerated to 82% growth. We saw exciting momentum across the board from Search to YouTube to the Gemini app (which reached 950M monthly active users). Our model APIs are processing 22B tokens/min (up from 16B+ last quarter) driven by our workhorse Flash models. We’re also seeing great adoption of Gemini Enterprise, used by 90% of the Fortune 100, as well as strong demand for our security solutions.
Outstanding results and momentum, and such an exciting moment—thanks to all of our partners and employees around the world! 🙌 About to hop on the call!
Vedang (fosstodon.org/@vedang) retweeted
Replying to @0xglitchbyte
He’s not talking about that. All the community around software is slowly dying. The beauty to share, talk, discuss about something that is not AI is slowly disappearing and you can see it everywhere. Of course you can do things alone, but that’s just depressing.
Vedang (fosstodon.org/@vedang) retweeted
Replying to @joaomendoncaaaa @hotlinemagi
the interesting crowd has stopped talking about actual tech and started talking about their boring ass agent setups.
nobody has ever cared for the uninteresting crowd. nothing gained, nothing lost there.
every product i use should just be a headless mcp, that feeds into an agent, where i never have to think about anything underneath.
except for our product, of course.
in our product, customers love the ui and love us very much.
we're special that way.
it's getting close to 2 years of coding agents being a thing
looking back on that time the majority of discussion on here on where they're going, what's cutting edge, what matters has been primarily wrong
you had to actively ignore what was going on here to win in this space
Vedang (fosstodon.org/@vedang) retweeted
Libghostty progress in the past 6 months. It's amazing that NOTHING IN THIS LIST was true 6 months ago, and now its ALL VERY REAL. I remember bringing up the idea of libghostty 4 years ago and most people saying "but why." I did it anyways. And here we are!
Text reproduced in case its easier to read this way:
As a reminder, libghostty is the highly portable, embeddable library that provides core terminal emulation, render state, and more. I always felt that a free, high qualty, lightweight, reusable terminal emulation core would benefit the developer world more than any single GUI application. And that is playing out!
It is and always was my true purpose with the Ghostty project (I said this in my first ever talk about Ghostty!). I've jokingly said many times that Ghostty GUI is just a glorified tech demo for libghostty. That's not fair though, because GUI is great and there are really talented people working on it.
Since I started the project, Ghostty has always gotten people saying "I don't understand why you'd start a terminal emulator today." Well, the answer is libghostty. It's truly unique and its enabling something special (imo!).
Highlights of libghostty since 6 months ago (none of the below was true 6 months ago):
- Libghostty has nearly 100% coverage of all of Ghostty's core (and you can compile with flags to remove any of these features for size/safety): libghostty.tip.ghostty.org/
- Libghostty now builds and is tested (in CI) for: Apple (macOS, iOS, visionOS), Windows (MSVC and GNU), Linux, FreeBSD, Android, WebAssembly, and freestanding (i.e. direct on hardware with no OS).
- Libghostty has bindings in pretty much every popular programming language: C, Zig, Go, Swift, Python, Rust, .NET, etc.
- Libghostty's memory requirements have dramatically shrunk to enable the portability above. There's still work to do but a single empty terminal now takes 90% less memory. And at scale I've proven 10,000 active (input/output happening) terminals on a Linux server with 4 cores and 8 GB of RAM.
- Libghostty powers all JetBrains IDE terminals, over 12.5 million active users. blog.jetbrains.com/platform/…...
- Libghostty is the most popular core behind the wave of venture-backed "agentic" terminals and editors, such as Herdr, cmux, and many others.
- Libghostty is being discussed and has been verbally accepted to replace the terminal core in Neovim: github.com/neovim/neovim/pul… (work still to be done)
- Libghostty powers a really popular and powerful terminal emulator for emacs (Ghostel): github.com/dakra/ghostel
- Libghostty's speed is used by Antithesis to fuzz popular terminal programs and has directly led to hundreds of bug fixes sent upstream to programs such as tmux, btop, shells, and other terminal emulators. :)
- And so much more: github.com/Uzaaft/awesome-li…
Libghostty is really successfully turning into the tide that raises all boats. As it becomes more popular, Ghostty itself gets more performant and stable, and so does everyone else. It is also a vehicle for delivering modern terminal emulation to the widest source possible.
I plan on tagging libghostty 1.0 in the next few months and declaring ABI stability at that point!
A better mental model is thinking of the frontier companies like Intel and AMD back in the heyday day of x86. Huge investment to get to a competitive chip, so only a few can do it. Most the profit at any point in time goes to the best chip, and you have to stay ahead release after release. Except instead of one chip a year you are doing a flagship model every release few months.
Intel was a great business, but very operationally intensive. No surprise Andy Grove wrote the classic book on High Output Management.
Read this excellent post by @captn3m0 and weep : captnemo.in/blog/2026/10/23/…
"Indian government sites are serving revoked eMudhra certificates"
Now-a-days, I'm coding and writing less and less. But when I do, it makes me happy. It gives me a sense of satisfaction and a fuzzy, warm glow. It puts a smile on my face.
All this to say to myself: playing for the joy of it is good for my soul! Future me needs to remember to do it more often!
Vedang (fosstodon.org/@vedang) retweeted
My quick takeaways on the Anthropic S-1:
1. This is a historical moment
2. $6.6M in revenue per employee!! Hard to even comprehend how good that is but Anthropic is AI native as it gets so makes sense.
3. I always thought OpenAI would drop their S-1 first
4. Customers spend about 9x more after a year. Net Revenue Retention is approximately 900% as of Sep 30, 2026. Good SaaS companies brag about 120%.
5. Cowork is growing faster than Claude Code did. Goes to show you the demand for consumer products. Duo will probably rip.
6. 3 years ago this company did $41M in revenue. In the first six months of 2026, it did $16.3 billion. I don't think anyone has a mental model for that curve yet, I sure don’t.
7. Nearly half of revenue comes through cloud marketplaces. About 48% comes from customers buying through them. Big companies buy where their budget already lives, and the lesson for founders selling to enterprises is to get listed where your buyers already spend.
8. Their run rate formula is published: the last 28 days of usage times 13, plus subscriptions times 12, which i guess is the new ARR math for founders?
9. It looks like They're merging Cowork into Claude dot au which tells you the chat box era is ending and the "go do the work for me" era is here.
10. Thousands of Anthropic employees are about to become liquid at once, so expect the biggest wave of new AI startups and angel checks San Francisco has ever seen. Reminds me when Facebook went public but this is way bigger.
Let’s go!
11. Buried in the filing, Anthropic says the gap between what Claude can do and how widely it's used is one of its biggest growth opportunities, so the company itself is telling you the models are ahead of the market and someone has to close that gap for dentists, landlords, and plumbers.
12. Whatever happens, exciting times to be building in AI.
Anthropic has filed an S-1 registration statement with the SEC related to its proposed IPO.
Read more: anthropic.com/news/s1-sec
Legal disclaimer: A registration statement relating to these securities has been filed with the SEC but has not yet become effective. These securities may not be sold, nor may offers to buy be accepted, prior to the time the registration statement becomes effective. This post does not constitute an offer to sell or the solicitation of an offer to buy these securities, nor shall there be any sale of these securities in any state or jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.
Vedang (fosstodon.org/@vedang) retweeted
Let's be realistic: what are we planning to offer them in return? Forget remuneration, do we have enough investments earmarked for setting up R&D labs? How about access to the compute infra? Uninterrupted power and electricity supply?
Vedang (fosstodon.org/@vedang) retweeted
This is a big myth, AC's ONLY recirculate air, they never bring fresh air!
If you sit in an AC room for 3/4 hours you are breathing air with 1500 ppm CO2
Vedang (fosstodon.org/@vedang) retweeted
Yesterday, someone posted a task runner claimed to be 39x faster than Turborepo.
I got really excited, thinking they found some edge case in Turborepo and that I could make something way faster.
I open the benchmark repo, and its just straight up, flat out incorrect. Like, not even sorta useful. Not only was it not measuring the task runner parts of the script, it was overfit to a highly specific, completely unrealistic workload. 💀 The entire project is obviously Opus 5.5 vibe coded and Opus cheated the goal. Easy to miss if you're not experienced in build systems. Forgivable!
So, I open a PR to show that the algorithm being used can also make scheduling slower, by any arbitrary factor, with only a tiny adjustment. I chose 100x slower than Turborepo for demonstrative purposes.
The author fixed some of the problems but there are still grave issues. They're still comparing on an overfit bench that doesn't hold up when you insert the slightest variable, and *insisting* that its right. It is very obviously incorrect, but oh, well.
After revision, Turborepo is only 1.36x slower. Down from 39x, but a more realistic number nonetheless. So I figure: "Great! There must be something I can learn to make Turborepo faster."
I go digging, and it turns out the other tool is only faster still because it has correctness bugs. Once they correct those, they'll be roughly on par with Turborepo.
On top of that, the numbers they post now report with a mix of "% faster" and "✗ faster", using "% faster" whenever the difference isn't big enough to make their tool look good. 1.36x gets turned into "36%", which looks like more than it is to a casual observer.
This is a story of how I thought I was going to speed up Turborepo by 39x, and got nothing out of it.
I'm not mad; I'm just disappointed. 😄
Folks at Mozilla seem to have caught on and are asking the right questions 🫡
bugzilla.mozilla.org/show_bu…
Since the entire internet cares about critical certificates today, a reminder @UPI_NPCI has been running on an expired cert since Sep 2025.
Issued by IDRBT, which is now managing all of *.bank.in.

ALT │ File in APK │ Subject │ Issuer │ Valid from │ Expires │ │ signer-erupee.crt │ CN=psosigner.npci.org.in (National Payments Corporation of India, Chennai) │ DigiCert EV RSA CA G2 │ 2023-09-01 │ 2024-10-01 23:59:59 GMT │ │ signer-upi.crt │ CN=upinpci │ IDRBT Sub CA 2022 │ 2023-09-20 │ 2025-09-19 18:29:59 GMT │
Vedang (fosstodon.org/@vedang) retweeted
I read this and I'm terrified, the situation seems intractable.
In the python ecosystem alone every cpython install, venv, UV is at risk.
Don't get my started on npm, pnpm, yarn, go, rust.
My current 2026 security posture: stay home and only connect to the internet from a trusted ISP.
The winter is coming.
discuss.python.org/t/informa…
Emudhra absolutely needs to be shut down.
Some things you do not get to come back from.
That emudhra can't even show accountability is further proof that they need to be shut down.
> The revoked intermediates themselves have no customer impact. They never issued a certificate, so no certificate in use anywhere relied on them.
This is a listed company whose business is digital signatures, completely missing the point. 🤦♂️
Everyone who either had emudhra's certs in their trust store or communicates with such entities who had that, is impacted - not just emudhra "customers". Because many web browsers, operating systems, and cloud provides included these, almost everyone in the world is impacted.
Cloudflare explains the seriousness of the problem:






























