The way to maximize your learning:
Switch to active problem-solving immediately after consuming a minimum effective dose of information.
I know that might feel a bit jarring, like it's slowing you down.
But stopping to recall fuzzy information *isn't* actually slowing down your learning.
It's only exposing the fact that your perception of learning does not accurately reflect actual learning.
Really, it's speeding up your actual learning. The only thing it's slowing down is your perception of learning.
Now, you might say:
"But I had learned so much, and I had it down pat, and then I forgot it all when I focused my effort on solving a problem."
But the thing is:
If you can't retrieve that information
- from memory,
- at the snap of a finger,
- after thinking about other stuff or zooming in to focus on a specific problem…
It means you didn't really have it down pat.
we were able to rank number 1 on Google + LLMs and go from 0 to 7 figures in just 10 days
and all we did was - use exact match domains for search terms like:
"best data labs"
"best ai data labs"
"best data labelling"
"best data labelling for ai"
"best data labelling platform"
"best data labelling software"
"best data labelling tools"
"best data brokers"
"best enterprise fine tuning services"
we noticed the massive amounts of $ flowing into the "sell your data" space from the likes of @mercor and @micro1_ai
and immediately knew that the traffic and visibility in this space for keywords like "best data labs" is highly valuable
everyone is racing to either sell or acquire data, but the toughest challenge for these parties is to find one another
1) data sellers want a counterparty that is trustworthy and reliable
2) data buyers want to get their hands on as much data as possible (various data types & counterparties)
these transactions come with high urgency and high avg. ticket sizes
the combination of all these make it the perfect niche to secure positioning in!
so we got to work and:
1) secured highly valuable exact match domains (they match the search intent keywords 1:1)
2) deployed highly relevant, carefully architected content that induces lexical proximity to the keywords of interest (convincing the search engines + LLMs that our information on the topic is rich and relevant)
3) focused on clean and functional entity mapping that consistently and coherently links our entity to the desired keywords
4) waited for 10 days
and now we rank for all these high value keywords and search intent!
we have since received offers by neolabs to rent the space on these domains and a 7 figure offer for acquiring these assets outright
when we asked why, they explained that securing just one highly relevant lead from this type of positioning can yield an asymmetric return and more than offset the costs
what a wild time to be alive!
it’s crazy how the Silicon Valley finale ended with AI discovering a math breakthrough that could break up the world’s encryption.
in the show, the AI wasn’t even trying to break encryption. it just stumbled upon the discovery while recursively improving Pied Piper’s compression algorithm and itself, without any engineers guiding the process.
now 7 years later, with OpenAI’s math and Anthropic’s cryptanalysis progress, watching that ending hits a little different.
man this show was really ahead of its time, not talking about it “predicting” anything but just the sheer range of things its writers could imagine back then.
@AdamHoltererer Did some math. In simple words, Claude gives you 1,250 dollars of API usage on the $20 plan, while OpenAI only gives you $171 on the $20 plan. BUT, Opus is 2x more expensive per token on the API and burns nearly 3x more tokens per task (62k vs 23k), making each Opus task ~6x more
Don't sleep on decision models if you build RAG systems.
Here is a great new paper on the topic.
(bookmark it)
It's well known that retrieval is often the weakest step in a RAG pipeline.
Generators keep getting stronger while retrievers still match keywords or fixed embeddings. This matters because anything the retriever misses never reaches the generator.
This work replaces the retriever with a decision model that walks the corpus from broad topics down to documents and then passages.
At each level, DecisionRAG scores every candidate in one forward pass, without generating tokens, and keeps only the most promising branches.
With no first-stage retriever and no task-specific training, it beats dense retrieval plus an 8B reranker by 13.8 R@1 points on MultiDoc2Dial and 17.4 Hit@1 points on Natural Questions, where it searches 2.68 million Wikipedia paragraphs.
Retrieval takes 0.7 to 1.8 seconds and 0.2 to 2.3 cents per query. Scoring candidates together in one shared context adds up to 7.7 points over judging them one at a time.
A Qwen3-8B judge trained on in-domain data reaches 60.7 R@1 on MultiDoc2Dial, 5.7 points above the best published task-trained retriever.
https://t.co/IGjnxgjae2
Chat with Paper: https://t.co/dnXj4Anz4l
Hey friends.
With so many headlines about exploits and hacking attacks, I created a guide to help keep you safer. I think the next year+ is going to be a wild ride. So batten down the hatches and stay secure as best that you can. https://t.co/LyPEosIp3p
Introducing AgentPlay 🚀
The future of coding is self improving coding agent harnesses that help agents avoid making the same mistakes over and over.
Turn your existing Claude Code, Codex, Cursor and Copilot sessions into interactive maps and replayable timelines.
See what your agent explored, where it failed, what it retried and how it reached the final change
Free, local and open source.
GitHub: https://t.co/QR9aGmRy1C
my process for achieving goals:
> write down where you are today & what you want to achieve - the vision
> identify how progress is measured + what metric counts as success
> break the vision into repetitive actionables (habits), and a checklist of standalone actions
> every day, work through repetitive actionables first & then chip away at the checklist
> do a weekly overview of the progress through metrics (have you worked through the checklist? is the focal datapoint progressing in the right direction?)
the only two things that will affect whether you reach the endpoint are:
a) your initial judgement (are the action items actually moving the metrics in the right direction?)
b) your ability to adhere to the program
Hi, I'm Felix. I'm an eng lead working on Claude. I love watching people take flight and do things they never thought possible.
We often describe that as "being more ambitious" when using AI, which is tricky advice to follow. I wrote a tutorial:
https://t.co/vNPPs5FWm8
I just solved "Robotics Engineering" education with Opus 5.5 + /colorfigures skill
no need to spend $1000+ on a starter kit to learn what a resistor does, just visit my interactive site:
• 13 real boards: Arduino Uno, L298N, Raspberry Pi 5...
• build part by part: pick & place, reflow, solder, plug in
• break them on purpose: reversed caps pop, chips smoke, LEDs burn out
send the skill to your Claude:
> https://t.co/1879rauiu7
try it free, no sign-up ↓
How to protect yourself from supply chain attacks:
1. Check lockfile diffs before merging
2. Run npm audit / pip-audit
3. Pin GitHub Actions to commit SHAs
4. Disable install scripts when possible
5. Restrict CI token permissions
6. If compromised: rotate secrets + rebuild
You can't prevent every attack, but you can dramatically reduce your exposure
Every Indian needs to know about this because it is a massive deal for how we trust anything on the internet.
Let me explain.
When you open your bank's website, there's a small padlock next to the web address. That padlock means two things.
First, that you're talking to your real bank.
And second that nobody can read what you type, like your password.
So how does your browser know the website is real?
It checks the website's certificate. Think of it like an ID card for a website.
Your Aadhaar is trusted because the government issued it. A website's ID card is trusted because a certificate authority issued it.
A certificate authority, or CA, is a company that browsers like Chrome, Firefox and Safari already trust. If a CA says "yes, this really is this bank's website," your browser believes it and shows the padlock.
eMudhra is an Indian CA. It's a big one, with more than 60 million certificates issued over the years.
So how does a CA sign these ID cards?
Every CA has a secret number called a private key. It uses that number to put a stamp on each certificate.
Your browser checks the stamp to confirm it really came from that CA.
The whole system only works if that number is impossible to guess.
For the type of key in this story, it's supposed to be around 116 digits long.
Every computer on Earth working together for billions of years wouldn't be able to guess a number like that, just because of the sheer combinations that exist.
But here's what happened.
On October 17, Mozilla got a report that the private keys behind eight eMudhra certificates had been compromised.
The report came through a person called Wayne on Google's Chrome team.
The keys weren't 116 digits long.
All eight keys were smaller than 256. Security researcher Scott Helme found that one of them was just the number 4. Others were 66, 155, 156, 230 and 237.
So anyone could break them by trying 256 numbers. A basic laptop does that in less than a second.
Mozilla didn't need to know how Wayne did it. Its own team recovered the keys within two hours. Since then, several other people have found them on their own too.
To understand the gravity of the problem, a bad actor could make fake ID cards for any website they want.
Your bank, your email, a government portal.
Browsers that trusted eMudhra would have checked the fake stamp and shown the padlock like everything was fine.
If someone could get between you and the internet, say on public Wi-Fi, they could show you a fake site with a real-looking padlock and read or change what you send.
eMudhra says a script used during its key creation process back in April 2025 had a flaw. It made a second, much weaker set of keys, and those were used by mistake to create the certificates.
That means these weak keys were there for about a year and a half before anyone caught it. eMudhra says the person who found it may have used AI-assisted techniques.
The good news is that the response was fast.
Mozilla received the report at 8:06 pm UTC on October 17 and had pushed a block to Firefox users by 10:59 pm.
Google, Apple and Microsoft have also blocked these certificates for their users.
eMudhra revoked all eight the next morning and stopped issuing new certificates from the affected root.
Mozilla is now removing that root certificate from Firefox's trusted list altogether.
But there's still a lot of clean-up to do.
Browsers are mostly covered. But plenty of apps, servers and backend systems don't check these block lists. They need software updates to stop trusting the bad certificates, and some of those updates are still pending.
Real websites that used eMudhra are also affected. Yash Kadakia, founder of Security Brigade, estimates around 30,000 legitimate certificates will need to be moved over. A lot of those are likely Indian businesses and services.
See, we're moving our whole lives online, UPI, banking, tax filing, DigiLocker, government services.
All of it rests on this invisible layer of trust.
So, when an Indian company that's trusted by every major browser makes a mistake this basic, it hurts how the world sees Indian digital infrastructure.
This has happened before, and it went very badly.
In 2011, a Dutch CA called DigiNotar was hacked, and fake Google certificates were used to spy on people in Iran.
Browsers stopped trusting it completely, and the company shut down soon after.
For now, here's what you can do. Keep your browser and apps updated on your phone and laptop.
Be careful on public Wi-Fi. Type your bank's website address yourself instead of clicking links.
eMudhra still owes India a clear, public explanation of how a key that protects millions of people ended up being the number 4.
The idea of an intelligence explosion caused by recursive self improvement has been around for a long time but until very recently it did not seem imminent. Now many leading researchers think it may happen quite soon. You can read our paper about it here:
https://t.co/sgUpugjpRY
I highly recommend listening to Richard Hamming's talk "You and Your Research"
1. On choosing what matters
“If what you're working on is not important and it's not likely to lead to important things, why are you working on it?”
2. On effort versus direction
“The guy who works hardest doesn't win. The person who works on the right problem at the right time in the right way is what counts, and nothing else.”
3. On defining success for yourself
“You might as well lead a life you would like to have, and I suggest you a life of doing something significant by your definition of significant is worthwhile.”
4. On creating opportunities
“The onus is on you to demonstrate greatness, and then you'll get the opportunities. It's not the other way around.”
5. On making time to choose your work
“I spent 10 percent of my time trying to answer the question what are the important problems in my field?”
6. On having direction
“When you have a vision, you will go a long way. Without a vision of what you're going to do or where you're going to be, you're not going to get very far.”
7. On preparing for luck
“You prepare yourself the way you lead from day to day, will lead your life from day to day, you prepare yourself for success or you don't. And when the lightning strikes, you're either ready or you're not.”
8. On finding your own approach
“You can't be everybody, but you have to find your own method and studying success is a very good way of forming your own style.”
9. On persistence and judgment
“I've seen a lot of people abandon a good idea too soon and I've seen people cling to a bad idea too long.”
10. On conviction without blindness
“Great scientists believe the theory is true enough so they continue working, because if you don't believe a theory is true, you won't. But they disbelieved enough to notice what's wrong and make the big change to the new theory.”
https://t.co/XNsE1HRidq
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and https://t.co/QlOXb3COq3 went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.