mlhpdx

Exactly that. No knock, no answer.

One of the fundamentally great things about the Wireguard protocol is the simplicity. A small codebase can implement it, and that’s lead to some great libraries and innovation.

Another great (and subtle) thing is the monotonically increasing sequence number. Note that it isn’t incrementing, like DTLS. This small thing makes it so much easier to implement with efficient concurrency, and event external state (i.e. distributed concurrency).

That latter bit we’ve done in our own library.

Edit: typo, don’t -> done

I’m optimistic about NHP being the middle ground solution for a lot of things. With OS support it can be transparent to users yet still effective.

Is the Network Infrastructure Hiding Protocol work at IEEE going to help thwart AI assisted attacks, if adopted?

Having employees (or system like bastion hosts) with unrestricted access is one of the recurring mistakes in such events. I can’t understand it.

> All of them modern "we keep your content safe" players

But they weren’t and probably aren’t and won’t be. They just put forth an image as much as needed to sell.

Congratulations on this automation, which I know from first-hand experience is very difficult to pull off.

Is the robot really working with individual boards and not panels? How do you deal with balancing copper area, and varying etch times?

People often focus on the assembly side as “hard” but quick-turn manufacturing of the PCB is vicious.

QUIC for embedded? I haven’t seen that, but there is a lot of DTLS. Particularly with 1.3, it makes QUIC look like a behemoth in code.

> Support for DTLS 1.3 (RFC 9147). Refer to the ossl-guide-dtlsv13(7) manual page for details.

DTLS 1.3 is a huge improvement over 1.2 for efficiency and simplicity. I can’t speak to the OpenSSL implementation but it’s great that support is finally released.

That’s pretty brazen, even in this day. If Perplexity is making money from a project to reverse engineer something patent protected, I’d imagine that would be crossing a line. Buy perhaps not in today’s world?

Edit: parent -> patent

I like the approach of rendering directly to SVG, which is what I want -- running layout once and caching the result in the browser or on the server side.

Putting reverse indexes in S3 alongside large aggregate log objects has been an effective pattern for more than a decade. With objects in cheap access modes and indexes in modes that are cheaper to access it becomes far more cost effective than most options (cheap S3 clones aside).

The earliest code I have to do this looks to have been created in 2012.

Separation of compute and storage is such a fabulous pattern.

The change in lifestyle expectations should be as well documented as the changes in social contact.