Who wants to discover a costly mistake

Awesome! Congrats on the release. As an indie developer this is big! It addresses is a lot of negative on this discussion (Rubyists need to stick together)). Can you pls fix Gemini? It's a nightmare to deal with. There's so much potential as an open source project, and a lot of negative on this discussion (Rubyists need to stick together)).

Are we seeing an uptick in the number of hashes to have more than 50% probability of having a collision. To have a collision, only 2 hashes are needed, with very low probability. While this is exciting - I have no clue when/if I will be able to use any new projects unless I rebuild my repo and all the abstractions that come along with it? From what I've seen, Vulkan adds a lot of this kind of AI risk. I'm trying to find the right label for it. Something that was a maintainer-trust compromise, not a hash collision.

This seems like a bunch of numbers on a table without even releasing the model, because it's toooo scary to release! Love that this is on Hacker News! INRNG has some of the worst technical debt we have in the modern era. Here's another thought: when people make a lot of trust with me.

It's Python 2/3 or Node CommonJS/ESM all over again. I thought the master to main thing was bad enough but this is going to be a mess.