This symptom was affecting display of numbers in the TUI, but the real bug/design flaw is using jq or JSON as a transport mechanism between components or between tools. JSON's number range is famously poor and it even architecture-dependent. So if you use jq or JSON to connect components or tools, you will have this same problem silently occurring elsewhere without visibility in the UI.
This is a bigger deal than it seems like! A confidence-inducing fix would include a blog post describing a top-to-bottom audit of jq/JSON used as a transport layer between tools and components. Not just a patch to the most visible problem.
Fellow alien here. Agree with Andre. Just embrace who you are and give it time. You've got a lot of life left to live and plenty of time to find fellow aliens to hang with.
My partner and I are creating a product every month this year (https://12products.xyz) so every product in this project is "I don't care if this success".
You do have it like you have any other digital clout (likes on an Instagram post for example). Perhaps with younger generations spending more and more time on digital devices, proving you have something in a digital wallet is just as good as owning the physical thing. Maybe it's even better.
I struggle to see the value (some CryptoPunks are going for outrageous prices). That being said, I think we are early days. I find these types of innovations to be interesting and want to see where it goes.
I build a tool for residents at care homes to find pen pals around the world.
I didn't try to get care homes on board so the project basically died upon launch. Sometimes I think about trying to go for it or make it just a general pen pal service instead...
Also, for clarification, this bug was only impacting the display of numbers in the TUI, not what the model sees. The model sees raw results from bash.