the_angry_angel

Cap completely ate several recordings for me. Admittedly they were over an hour long, and I should’ve broken them up a bit, and perhaps it’s not what it’s used for. Switched back to OBS, while it’s not as easy to use it’s pretty reliable

There’s support via Barman cloud - we use it for azure at work but s3 and others are supported iirc

Kopia is awesome. With exception to it’s retention policies, but work like no other backup software that I’ve experienced to date. I don’t know if it’s just my stupidity, being stuck in 20 year thinking or just the fact it’s different. But for me, it feels like a footgun.

The fact that Kopia has a UI is awesome for non-technical users.

I migrated off restic due to memory usage, to Kopia. I am currently debating switching back to restic purely because of how retention works.

Coming up to 37 and for the last few weeks I’ve had the same sort of realisation - reading novels seems to take more concentration than it should, and I’ve become lazy with maths.

I’ve had an eye check, a few months back a general medical. Both were fine/no significant changes. I rarely drink, no drugs. I feared a series of migraines might been response but I’ve been assured otherwise.

I so far figured it’s too much skim reading, a lot of very poor sleep, being on the edge of burn out and maybe a touch of post COVID brain fog.

Your post is encouraging me to start doing something about it.

I don’t have much to add but it’s reassuring to know that I’m not alone

Teleport I feel solves this well, from an organisation perspective

Just to echo this, I’m currently using a crate called deku (for a toy project to learn rust). Deku is a wrapper on top of bitvec which lets you annotate structs and enums for decoding and encoding. The speed I was able to implement a binary TCPStream encoder/decoder was great. Both have been rock solid for me.

Highly recommend both libraries!

> I hear this all the time, but I question how true it is. I've been running my own mail servers for decades, and I've never had any problems with sending or receiving mail. I suspect anyone who properly configures their server will be fine.

At work I ran email servers professionally and with good deliverability for years. My own email server was arguably longer lived than those at work, just much lower volumes. IP block was clean, DKIM, SPF, rDNS, etc. all setup correctly.

I thought I had no deliverability issues. I interacted with mailing lists regularly, the odd email to friends and family and I was firmly in your camp until I had to deal with a death in the family.

I think this was shortly after Microsoft BPOS became Office365. It became very very clear very very rapidly that to certain orgs I just wasn't hitting the inbox. And there was jack shit I could do about it. That was the end of my mail server, and it's certainly got worse over time.

> I doubt most medium to large companies I see implementing Kubernetes could be considered a good fit for Kubernetes. If you want to run on-prem / colo you are probably better of with something simpler like Nomad.

Our path has been Ansible -> Ansible+Docker -> Docker Swarm -> k8s. We absolutely don't need k8s, but the other options all had downsides.

1. Nomad was on our list and probably would've been better, but there were no managed Nomad solutions at the time and it was not as widely used as other solutions

2. Our time on Swarm was /ok/, but it was more and more obvious that being on the lesser walked path was a problem, and it's future made us run away from it

3. k8s gave us a nice declarative deployment mechanism

4. We can switch to a managed solution down the road with less friction