ManiMe on Nostr: I think invites are more than just a collection nip 51 lists. They will need expiry ...

I think invites are more than just a collection nip 51 lists. They will need expiry options and reciept generation and other features specific to “inviting and onboarding”. A lot of us are working in this problem in silos… but we don’t seem to be aligned. Maybe good thing that bluesky has forced the issue…

quoting
note166f…pt45

That’s what hodlbod (npub1jlr…ynqn) said and also Vitor Pamplona (npub1gcx…nj5z) … and others.

https://github.com/nostr-protocol/nips/issues/1062

The problem is … we’re not problem solving together, and each of us get tangled in our own patch of technical weeds.

- what is the actual problem being solved with “invites”?
- who (stakeholders) would benefit, for which solutions design should always be targeted?
- what would (a family of) MVP solutions look like, whereby each of our projects could be aligned in tackling the problem from different angles?

Decentralized is great … but sometimes we just need to get on the same page.

Here’s why:
note1t96…3eqy