out of curiosity, why fortran? no disrespect. I wrote a lot of scientific software in the earlier days of my career and I learned fortran to update ocean modeling software.
From my experience building browser automation tools, the biggest challenge with most Chromium-based solutions is that their TLS fingerprint is a dead giveaway. Firefox-based approaches tend to fare much better against JA3/JA4 fingerprinting.
The key insight is moving fingerprint spoofing from the JS level (which is itself detectable) down to the native C++ level. It's a fundamentally different approach.
Love seeing niche Show HN projects like this. The choice of Fortran is wild but that's what makes it fun. As someone building small Mac utilities, I appreciate any project that proves you don't need a massive stack to ship something useful.
Whenever I hear about this AT protocol I think about the text-based commands to control cellular modems. I can't be the only one, r-right guise... r-right?
This was quite straightforward to code ’manually’, but we got stuck for some hours when trying to send the first message.
CPU topped, fans spinning, no message through. Analyzed, and after a while when we got same block the nth time, someone proposed Claude.
So Claude got the repo, prompted Claude:
”You got one job, why isn’t message through and why CPU usage high?”
He didn’t solve it. Probably could have if we kept Clauding.
But we found the problem. The issue was that the code was hitting the terminal 300 times trying to send the message :)
For clarity reasons Claude got the job to write the README, personally I don’t like that approach, but we got many other projects so time management basically.
We are building Cobolsky too.
Right now we are building the part to get images through using Apples old algo. Will be 576x720 using the Föoyd-Steinberg dither, 1984 Apple algorithm :)
27 comments
[ 2.7 ms ] story [ 34.7 ms ] threadTangential, but to the author, are there any FORTRAN codebases you feel are well designed?
- VCs band together to fund something shiny.
- Devs love shiny, helping spread the something.
- VCs enschitify it to get their coins back.
The key insight is moving fingerprint spoofing from the JS level (which is itself detectable) down to the native C++ level. It's a fundamentally different approach.
Interesting choice. Why?
https://www.patreon.com/posts/fortransky-we-in-153457794
This was quite straightforward to code ’manually’, but we got stuck for some hours when trying to send the first message. CPU topped, fans spinning, no message through. Analyzed, and after a while when we got same block the nth time, someone proposed Claude.
So Claude got the repo, prompted Claude:
”You got one job, why isn’t message through and why CPU usage high?”
He didn’t solve it. Probably could have if we kept Clauding.
But we found the problem. The issue was that the code was hitting the terminal 300 times trying to send the message :)
For clarity reasons Claude got the job to write the README, personally I don’t like that approach, but we got many other projects so time management basically.
We are building Cobolsky too.
Right now we are building the part to get images through using Apples old algo. Will be 576x720 using the Föoyd-Steinberg dither, 1984 Apple algorithm :)