along with the tag limits, I think we need a better approach for addressing NIP29 groups. I don't know maybe something like nostr:ngroup1 🤷‍♂️

Reply to this note

Please Login to reply.

Discussion

Group = Relay = Npub

Avoids so much of these complications.

how do you think we should send a group link to a friend?

Depends what your goal is.

You can just share the Npub like you do for users.

But most will instead want to invite others to experience a community **in a specific app**. For that there's several options:

For Web Apps you can share a URL of the group/community:

- this link can be personalized to the receiving user

- this link can end with the npub so other apps can pick up on it

For Native Apps I'm currently breaking my head on how I want to do this. I have this strong hunch that there's something really awesome that you can do when the community **is** a relay/media server. As in:

- it has a domain

- it can store events, file hashes and even the files (apk's etc...) itselves

- it can whitelist npubs (throw-away npubs included) for access to those events and files

- with cashu you can even set a little starter's budget aside for the invitee

Maybe nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 invites is the 🐐 solution tho.

You get invited to a community and have the apps to best interact with said community right there for you to install. As recommended by the community itself.

iirc there was a proposal by nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 to add nchat references, they probably can be used to reference groupchats

I think nip29 groups should have standard unique ids just like our pubkeys (nprofile), something like `ngroup` which also includes its relay url.