Show HN: We built a terminal-only Bluesky / AT Proto client written in Fortran
FormerLabFred
65 points
35 comments
March 20, 2026
Yes, that Fortran.
Related Discussions
Found 5 related stories in 60.7ms across 3,471 title embeddings via pgvector HNSW
- Show HN: Skir – like Protocol Buffer but better gepheum · 72 pts · March 08, 2026 · 54% similar
- Show HN: Horizon – GPU-accelerated infinite-canvas terminal in Rust petersunde · 60 pts · March 17, 2026 · 54% similar
- Show HN: Terminal-Style Portfolio on the Internet kuberwastaken · 22 pts · March 01, 2026 · 54% similar
- Show HN: Tmux-IDE, OSS agent-first terminal IDE thijsverreck · 75 pts · March 18, 2026 · 54% similar
- Show HN: Gridland: make terminal apps that also run in the browser rothific · 76 pts · March 24, 2026 · 52% similar
Discussion Highlights (11 comments)
cat-turner
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.
blundergoat
fortran > cobol
uberdru
The world is a better place for this app. Wonderful!
hk1337
Are there any other AT protocol apps that aren’t derivatives of bluesky? By that I mean, not social media feed related, twitter clone.
h4ch1
It's always nice to see production codebases in languages that you've never used but are interested in. Tangential, but to the author, are there any FORTRAN codebases you feel are well designed?
aimarketintel
AT Protocol is a joy to build on — open public data, structured JSON, zero auth friction. I built a Bluesky scraper using the same endpoints and it's one of the most stable scrapers I have. Great to see more tools for this ecosystem.
nerdypepper
y'all gotta throw this up on https://tangled.org ;)
zoom6628
Brilliant in every possible way. Fortran was first language I learnt at high school in its "PORTRAN" variant.
isodev
On ATProto: it’s funny how we never learn the lesson: - VCs band together to fund something shiny. - Devs love shiny, helping spread the something. - VCs enschitify it to get their coins back.
Ashkaan
Oh this is cool
youhai
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.