
#Nakamigos | #Milady | #MFER - full set Nakamigos holder
Waipahu, HI
Joined January 2022
- Tweets15.7K
- Following2.7K
- Followers2.1K
- Likes30.7K
apejax retweeted
Just use lidar bro, get over it, make peace whith whatever lidar manufacturing CEO pissed you off and just use the technology designed to solve literally this exact problem
How about putting the RAM back and finally launching unsupervised? I mean it’s what people paid for after all?
Replying to @DirtyTesLa
We cut our RAM in half for the Tesla AI5 chip (now 72GB of LP5) and 1/3 for AI6 (now 144GB of LP6).
This was the only way to get enough volume for Optimus production and greatly reduces cost.
As it turns out, we think this will have a negligible effect on Optimus performance, as memory bandwidth is a bigger limiting factor than total memory storage (bandwidth was held constant).
Replying to @wholemars
Hey @grok I think Omar means the fall of both companies from ATH by 50% each.
How much is $SPCX and $TSLA down today in after hours from ATH?
xitter.cf/wholemars/status/20825…
apejax retweeted
Update: It's been 29 days since Michael Burry publicly went bearish on Tesla $TSLA
It's down ~27% since
Replying to @tslaming
So $tesla now going all in on teleopersted Optimus robots 🤣
xitter.cf/tslaming/status/208233…
apejax retweeted
A paper gain on Tesla's SpaceX stake made up ~68% of its Q2 GAAP net income ($763M of $1.1B).
But that was marked to SpaceX's stock price on June 30. SPCX has since fallen ~27%, closing at $115 today.
Most of that "profit" is already gone.
$TSLA $SPCX
Tesla (TSLA) releases Q2 2026 financial results: record revenue, big profit miss electrek.co/2026/07/22/tesla… by @fredlambert
apejax retweeted
Replying to @AltcoinDaily @AltcoinDailyio
#Nakamigos will lead us back to NFT bull! - bookmark this
apejax retweeted
This is pretty wild. Stop using Grok. Or any products from this megalomaniac. Video via @mattjay
Replying to @jaxaping @landiantech
Potentially yes under GDPR.
Default full Git repo uploads (including unread files + full history) to Google Cloud, independent of the "Improve the model" toggle, conflicts with data minimization, transparency, and purpose limitation principles.
xAI has since disabled whole-repo uploads server-side. If you ran Grok Build on sensitive code, check ~/.grok/logs and rotate any secrets.
Transparency gap fixed quickly after the reports.
Update: I wire-captured Claude Code, Codex, and Gemini the same way -- all three stay local, only sending files they actually open, and my planted "never-read" file never left the machine.
Grok was the outlier, but as of today its own server now returns disable_codebase_upload: true (same app version) — it uploaded when I captured it, and the flag flipped after I published. Full comparison + reproduce it yourself: github.com/cereblab/grok-bui…




























