pyritschard

It refers to a technique also known as "port knocking" which consists of leaving a port closed by default and opening it upon receiving a message by another channel (in this case, a UDP packet).

It was mostly in use when TLS hadn't made it's way into most common protocols

We still intend to publish the successor to Pithos at some point, it has seen a large overhaul in terms of how metadata is handled and relies on a in-house system for blob storage.

This is great news. At Exoscale we are now using Clubhouse but keep tracking product descriptions and design documents + ADRs outside of it. Tying these to the in-flight epics would be a very welcome change.

One can only hope it will remain engineer friendly and allow for reviews and good text formats.

Hey, Exoscale CTO here,

Thanks for looking into the service. We're certainly not the cheapest in terms of pricing but I would also warn against using RAM prices as the sole way to gauge a service.

To drive low prices a lot of VPS providers tend to have a very liberal way of playing with overcommit, which we don't do. The same goes for CPU.

Our instances should be considered to higher-end families such as the C3 and here you'll see we're playing in the same field in terms of prices.

Exoscale sits in the middle between AWS and Digital Ocean. It has a much narrower catalog than that of AWS but essential services needed to drive cloud application.

Yes, I've read and see the difference from schema. The huge advantage with this, is that even though the approach is different, it supersedes schema's abilities and it will be a require away for every library and application author.

We also owe the OpenBSD team OpenSSH, which greatly benefits from their attention to detail and commitment to small improvements towards better security.

Of course software is never perfect, but it's nice to know the (small) subset of OpenBSD developers working on OpenSSH are still working on keeping the proverbial doors locked.