HackerTrans
TopNewTrendsCommentsPastAskShowJobs

otterwilde2

no profile record

Submissions

[untitled]

1 points·by otterwilde2·last month·0 comments

Meta's AI agent for WhatsApp Business is now available globally

techcrunch.com
1 points·by otterwilde2·last month·1 comments

[untitled]

1 points·by otterwilde2·last month·0 comments

[untitled]

1 points·by otterwilde2·last month·0 comments

[untitled]

1 points·by otterwilde2·last month·0 comments

[untitled]

1 points·by otterwilde2·2 months ago·0 comments

[untitled]

1 points·by otterwilde2·2 months ago·0 comments

[untitled]

1 points·by otterwilde2·2 months ago·0 comments

[untitled]

1 points·by otterwilde2·2 months ago·0 comments

How TCP Works – Handshake, Sequence Numbers, Congestion Control

toolkit.whysonil.dev
5 points·by otterwilde2·2 months ago·0 comments

HTTPS: The Three Guarantees and the Handshake Beneath

toolkit.whysonil.dev
2 points·by otterwilde2·2 months ago·0 comments

Systems Are Visual – This Is a Better Way to Write Them

toolkit.whysonil.dev
4 points·by otterwilde2·2 months ago·0 comments

Show HN: What happens when you load a webpage (Interactive)

toolkit.whysonil.dev
32 points·by otterwilde2·3 months ago·9 comments

comments

otterwilde2
·2 months ago·discuss
The whole UI could use a polish. The About, How To Use pages don't work either.

Also, how are you planning on integrating these ads with llms?
otterwilde2
·2 months ago·discuss
thanks.
otterwilde2
·4 months ago·discuss
The step-by-step timeline format is really well done. I've bookmarked the OAuth page specifically — explaining the redirect flow visually makes it so much clearer than the spec's wall of text.

One thing I'd love to see added: a WebSocket upgrade visualization. The initial HTTP handshake → 101 Switching Protocols → full-duplex flow is something a lot of devs use daily (via Socket.io or similar) but never actually understand at the protocol level. It would fit perfectly with your existing format.

Also, the HTTPS section could benefit from showing the 0-RTT resumption failure case — what happens when the server rejects the early data and falls back to a full handshake. That's the part that catches people off guard in production when they're debugging intermittent TLS issues.

Really nice work overall. These kinds of interactive explainers stick way better than reading RFCs.