My first interaction with a self-proclaimed Buddhist was in an Omegle chat where he opened with something like "the US staged 9/11", I guess in an attempt to rage-bait
Or what about how the first fifteen minutes of each season 2 episode is just "last time on..." and viewers decide they don't have the time for this shit
I've been saying this for a while: without opining whether or not machine learning models are even capable of consciousness, there's no way in hell LLMs are.
These are once-through, completely immutable models. Any activity that could be remotely construed as "thought" evaporates the instant it outputs a token, and then it starts over from scratch.
Good fucking luck being conscious when your consciousness only exists for a fraction of a fraction of a second at a time.
This would be incredibly hazardous to pass around as a bare pointer with no context, though. I'd expect to see this in a struct that, at minimum, also includes fields for the size of each dimension.
It's not enforced though, and there's no way as a consumer to see how a crate was published.
To be extremely fair, crates.io has a huge maintenance bottleneck because AFAIK it doesn't even have a single dedicated developer. But that's definitely a big part of the problem.
The Rust Foundation is really just not pulling in enough revenue to support the project properly. They really ought to figure out more revenue streams than just sponsorships and donations.
You can't overwrite previously published versions.
Application projects are recommended to check-in the Cargo.lock which pins dependency versions but you can always just run cargo update at any time which automatically upgrades all dependencies to the newest version allowed by the Cargo.toml.
Some projects get around this by pinning the dependency in the Cargo.toml (using =) or by vendoring all their dependencies, which is a huge pain in the ass.
Interestingly, developers in ecosystems like Go, Rust, and those utilizing native Web APIs—where robust standard libraries drastically reduce reliance on third-party code and strict cryptographic verification is built into the core toolchain—reported zero instances of a college dropout’s weekend project wiping out global logistics infrastructure today.
As someone who's built a career in Rust, it is 100% susceptible to an attack like this. The community is just generally paranoid enough to avoid depending on super niche packages.
Even so, Cargo still doesn't have code signing and crates.io doesn't have 2FA. They just barely rolled out email alerts for new crates being published with your API key.
And there's dozens of single-author crates that are depended upon by millions of lines of code, any one of which could easily be a vector in a supply chain attack. In fact there have been attempted supply chain attacks against crates.io, but to my knowledge they've all relied on typo-squatting.
The Internet gives us access to the kind of depths of human depravity on a daily basis that most people wouldn't have been exposed to in 1968, unless they had just gotten back from Vietnam.
Y'all need to read about the mutiny on Skylab 4: https://en.wikipedia.org/wiki/Skylab_4#Communications_break%3Fwprov=sfla1