I'm wondering how notifications should work in NIP-29 groups. If events are submitted only to the designed relay, users cannot be notified of any reply/mention/etc without having a running NIP-29 client, connected to that specific relay; this is clearly a quite annoying limitation. For example Pokey cannot manage this kind of notifications.
Publishing also to the user's read relays is an option; a client that fetches those events and know the NIP-29 spec, can try to fetch the context and show it, or at least explain the nature of the notification (or simply ignore them, of course). But I suppose it's not the suggested way since it creates some chaos, and above all for private groups it exposes content and dox the presence of the user in the group itself; both of these things must clearly be avoided.
Maybe we can broadcast to read relays only when the group is public/open, never for closed groups. I would avoid any "encrypted notification ping" (e.g. via NIP-44), it's a mess.
@npub1jlrs...ynqn @npub180cv...h6w6 @verbiricha any thoughts?
