You mean ex-AI dev surely?
xAI dev leaks API key for private SpaceX, Tesla LLMs
61–70 of 83 posts
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#62Earlier quoted context omitted.
> Guess who's going to be fired by elon :D i know, you probably just meant it as a fun comment. but i don't get how this is funny. this person probably relies on income, might have a family to feed... and just made a mistake. a type of mistake, that is not uncommon. i mean i have seen corporate projects where senior engineers didn't even understand why committing secrets might be a bad idea. yes, of course, as a engi…
If you ever visit a Bill Burr show, let me know. I wouldn't want to miss it.
Big fan of bill burr. I don't get how some here don't understand what my comment is about. I assume your implication is that is have no sense of humour or am too snowflaky. I mean, next time you visit a bill burr show, let me know if his punchline is such a banger like the one i commented on. And if you think this is the same type of humour, please, let me know when you visit a bill burr show next!
But, my comment was clearly not about making excuses for the mistake of the engineer. I wanted to express that it's insane that such a common mistake can happen in a company like that. And i don't get how people let the ceos & leads off the hook so easily.
But some apparently don't think that way.
In my opinion: the mistakes that are common, and severe, and very easy to avoid, have to be expected and hence circumvented through industry standard behaviour. And that is not (solely) the responsibility of one committing engineer. Any good team has best practices to prevent these type of basic, potentially fatal mistakes from happening, and usually at least a glance-over review process where these mistakes should be found by another team member on first sight... and now, when it's an "AI making devs extinct"-type of company... and they're not catch this type of error, is ridiculous. That an individual can screw up something potentially so critical, is an organizational failure.
But anyway, i think my points were clear in the first comment already.
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#63Earlier quoted context omitted.
Or, since we're apparently playing the game of maybes in this thread, maybe the LLM was only trained on the teams grandmothers' spaghetti recipes, so that new hires can learn to make the best bolognese sauce.
This being Musk, it wouldn't surprise me. I mean, consider The Boring Company sell a "flamethrower" despite being theoretically about… boring.
I think you missed a lot of the word play. Somebody else has explained Bore[1]-ing vs boring.
But they sold a blowtorch aka not a flamethrower. The difference being a flamethrower actually "throws flames" like 10+ feet.
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#64Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#65What absolute incompetence. Not just on this dev, but any org with API keys ought to be scanning for leaked keys constantly. Failure of one and failure of many. Of course Elon hires only based on 'merit'...
How would you scan for your api keys on repos outside of your organization? I assumed this was a dev’s personal repo.
This was on public GitHub, which anyone can scan for anything. Their API is a firehose you can consume: https://api.github.com/events
GitGuardian's public report on secrets sprawl talks about their methodology of scanning any commit https://www.gitguardian.com/state-of-secrets-sprawl-report-2...
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#66One thing that sticks out to me is that there is an incorrect assumption from the journalists that having the API keys to an LLM can lead to injecting data. People still don’t know how LLMs work and think they can be trained by interacting with them at the API level.
unless I somehow skimmed over it, they only appear to refer to "prompt injection"
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#67Earlier quoted context omitted.
This being Musk, it wouldn't surprise me. I mean, consider The Boring Company sell a "flamethrower" despite being theoretically about… boring.
I think you missed a lot of the word play. Somebody else has explained Bore[1]-ing vs boring. But they sold a blowtorch aka not a flamethrower. The difference being a flamethrower actually "throws flames" like 10+ feet. [1]: https://en.wikipedia.org/wiki/Bore
I didn't miss anything in the wordplay*, it was obvious. (As are the initials, an extra pun).
I put quotemarks around "flamethrower" because that's what it was originally sold as before obvious and predictable legal issues with real flamethrowers and the fact it was obviously mimicing the prop in Spaceballs.
My point is: neither weed burners nor actual flamethrowers have anything to do with digging tunnels nor any adjacent aspect of civil engineering.
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#68Earlier quoted context omitted.
> if this person is actually good at their job and takes it seriously, it's certain: he or she is not going to leak a secret again If they were good at their job, they wouldn't have leaked the secret in the first place. The correct workflow is to: 1. Create commits that only change do one thing. Not possible to "forget" there were secrets added alongside another feature. 2. When adding secrets, make sure they're encr…
I'll do you one better. Start your .gitignore file with this line *
Mine all start with (and .dockerignore has a similar one)
# Default block all
/*
# Specifically allow files and directoriesRe: xAI dev leaks API key for private SpaceX, Tesla LLMs
#69The biggest surprise to me was: “administration officials told some U.S. government employees that DOGE is using AI to surveil at least one federal agency’s communications for hostility to President Trump and his agenda”.
I understand that there’s no expectation of privacy at work (especially in govt), and everything you write is “on the record”; however an employer monitoring comms for what’s essentially thoughtcrime is heinous. Isn’t disagreement healthy?
Re: xAI dev leaks API key for private SpaceX, Tesla LLMs
#70The biggest surprise to me was: “administration officials told some U.S. government employees that DOGE is using AI to surveil at least one federal agency’s communications for hostility to President Trump and his agenda”. I understand that there’s no expectation of privacy at work (especially in govt), and everything you write is “on the record”; however an employer monitoring comms for what’s essentially thoughtcrim…
Yes but it's worth understanding the executive branch (which according to this administration includes all federal agencies), in its constitutional form, is more or less just an extension of the president. Conceptually they all "perform at the pleasure of" the person of the president. The "balance" and "disagreement" can happen outside of the executive, in the legislative or judicial branches.
Definitely not how I would run an organization (even a military organization), but it's not _conceptually_ wrong. If you were a general and you had lieutenants expressing "hostility to" your agenda, would you keep them on? Again, I'd probably say yes up to a limit, but it's not outside of a generals purview to concern themselves with this.