• 0 Posts
  • 16 Comments
Joined 1 month ago
cake
Cake day: May 1st, 2026

help-circle
  • The very broad funds definitely will - VTI/VTSAX - but at lower weights and under less time pressure than the rigid index funds (VOO/VFIAX). That takes off a lot of the liquidity squeeze and (presumably) reduces their loss.

    But you have to remember that people who use these funds intentionally invest in obvious losers and willingly overpay for hyped stocks because they believe, in the long run, that buying obvious losers is more than balanced by also buying the unexpected winners.

    SpaceX is just the first time an oligarch tried so obviously to rig the passive investor structure to his favor, and I’m glad the S&P people didn’t cave.






  • What I’ve seen indicates SpaceX will become something like 0.1% of S&P and 0.5% of Nasdaq. If a retirement fund is one of those indexes, and they get ‘forced’ to buy at 2x SpaceX’s eventual value, then that’s a loss of 0.05-0.2%. $50-200 on $100,000 principal.

    Most normal people won’t notice that among the usual stock market noise. Over a hundred million account, though, it’s a huge amount of money getting funneled into the thousands accounts able to front-run the index inclusion, which means, in turn, a huge amount of money getting funneled into the dozens of VCs who got into SpaceX pre-IPO.

    It’s like the scam from Office Space where they collect the rounding errors on interest.








  • My setup is a pile of kludges built on top of each other over the last two decades.

    I started with ULAs distributed through DHCP, connected to named, which allows hosts do declare their own name and let me access local services as though I had a real domain.

    My ISP eventually started supporting IPV6, but only assigned /128, so the ULAs got NAT-6ed out to the real world.

    I eventually learned how to request prefix delegation from the ISP and set up SLAAC.

    So now, my PIv6 clients have a) their link-local address, b) the ULA, c) a “privacy” SLAAC, and d) a unique SLAAC. All my internal services still refer to the ULAs.

    I don’t think I’d recommend this system for someone setting up from scratch. The easiest thing would be to go with SLAAC, if you can get prefix delegation, and set your DNS/pihole to send the unique-SLAAC address of any servers you run.