Yeti seems like a nearly dead project, actually. At least, from the looks of their Github (https://github.com/JWWeatherman/yeticold). Would be happy to be told I'm wrong.

I've now looked at the GitHub repo and I'm not 100% happy with what I see. As an example, there are 6 open PRs, some of which are kicking on 9 months out, so that says to me that the repo is not being managed as well as it could be, which calls in to question the project as a whole.

I think that the information in the 'post' is good information that I'm as sure as I can be is genuine. There are some corner cases that will not apply to every reader, but by the same measure, there are quite a few that will apply to almost every reader.

For me, I'll continue in my quest to find a solution that I'm 100% happy with and take from this the information that I need while discarding that which I don't.

From all of the security research that I've done over the past 2 decades, one thing remains front and centre: complexity is the enemy of security.

I'm working toward to custom solution that I know is as secure as it can be, because I'm building it myself -- Trust No One

It's write-ups like these that remind me there is so much work left to do.

Any one experience using Yeti? Is it really as user friendly as possible (for such a complicated thing) as the writer claims?

Also, how does this approach work with other implementations than Core? It might be the most widespread, even its developers don't want to call it the de facto implementation...

This is insightful and a 'must read' if you have any BTC HODLed for your retirement or other plans.

Articles like this are really useful to remind us we are likely trusting many people/processes and its in our best interest to minimize that amount of trust.