Earlier quoted context omitted.
using them in VSCode all the time for months now. Qwen from Alibaba Cloud, Deepseek from deepseek.com. none of them upload entirety of codebase or even attempt to. in fact, opposite. Chinese AI seem to post-process heaviliy locally. they are always using head / tail, grep, sed, and do as much as they can locally and extrac meaningful data and send home (AI inference chunks). only what is really needed. it is actually…
For me, them allowing API usage on coding plans so we can use any harness, and returning the full unabridged reasoning back are how they earned my trust.
What xAI's Grok build CLI sends to xAI: A wire-level analysis
81–90 of 251 posts
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#82Earlier quoted context omitted.
How is it hyperbolic when it's literally the subject of the post? Did you not read the OP?
The "scam" part is the hyperbolic part
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#83Earlier quoted context omitted.
They were caught stealing Apple trade secrets, dude. Nothing is beneath them.
Nothing is beneath Altman, maybe, but Satya isn’t that dumb. MSFT cares about OAI but giving access to private data and trade secrets voluntarily would be catastrophic for them. Doesn’t feel like the type of mistake Satya would make.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#84Earlier quoted context omitted.
Does OpenAI also have access to all github repos via partnership with microsoft?
GitHub Copilot engineer here working on identity, safety, and privacy - no, even Microsoft doesn’t have access to all GitHub repos. As years have passed since the acquisition “company” delineations have blurred a bit, but Microsoft employees still need to go through a separate onboarding process to access any GitHub company resources (internal repositories, telemetry, documentation, etc.), and then we have an additio…
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#85This is one of the reasons why native proprietary coding agent runners like claude-code, codex, grok-build etc are so dangerous for privacy… you just don’t know what “secret sauce” they’ll add in the next update… It’s much safer to use something like opencode and use models via their API… however, the tradeoff is that it will never perform as well as it does in their native agent runners…
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#86Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#87Earlier quoted context omitted.
GitHub Copilot engineer here working on identity, safety, and privacy - no, even Microsoft doesn’t have access to all GitHub repos. As years have passed since the acquisition “company” delineations have blurred a bit, but Microsoft employees still need to go through a separate onboarding process to access any GitHub company resources (internal repositories, telemetry, documentation, etc.), and then we have an additio…
How do you define "access" here? Microsoft has demonstrated that it can delete any GitHub repo at will. Maybe there's some shell entity between corporate "Microsoft" and "GitHub" that's doing the dirty deeds without attribution...
Microsoft can certainly request that we perform actions against repositories, as can governments, customers, random people on the street, etc. Whether action is taken in those cases is a question for lawyers to fight over, but we have the engineering guardrails in place to require it to be an intentional, audited action.
I appreciate the spicy question tho, even if misguided!
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#88It still somewhat blows my mind that xAI is allowed to operate in Europe given e.g. GDPR et al . Closest I can come to is Musk is above the law even in the EU given his relationship to Trump.
Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#89Re: What xAI's Grok build CLI sends to xAI: A wire-level analysis
#90How do these findings compare to Codex, Claude code, and cursor