How to invite other users into the group

[hitohata]

Agenda

In this system, to share the container, the user needs to invite other users into the group. In this discussion, decide how to invite other users into the user's group.

For now, @kotaaaa suggested the following process:

Let's say user A tries to share the group with user B.

First, the Frontend accesses the '/group/{groupId}/share' API. Then it API returns Hash data that is generated by some logic within the Backend.
-> User A gets a link address, like https://{nishiki-domain}/json/{hashValue}.
-> User A shares that link with User B.
-> User B accesses that link.
-> Inside the Frontend used by User B calls Backend API, /groups/{groupId}/join/{hashValue}.
-> Then User B joining the group is accomplished.

[hitohata]

I think @kotaaaa 's way sounds good.
I plan to create the Hash Value from Group ID and The timestamp which is a link expired Datetime.
And I'd like to make sure one thing, that we don't need to specify the user. Is this specification correct?

[hitohata]

@kotaaaa
OK. The selectability is not a priority, so let's discard its feature for now.
Is the default expiry time 7 days enough? It is just my sense but it feels too long (this time is not important for now though).

[kotaaaa]

Any number from 1 day to 7 day is ok for me (I suppose 3 day is the best for this function).
@uskayyyyy Can I get your opinion for this point?

And 1 question, will a new link be issued every time users click the Copy Link button? or existing links should be returned as long as they have a valid expiry time?

[hitohata]

And 1 question, will a new link be issued every time users click the Copy Link button? or existing links should be returned as long as they have a valid expiry time?

Oh, I overlooked that situation. I think when the button is clicked, the previous one should be disabled and a new link will be created.

[kotaaaa]

Oh, I overlooked that situation. I think when the button is clicked, the previous one should be disabled and a new link will be created.

If so, some user might know unexpectedly that the link is disabled when new link is issued by other user in the same group because according to the above discussion, this link will be issued uniquely by each group.
Is that permitted?

I summarized 4 candidate patterns. Please vote or comment whatever you want.

• 1, create a new link every time the button is pushed, and previous one is disabled.
• 2, create a new link every time the button is pushed, and previous one is not disabled.
• 3, don't create a new link every time the button is pushed, and share the link within the group until expiry date comes.(expiry date can be seen differently by users in the same group)
• 4, don't create a new link every time the button is pushed, and share the link within the group forever

After I summarize, I thought No3 is ok.

[hitohata]

Thank you for summarizing! You are right, considering the user experience my opinion seems a bad idea.

The No3 sounds good to me too. Is it possible to implement the expiry date for the users about the expiry date when users push the button? It might help users' experience.
However, doesn't need the updating of the expiry date? For now, users cannot expand the expiry date until that time comes. (Maybe this feature is not mandatory for now)

[nick-y-ito]

After discussing verbally, we reached the following conclusions regarding the invitation links:

• Each link is identified by a unique hash value.
• The links expire 24 hours after they are generated.
• If a previous link is still valid, its expiry is overridden to 24 hours instead of generating a new link.
• If there is no previous valid link, a new link is generated.