fiatjaf on Nostr: If you know what is your desired "state" (as represented by the kind:30618 event) you ...

If you know what is your desired "state" (as represented by the kind:30618 event) you just push it everywhere and do the git push afterwards (that's what `nak git push` does), so 2222 will just catch up automatically.

The concept of "force-pushing" isn't really a thing from the grasp server perspective. The grasp server will accept any pushes that match the signed state they received.

Essentially the --force flag only exists to discard the client-side default safeguards against overwriting the state that you have locally.

To answer your question: if you force-push once while 2222 is down you won't need to force-push again after 2222 is back online.