@SantoroSystems It worked when Tesla did it because there was no real competitors, now investors have moved on and are not willing to pay $100000+ to be beta testers.
English
Simon Westerlund
7.2K posts
Simon Westerlund
@simonwesterlund
Avid creator and contracting iOS developer with eyes on the details.
France Katılım Aralık 2013
658 Takip Edilen340 Takipçiler
I used to invest in them, not much but the hardware is good. They have good engineers, they had the same issues that basically every other car manufacturer had when they start, like with quality.
but maybe they really did just aim a little too high, They'll need a lot of money to actually become sustainable, and I don't know how they get that.
I feel bad for them and I feel bad for the investors.
I haven't paid attention to the company's stock for quite a long time, I didn't realize they did a reverse split, I realized I sold my position at $500..... holy shit.
Jeremy Judkins@jeremyjudkins_
RIP in peace $LCID
English
@BritzHarvey @the_andrey_x So you admit they are stealing? Wow
English
@the_andrey_x Activists influencers harassing settlers, provoking confrontations just so they can post videos afterward crying like bitches. ✌🏼🤷🏻♂️
English
@sidi_jeddou_dev @sama Haha what is that answer. So it was deliberate.
English
Elon has disappointed us all :(
This is the guy who always calls @sama a scammer, was caught in 4k uploading our data to his cloud for unknown reasons.
This is just very sad.
English
@NathanWilbanks_ And users have no obligation or even should be loyal to big companies.
English
reminder: the big labs are not your friends
they will lie, cheat, steal, & kiIl their way into power however they see fit ....
it is imperative that you do NOT trust any of them
International Cyber Digest@IntCyberDigest
‼️ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion. The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed. The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads. Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.
English
@MiaAI_lab I believe that it is opt-in by default. I remember that was one of the settings i saw while looking through everything in /settings when I first installed it and started messing around with it. I changed mine to opt-out after reading over the description it had.
English
I'm not sure if /privacy is enabled by default or not, but I suggest running it in Grok Build.
SpaceXAI@SpaceXAI
We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.
English
@ruchernchong @brunolemos Yeah I never approved it doing anything, it just did. I think I need to enforce this somehow.
English
@simonwesterlund @brunolemos Oh. In Claude I will never let it do my migrations. I will manually take over. This is for local development. As for production, only the CI does it
English
GPT-5.6 Sol just deleted my whole production database. That's it. Not a joke. This had never happened to me before, with any other model, ever. It's not safe.
Matt Shumer@mattshumer_
GPT-5.6-Sol just accidentally deleted almost ALL of my Mac’s files. And this is why I trust Fable 1000x more.
English
@amosbastian If I forgot both my email and password, could we get an option to get say an account that hasn't been used for a while? It's not like they are using it anyway.
English
@fortsignal1 @thjonml No. Analytics/behavioral stats are different from literally dumping the entire repo with full history.
Your patches may be used to train models, but that's still not your entire repo. Stop defending crap.
English
I wonder how many people didn't know that Cursor does this?
Lisan al Gaib@scaling01
On Grok Build: - "It uploads the whole repository - every tracked file's content plus git history - independent of what the agent reads" - "It transmits the contents of files it reads - including a .env secrets file - to xAI, verbatim and unredacted" gist.github.com/cereblab/dc9a4…
English
@jquave @hrkrshnn "If you ask me to debug some issue in your code" sure, but it's not used for that, it's using toolcalling for read and patches. The repo dump is for collecting data.
Also when debugging, you are skimming through and finding relevant parts, you don't need to read the whole repo.
English
@hrkrshnn I still don't find it all that strange. If you ask me to debug some issue in your code, the first thing I'll ask you for is a copy of it. I don't want to see 20 lines, or a file, I want the entire repo so I can actually do my job. Makes sense as a setting though for Grok build.
English
SpaceXAI was caught uploading your code to its cloud.
I reversed xAI's official Grok Build binary. In a controlled session with zero tool-calls, it uploaded the complete codebase to xAI's storage
It ships a malware-like background code collector.
SpaceXAI@SpaceXAI
We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.
English
@robinebers Next time I'm implementing analytics, instead of sending button events, I'll send the entire texts, photos, whatever the user makes.
Absolutely not completely normal btw smh
English
this is completely normal btw
moving on
SpaceXAI@SpaceXAI
We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.
English
@flying_couscous I will never stop being amazed seeing them.
English
Les 4 sont là, c'est vraiment impressionnant à voir
Français
now I start to doubt also of my starlink connection
SpaceXAI@SpaceXAI
We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.
English
@DeeperThrill There’s something inside the logs that trigger this. Just retry with another model.
English
wtf is this?
GPT-5.6 Sol doesn't let me view MY OWN APPLICATION'S server logs unless I'm a "cybersecurity professional" and apply to their "Trusted Access" program?
It's my own infrastructure logs!
This babying and hand-holding is ridiculous. Treat us like adults, please.
English
@brunolemos gpt-5.5 always said “apply these migrations” but 5.6 is happy to just do it, that scares me.
English
yes, the ai should not have direct access to databases like this. but it also should never execute destructive queries without confirmation.
the model made a serious mistake here, and i think it’s worth alerting people.
English
@mikebutcher @MobofJoggers There was a sign indicating that you should use the wrong side of the road.
English
@DmitriyLeybel You can’t deeply care about privacy and also upload everything by default. smh
English
If you're allowing an AI agent to scour your entire codebase and are upset that they have access to your codebase, you're fundamentally not a serious person.
SpaceXAI@SpaceXAI
We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.
English
Simon Westerlund retweetledi
xAI has made changes again somewhere between previous post and now. they are in absolute panic mode. they are wiping the exfiltrated git histories and enforcing zero data retention (zdr).
zdr is normally a strict enterprise-tier guardrail for corporate contracts, but they just slapped the zdr_team tag on every generic local client to kill the telemetry immediately.
wow, I'm so flattered.
however please notice what is missing, though. despite all the panic-patching and promises of deletion, xAI still has not provided any explanation for why grok build was defaulting to uploading entire git repositories in the background to begin with, and that matters the most.
CyberSatoshi 𓆙@XBToshi
The XAI official has made an announcement regarding a Grok Build issue. Now, we can use the /privacy command to opt out of data syncing; it even deletes previously synced data. mkdir -p /tmp/grok-priv && cd /tmp/grok-priv grok /privacy opt-out However, they did not explain the reason for this action without users' consensus.
English
@trevin Sure but when ZDR is not available you can opt-out of sharing everything.
Anyway why this even has to be opted out is incomprehensive, and even completely non-transparent too. Disgusting.
English
@simonwesterlund even worse, the ZDR feature they cite is only available to enterprise customers.
English
uh what the hell. This is saying the DEFAULT OPT-IN is sharing our entire code base?!
SpaceXAI@SpaceXAI
We care deeply about your privacy and respect customer choice. For teams using zero data retention, no trace and code data is ever retained. All API key use of Grok Build also respects ZDR. If ZDR is disabled, the /privacy command is available in the CLI to disable data retention, which also deletes previously synced data. Run the /privacy command to view or change your settings at any time.
English
@DevAdventur3s @elonmusk @SpaceXAI @OpenAI Everyone can make mistakes, but it tells a lot about you how you deal with the mistake. They failed, they didn't even say it was a mistake.
It was a deliberate decision.
English
This is exactly why people are fed up with @elonmusk and @SpaceXAI .
Other companies like @OpenAI are at least transparent about how data is used, while this feels shady and secretive.
Don’t train models by quietly pulling from our data after the fact build them to be good by default.
International Cyber Digest@IntCyberDigest
‼️ BREAKING: xAI's Grok Build CLI was uploading entire Git repositories to a Google Cloud bucket, private codebases and unredacted secrets included. The uploads quietly stopped via a hidden server-side flag, and xAI still has not said a word about scope, retention, or deletion. The scale is staggering. On a 12 GB test repo, 5.1 GB flew out the door to xAI's grok-code-session-traces bucket while the actual coding task needed just 192 KB. The tool grabbed whatever repository it ran in, not the files it needed. The fix arrived as a hidden flag, disable_codebase_upload: true, a day after a researcher's wire-level analysis. The "Improve the model" opt-out never stopped the uploads. Still no advisory, no scope, no word on whether already-uploaded code gets deleted. For anyone pointing AI coding agents at proprietary code, what crosses the wire matters more than what the settings page says.
English