Git is not a network though. And I wouldn't bother building an alternative to Git if I never faced a need that can't be satisfied by Git.

So if the need never really came up, or if you then showed me how to satisfy it with just Git, I would do that.

But the argument of networks should not be abused for non network stuff. For example, we gain nothing from interop with Oauth, when we are only authorising our apps to our homeservers, so inventing something simpler and more fit to our need than Oauth is the right decision, and it doesn't matter how old or tested Oauth is.

Specific arguments are not universal dogma, they need context and judgment to apply to other situations.

Regardless, even if we built our own sync system, it doesn't affect anyone who would rather ignore it. Some of their flows might suffer (like continous mirroring and backup), or it might not suffer because they use Git and they are satisfied with that, but as long they stick to Pkarr, HTTP, and the simple PUT,GET, DELETE apis, apps will just work.

We are dedicated to the simplest setup necessary to achieve our goals, but not any more simpler. Worshipping simplicity too far result in sacrificing important features, like proper key management in Nostr. By definition managing Pubky keys is going to be more complex (spec wise) but offering nicer UX, and that is the balance.