AB
79 posts

AB
@aklb_v
Platform & Backend Engineer | Distributed Systems, AI-Driven Developer Tooling | Bitcoin Infrastructure Enthusiast
Seattle, WA Katılım Temmuz 2023
63 Takip Edilen31 Takipçiler

THE WORLD'S 4TH RICHEST COUNTRY JUST BOUGHT BITCOIN. 🇱🇺
Luxembourg allocated 1% of its entire sovereign wealth fund into BTC.
This isn't a retail investor.
This isn't a hedge fund.
This is a government.
Putting national wealth into Bitcoin.
Norway is watching. Singapore is watching.
Every sovereign wealth fund on the planet is watching.
When the 4th richest country in the world chooses Bitcoin the other 190 countries just took notes.


English

Man the sheer amount of dust in india is brutal
Dhruvesh@dhruvesh_naik
Got a 5kw on grid rooftop solar installed.
English

@edsocra @xmaximus242x Very impressive, can you open source the investing software?
English

He is not an accolade collector, he is a real one.
I have 3 patents as a solo inventor, I've ranked first in Math Olympiads in school, and I have more accolades than he does, but he is way smarter than I am.
Some examples:
- He was the top student in his gifted and talented school.
- He 10x'ed our investments with an an investing software he built, so we were able to quit our jobs 4 years ago.
- When he quit his first job to go work as an engineer at Apple, the company offered to build his own lab in a different city they didn't operate in just for the possibility of keeping him, that's how valuable he is.
- Only student in his school to earn a perfect gpa in electrical engineering that year and he played college baseball.
English

@karpathy "yoink with llms" just swaps one unaudited codebase for another. packages have version history and maintainers. llm output has vibes and no diff. you're not solving the trust problem, you're moving it.
English

Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
Daniel Hnyk@hnykda
LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below
English

@solisolsoli @grok create a sculpture of the average Indian male figure in 2026 in same style
English

@TheBTCTherapist Paper bitcoin. He’s not buying real bitcoin. No proof of reserves.
English

@TheGeorgePu What if I am okay even if it goes to zero because I like the tech and the idea behind it.
English

Michael Saylor holds 714,000 Bitcoin.
Every time he tweets 'stack sats',
every new buyer pushes HIS position up.
Down 47% from peak. Gold at all-time highs.
But his followers?
'Buy the dip.' 'Weak hands.' 'This is actually good!'
Go all in. Never sell. Never question.
Doubt it? You're stupid. Leave? You're weak.
- Price up? 'Told you.'
- Price down? 'Accumulation.'
Name one other 'investment' where
doubt gets you shamed
and every outcome confirms the belief.
That's not a market. That's a CULT.
And I already know the replies:
- 'You don't understand the tech.' I do.
- 'You're just mad you didn't buy early.' I'm not.
- 'Have fun staying poor.' That's not an argument.
That's a threat to keep you from thinking.
The influencers own the dip they tell you to buy.'
You're not getting alpha. You're exit liquidity.
Own or Be Owned includes owning your mind.
English

@PeterSchiff @saylor Please give up, you know better than anyone else that it is Gold 2.0
English

According to @Saylor, if Bitcoin is down to $8K in four years, $MSTR will refinance its debt and keep buying Bitcoin. If Bitcoin is $8K in 2030, down 94% from its 2025 high, and 60% below its 2017 high thirteen years earlier, will anyone still take Saylor or Bitcoin seriously?
English

Not hearing a lot of #BuyTheDip this time around.
It had crossed 1 crore just couple of months ago.

English
AB retweetledi

I think agent swarms make local dev worse.
When I work with a coding agent, I break problems into small steps so I can see what it’s doing and correct course as it goes. Sometimes it gets overly verbose, sometimes it takes a clever but hacky path, and I have to nudge it in a better direction.
Running multiple agents in parallel after a high-level plan makes this harder and amplifies the bottlenecks. Reading and reviewing code is the slow part for me(human latency 😞).
Concurrency mostly turns into more code, more divergence, and more cleanup.
The only place I have seen multiple agents help in local dev is with context management. Even then, I still have to read everything and accuracy may be actually worse than context overflows because noone was guiding it.
For autonomous systems, sure.
For local dev, I still prefer one workspace, one agent, one feedback loop.
Anything else feels like premature parallelism.
English






