I get it, of course. The challenge is implementing this in a way that allows users to retain their existing work. Zap Cooking is completely self funded and has never received grant money, so you can imagine that a solution which creates a strong disincentive to start “new” while removing current interoperability is not optimal.

Users have also come to value that interoperability, especially with tools like npub.pro, and breaking that would be a disservice to them as well. I remain open minded and haven’t dismissed the idea entirely, and have come around to it more recently. I’ve put real time, money and effort into this project over the past few years, so these important considerations need to be weighed seriously.