Interesting reasoning about what is hard in systems with concurrency. It's definitely about the state space of the system and the structure of that space.

Good musing about complexity. Very often we need to move it around, the important question is where should it appear. For sure you don't want it scattered everywhere.

Now this is definitely a smart trick to estimate position in tunnels.

It shouldn't be, but it is a big deal. Having such training corpus openly available is one of the big missing pieces to build models.

Nice chain of attacks. This shows more than one vulnerability needs to be leveraged to lead to root access. This provides valuable lessons.

This is a nice view into how a query planner roughly works and a nice algorithm which can be used internally to properly estimate the number of distinct values in a column.

The title says it all. This is very fragmented and there are several options to fulfill the task. Knowing the tradeoffs can be handy.

Interesting musing on the heuristics we use when solving problems. There are good advices in there to make progress and become a better developer.

Avoiding boolean parameters in library APIs should be a well known advice by now. Still they should probably be avoided when modeling domain types as well.

Definitely a good post. No you don't have to go all in with cloud providers and signing with your blood. It's often much more expensive for little gain but much more complexity and vendor lock in.

This is an interesting and balanced view. Also nice to see that local inference is really getting closer. This is mostly a UI problem now.

Fascinating research about side-channel attacks. Learned a lot about them and website fingerprinting here. Also interesting the explanations of how the use of machine learning models can actually get in the way of proper understanding of the side-channel really used by an attack which can prevent developing actually useful counter-measures.

Looks like a nice way to improve handling of merge conflicts. I'll test this one out.

Could XMPP make a come back if the user experience was better?

I didn't know the voting rolls were public record in the US... this is a really bad idea.

If you wonder how the protocol is designed and how the actual implementation works, this is a nice introduction. Clearly it's helped by the size of that program which is fairly small.

Looks like there are people out there to get Tor relays down... and they found a smart networking trick I'd expect to not work anymore.

A bit biased toward stable product teams only. Still, there are good tips which are more widely applicable here. This gives a good idea of the management of a distributed team of remote workers.

Interesting explanation of the different visions and governance behind ActivityPub and ATProto.

Each has a use, they shouldn't be conflated. It makes for poor user experience and accessibility otherwise.