0 Followers
0 Following
1 Posts
I got the Sennheisser Momentum 4 and couldn’t be happier with them. The ANC is great, and they are very comfortable to wear all day long. The battery life is also just incredible. They really do last 60 hours, if not more.
Komodo works really well for this and is fairly easy to setup.

I recently installed Pangolin in Hetzner and spun up a statefulset in my k3s cluster for the Newt container. It works beautifully. With it you can proxy Pangolin to the cluster address of your service very easily.

For example: sonarr.media.svc.cluster.local:8989 Format being: deploymentName.namespace.svc.cluster.local

Internally I still use Traefik for my services and just left all the CNAMEs in PiHole pointed to Traefik but if you are external your DNS would look at what’s public on my domain and route through Pangolin.

Haha. You aren’t wrong. But just rotate the key after. Also, there are plenty of secure delivery methods and encrypted delivery options.
You have a point. But Bitlocker recovery keys are all numeric. Really not all that hard to translate over the phone. Typically a secure email is what we use to deliver since 99% of employees also have email on their mobile devices.

I think your approach to monetizing towards companies is great and you should totally do that. As someone that works with an RMM everyday and I’ve tried nearly all the big box ones. They all suck. So seeing something new in this space is great. Especially if it works.

I think restricting the home lab level to 1-3 sites could be a viable path? Maybe even license agreement stating not to be used for business without subscription (you might already do this, I didn’t read the license)? I’d expect that to be hard to enforce though.

I did read a bit about the self compiling and think that’s a good idea and totally could have signed up with an alias email. But for me, when I want to test something I want it to be a quick docker/k3s deploy. Could you publish your docker containers for home lab, maybe restricting bare metal installs to a license would deter companies from installing due to most in house IT wanting things on VMs or bare metal.

This does look great. I’d love to see a free “home lab” license option without having to sign up for something or create an account. The information on your pricing page could use more detail on the “Did you know? You can start with a free open-source membership through our Members Portal” section.
It’s a good idea. Also, domains are pretty cheap so I feel it a worthwhile yearly expense.
I’ve used addy.io for years and never had a site reject my alias. But I might do things differently than you. I own two domains for emails. My main one that is configured with Mailbox.org. And my secondary domain has its MX records set for addy.io. So when I create an alias I just make it at [email protected]. This is probably why I’ve never seen a service block me. I have seen lists on GitHub for companies to use in their code to block alias emails, and addy.io was in there. Are your aliases generated using their domains?
Adding a custom domain | addy.io

This article guides you through the steps to add a custom domain on addy.io. This allows you to receive and send email from your own domain through the service.

It’s the airdrop a contact feature. Hold another, phone or even yours, up to it and it will trigger it.