
Singularity Knocking
50 posts






🚨 SPACEX IS ABOUT TO REPEAT CISCO 2000 And nobody is ready. In 1999, Cisco was the backbone of the Internet. Real company. Real revenue. It was the most valuable company on Earth. Then the bubble burst. Cisco crashed almost 90%. Here's the real tragedy: The internet DID change the world. Cisco WAS right. But the stock? 25 years later, it still hasn't recovered to its 2000 peak. Now look at 2026. SpaceX just went public at $2 TRILLION. Everyone is calling it “the backbone of the Space Age.” Same story. Same narrative. But the setup is even more dangerous than Cisco: Much higher valuation. Extreme retail FOMO at the top. Market sitting at historic overvaluation. That's not an opportunity. That's a trap. Most people think buying the "future infrastructure" means guaranteed gains. But being right about the future doesn't mean you're right about the price. Cisco proved you can build the future and still destroy your investors. So now you have two choices: Chase the most expensive infrastructure IPO in history at the peak… Or understand what Cisco 2000 already showed you. Remember, I've predicted every major turn for the last 10 years, including the exact 2022 S&P 500 bottom and the recent 7,600 top. My next call will be the biggest one this cycle. Turn notifications on. Most people will follow me too late.


JUST IN: SpaceX is now America's 6th most valuable public company

The government shouldn’t take over Anthropic, CEO @DarioAmodei told me, though the current situation is “dangerous and unstable.”







JUST IN: OpenAI is reportedly considering drastic token price cuts as competition with Anthropic for AI users intensifies.

We’re rolling out changes to make Fable 5’s safeguards for frontier LLM development visible. Starting this week, flagged requests will visibly fall back to Opus 4.8—the same as our safeguards for cyber and bio. You will see this every time it happens. On the API, any flagged requests will return a reason for their refusal (coming to server-side fallback in the next few days). We wanted to deploy Fable 5 to our users quickly and safely. Visible safeguards can be probed, so they have to be robust, which takes time to get right. Invisible safeguards can be targeted more narrowly, allowing us to ship quickly with very few false positives. We went with invisible safeguards for this reason—and that was the wrong tradeoff. You should have visibility into the safeguards we have in place, and why. We’re sorry for not getting the balance right. Making the safeguards visible makes them easier to work around, so keeping them robust to jailbreaks will unfortunately mean more false positives while we improve the classifiers. We're also tuning our bio and cyber classifiers to trigger less often on harmless requests. We know this is frustrating and we’ll do our best to keep this period as short as possible. If you think a request has been mistakenly flagged: run /feedback in Claude Code, click thumbs-down on the fallback in Claude.ai or Cowork, or file the safeguard appeal form for API requests. Your reports help us tune these classifiers and we appreciate your feedback. support.claude.com/en/articles/82…



DAILY SITUATION RECAP:

Anthropic’s speedrun to becoming the bad guys should be studied


