Lessons from Implementing NIP-34 in Flotilla-Budabit
At the Flotilla-Budabit project we’re building a Nostr-native Git-centric collaboration client based on Flotilla. NIP-34 is the backbone: it defines how repositories are announced, how repository state is broadcast, how patches and issues are represented, and how status is tracked - using plain Nostr events. NIP-22 supplies the comment threading model, and NIP-32 defines a general labeling system we can apply across those objects.
After multiple iterations, we've done some reflecting on what worked, what didn’t, and the exact event shapes and cross-NIP interactions we implemented (and wrestled with) and we're sharing it here with you.
