Hi Nusenu, I am reopening this thread because I want us to be on the same side here, but let me start by saying your feedback during the Happy Families work in C Tor was genuinely useful, and it made the feature easier to integrate with tools like yours. A bit of context on why we are moving carefully here. Happy Families came out of the Walking Onions design work for Arti, where MyFamily does not scale. We backported it to C Tor because relay operators were hitting real pain: descriptor size limits as AuthDirMaxServersPerAddr went from 2 to 4 to 8, and the quadratic MyFamily configuration burden that ansible-relayor exists to smooth over. To give you some context. What we are trying to avoid is breaking clients that are still out there and that we do not fully understand. That is why I would rather spend the next few months (just over 1 month really at this point) nudging downstream distributions toward 0.4.9.x than accelerate adoption. People have waited a long time for Happy Families, and a few more months of MyFamily pain is a trade I think most operators would accept. On the framing: I do not see this as "relay operators vs. torproject.org". My ask is specifically to you as the maintainer of a widely used configuration tool, in the same way we would raise it with any tool that steers Tor toward behaviour we are recommending against. Concretely, what I am asking is that you revert the 17-line diff and cut a release. A note on the GitHub tarball page will not reach people, since most users pull ansible-relayor as a Git submodule or from Ansible Galaxy. How you handle support and releases beyond that is entirely your call. Would you be open to that? -hiro