| ▲ | barbazoo 3 days ago |
| Not only no weights. Not sure what people's expectations are but a lot of the time this isn't even valid code with all the redaction they did [1]. I'm confused as to who this is for, this surely isn't the repo they're working on, is it? [1] https://github.com/twitter/the-algorithm/blob/main/trust_and... |
|
| ▲ | Raed667 3 days ago | parent | next [-] |
| This is 100% for headlines and Musk to be able to say "we're open" during interviews. Its actual usefulness is not the point |
| |
| ▲ | Aurornis 3 days ago | parent | next [-] | | When they "open sourced" the Tesla Roadster the website only had a couple of mostly useless files. Discussion at the time https://news.ycombinator.com/item?id=38383099 Despite not containing more than a few random files, there were headlines everywhere about the "Open Source Tesla Roadster". There were countless comments, Tweets, and posts about how amazing it was that the Roadster was now open source. None of the people reporting on it or praising it actually looked at the files and realized you couldn't actually build anything other than the HVAC control board for the car. | |
| ▲ | pbasista 3 days ago | parent | prev [-] | | The reporters should be getting down to the point and asking Elon Musk about the practical usefulness of such a heavily redacted public release. | | |
| ▲ | morkalork 3 days ago | parent [-] | | I can think of like 3 institutions that have reporters who would ask that kind of question (The Register, Ars Technica and 404media) and I don't think Musk is going to be sitting across the table from any of them, ever. | | |
| ▲ | skissane 3 days ago | parent | next [-] | | > I can think of like 3 institutions that have reporters who would ask that kind of question (The Register, Ars Technica and 404media) and I don't think Musk is going to be sitting across the table from any of them, ever. Ars Technica’s space editor, Eric Berger, interviewed Musk only a few months back: https://arstechnica.com/space/2025/05/elon-musk-turns-his-fo... | |
| ▲ | simultsop 3 days ago | parent | prev [-] | | I believe these are the last kicks of a dying horse/bird... Why you take this so serious? The world is moving on. Nobody will trust anyone with their freedom of speech, ever. Is this so hard to see? Any centralized solution qucikly implements censoring, starts banning users. |
|
|
|
|
| ▲ | nextaccountic 3 days ago | parent | prev | next [-] |
| Are you talking about this? wandb_key = ...
wandb.login(...)
It's rather weird that they would add keys to the source code like this, rather than reading from the environment or some secrets service. Rather than redacting the source, they should refactor to remove the keys from the source |
| |
| ▲ | barbazoo 3 days ago | parent | next [-] | | One example, that's right. Another one: train_query = f"""
SELECT
{{feature_names}},
{",".join(labels)},
...
"""
and right at the top: cat_names = [
...
]
| |
| ▲ | mvdtnz 3 days ago | parent | prev | next [-] | | There's no way you got to this bit without skipping over multiple actual redactions, like SQL queries with all of the details replaced with ellipsis. Why are you cherry-picking one innocent instance when you know exactly what the parent comment is talking about? | |
| ▲ | bathtub365 3 days ago | parent | prev [-] | | Since it’s redacted we don’t know what was here. They could be redacting the names of the environment variables or other secrets names they use for credentials since a supply chain attack could more easily exfiltrate them if they know the name. |
|
|
| ▲ | Levitating 3 days ago | parent | prev | next [-] |
| what is your footnote referring to exactly? |
|
| ▲ | nativeit 3 days ago | parent | prev [-] |
| I know when I think “open source”, I am always thinking “heavily redacted”. /s |
