lsofzz's comments

On: A few CPU hardware bugs

[lsofzz]

> Rockchip calendars

>.< haha i remember this

On: HTTP Cats

[lsofzz]

Haha made my day

On: Confer – End to end encrypted AI chat

[lsofzz]

MM is basically up-selling his _Signal_ trust score. Granted, Signal/RedPhone predecessor upped the game but calling this E2E encrypted AI chat is a bit of a stretch..

On: Confer – End to end encrypted AI chat

[lsofzz]

Go read a book on basic cryptography. Please.

[charcircuit → lsofzz]

I have read through Handbook of Applied Cryptography.

On: I'm a Tech Lead, and nobody listens to me. What should I do?

[lsofzz]

> I'm a Tech Lead, and nobody listens to me. What should I do?

TL;DidntRead

Precisely. Take the `TL` title out the door. Take the `ego` out the door.

Then, step in the door - as a friend, with empathy, proactive listening and support the engineers.

Round-table `discussions`. Not Waterfall.

My 2 cents.

On: Writing "/etc/hosts" breaks the Substack editor

[lsofzz]

> The people configuring WAF rules at CDNs tend to do a poor job understanding sites and services that discuss technical content. It's not just Cloudflare, Akamai has the same problem.

I agree. There is a business opportunity here. Right in the middle of your sentences.

Hint: Context-Aware WAF.

Many platforms have emerged in the last decade - some called it smart WAF, some called it nextgen WAF.. All vaporware garbage that consumes tons and tons of system resource and still manages to do a shit job of _actually_ WAF'ing web requests.

To be truly context-aware, you need to compute a priori about the situation - the user, the page, the interactions etc.

On: Rules for writing software tutorials

[lsofzz]

Thank you.

On: Async Rust is not safe with io_uring

[lsofzz]

<3

On: Using Rust in non-Rust servers to improve performance

[lsofzz]

<3

On: GitOpper: GitOps Without Kubernetes

[lsofzz]

> Bottom line is: GitOps means the source of truth is Git and automation makes sure to avoid drifts. You still have to have a rollout strategy and schedule that makes sense for your usecase.

THIS.