Readit Newsnmadden commented on Report: Tim Cook could step down as Apple CEO 'as soon as next year' 9to5mac.com/2025/11/14/ti... · Posted by u/achow
That's what I learnt from as part of CS curriculum at MiMUW. Can recommend:
https://en.wikipedia.org/wiki/Introduction_to_Automata_Theor...
Not sure why you're being downvoted for recommending a classic textbook!
we’ll ask, “What’s the simplest possible computing machine that can recognize balanced parentheses?”
A counter. That's the difference between theory and practice. Because in practice, everything is finite.
> Because in practice, everything is finite.
Indeed! https://neilmadden.blog/2019/02/24/why-you-really-can-parse-...
nmadden commented on Claude Code can debug low-level cryptography words.filippo.io/claude-d... · Posted by u/Bogdanp
I love D2; I just wish ELK were the default layout engine; it is extremely rare that Dagre does a better job than ELK, and it took me a while using D2 before I discovered the layout-engine property.
The proprietary/commercial TALA engine is really excellent too. I’ve been using it to do complex dataflow diagrams, and the results are so incredibly well laid out.
nmadden commented on A modern approach to preventing CSRF in Go alexedwards.net/blog/prev... · Posted by u/todsacerdoti
If your case is just supporting browsers and not things like curl this seems fine. But when the headers are not set the CSRF protections are "disabled" exactly to support this case, that you may want to do this request using something like curl.
I guess. But it would only impact you if you’re using cookies with curl (I assume the middleware is only applied to requests with cookies?) — and it seems pretty easy to add a -H ‘sec-fetch-site: none’ in that case.
nmadden commented on A modern approach to preventing CSRF in Go alexedwards.net/blog/prev... · Posted by u/todsacerdoti
I don't understand - the article is literally about origin/Sec-Fetch-Site
The article has a whole section about requiring those headers by forcing the use of TLS 1.3 — the theory being that browsers modern enough to support 1.3 are also modern enough to support the headers. But why not just enforce the headers?
nmadden commented on A modern approach to preventing CSRF in Go alexedwards.net/blog/prev... · Posted by u/todsacerdoti
Enforcing TLS 1.3 seems like a roundabout way to enforce this. Why not simply block requests that don’t have an Origin/Sec-Fetch-Site header?
Crashing is not an outage. It’s a restart and a stack trace for you to fix.
Are you in the right thread?