Braydon Fuller on Nostr: In my opinion it should be part of the core specification and widely implemented ...
In my opinion it should be part of the core specification and widely implemented (e.g. mandatory).
It's very important for decentralization and simplifying the complexity of NIP-65 "outbox model" for clients. Relays won't always be online and events/notes during that time could be missed. Negentropy syncing helps that in an efficient way and reduces the need to recieve duplicate events from other relays. Furthermore, each client doesn't need to implement full NIP-65 support and can be a viewer into your relay (which does support full NIP-65 for you). That is important because there is a wide range of Nostr use cases from git collaboration, video channels, podcasts, notes (and even as Vitor Pamplona (nprofile…deau) mentions, medical data). Each of those I think will most likely be best as individual apps.
Note however that mandatory doesn't mean it's always enabled for all users at all times, just as writing to a relay is mandatory but many only let a set of pubkeys write to it.
It's very important for decentralization and simplifying the complexity of NIP-65 "outbox model" for clients. Relays won't always be online and events/notes during that time could be missed. Negentropy syncing helps that in an efficient way and reduces the need to recieve duplicate events from other relays. Furthermore, each client doesn't need to implement full NIP-65 support and can be a viewer into your relay (which does support full NIP-65 for you). That is important because there is a wide range of Nostr use cases from git collaboration, video channels, podcasts, notes (and even as Vitor Pamplona (nprofile…deau) mentions, medical data). Each of those I think will most likely be best as individual apps.
Note however that mandatory doesn't mean it's always enabled for all users at all times, just as writing to a relay is mandatory but many only let a set of pubkeys write to it.