HackerTrans
TopNewTrendsCommentsPastAskShowJobs

thestackfox

no profile record

Submissions

What Codex Chooses (Vs Claude Code)

amplifying.ai
5 points·by thestackfox·4 ay önce·0 comments

Show HN: Stack Status – Tracking outages across the internet's underlying stack

stackfox.co
3 points·by thestackfox·5 ay önce·0 comments

Cloudflare adds real-time Markdown rendering for AI agents

blog.cloudflare.com
48 points·by thestackfox·5 ay önce·22 comments

comments

thestackfox
·4 ay önce·discuss
Respect. But also ... WHY????

Now let's do

(1) A DNS file drop: Split small files into TXT records and rebuild them client-side. Useless for big files, perfect for config blobs, tiny payloads, and cursed demos. Also someone can write an S3-compatible client.

(2) Redis DNS:

- GET foo.cache.example.com -> TXT record returns value chunks

- TTL is the eviction policy

- Cache invalidation becomes even more of a hate crime.
thestackfox
·5 ay önce·discuss
I get the sentiment, but "I don’t like magic" feels like a luxury belief.

Electricity is magic. TCP is magic. Browsers are hall-of-mirrors magic. You’ll never understand 1% of what Chromium does, and yet we all ship code on top of it every day without reading the source.

Drawing the line at React or LLMs feels arbitrary. The world keeps moving up the abstraction ladder because that’s how progress works; we stand on layers we don’t fully understand so we can build the next ones. And yes LLM outputs are probabilistic, but that's how random CSS rendering bugs felt to me before React took care of them

The cost isn’t magic; the cost is using magic you don’t document or operationalize.
thestackfox
·5 ay önce·discuss
If you’re willing to serve adversarial Markdown to agents, you’re already willing to cloak HTML.
thestackfox
·5 ay önce·discuss
Nicely done. I poke at DNS a bit over at StackFox (https://stackfox.co/site/wirewiki.com), and anyone who’s spent time looking at DNS knows how much work goes into this.

A couple thoughts:

1) Nameserver “redundancy” that isn’t. All the ns1/ns2 setups that collapse onto the same provider or ASN once you follow the trail.

2) Authoritative drift. One server quietly serving an older serial or odd TTL for a while — invisible until something breaks. With global data, quirks like that become obvious.

Anyway, inspiring job. Wirewiki already feels like something that should have existed but somehow didn’t.