ubikom VS http-add-on

Excellent client, btw. I have an issue open regarding this, but when I tried it seems to work fine. The client autoconfigured itself. If you are having issues with em client, please PM me or comment on the issue here: https://github.com/regnull/ubikom/issues/58

Thanks for reporting the issue. You can track it here: https://github.com/regnull/ubikom/issues/54

I'm working on https://ubikom.cc, end-to-end encrypted email service based on the concept of self-sovereign identity. Basically, you keep the encryption key, and all your messages are encrypted, on the wire or at rest. The core platform is open-source, the code is available here: https://github.com/regnull/ubikom

Billions of users use GMail (or similar services). These companies are making money by selling ads, and their "free" email service is just another way to improve ad targeting. Furthermore, your account can be disabled at any time and for any reason. Sure, you can switch to Protonmail, Tutanota, etc. because they are "good" companies. But why do you have to trust to any of them? Keep your encryption key, and have communication providers move around encrypted bytes on your behalf. Store your identity on a blockchain (maybe), so that no one can take it away.

That's the idea. If you'd like to work on something like this, get in touch. lgx (at) ubikom.cc

Shameless plug time! I'm working on 100% encrypted/authenticated email based on Self-Sovereign Identity and decentralized key registry, check it out at https://github.com/regnull/ubikom

KEDA ships with an HTTP add-on to enable HTTP scaling.

KEDA has a special scaler that creates an HTTP proxy that measures and buffers requests before they reach the app.

I am a core maintainer on the KEDA HTTP Addon project (https://github.com/kedacore/http-add-on). It's 100% written in Go and we are a small group looking for additional contributors. I believe there are interesting challenges ahead of us that will be enjoyable to solve.

If you're interested, please reach out. My username here is the same as my username on the Gophers and Kubernetes slack groups.

(You're of course welcome to just go pick up an issue in the repo if you'd prefer)

The KEDA HTTP Addon project contains three major components: the operator, scaler and interceptor.

Hacking on the KEDA HTTP Addon, I found myself having to do something familiar:

First, we need to finish the minimal infrastructure. The components and supporting artifacts (Helm charts, CI scripts, etc...) are being built in PR #2, and once we have them completed, we will merge it [5]. Second, we need to establish a roadmap. We're beginning to outline it now and will finish it shortly after merging.