1076413 - Usage should extends a links lifespan (call urls, not rooms)

Status: VERIFIED WONTFIX

(Hello (Loop) :: Server, defect)

Description

[:Harald Kirschner :digitarald]

To make Hello links useful for re-occurring meetings share links need should be available as long as they are used.

Having a 30 day expiration like it is now makes sense, but not that its post creation. The timer should be reset after each use to extends the links lifespan.

Comment 1

[Matthew N. [:MattN]]

I think I saw something about Rooms working like this but I can't find it now. Is that correct?

Comment 2

[Mark Banner (:standard8)]

The rooms part is bug 1074700, which is going to replace links.

I don't think we're planning on fixing this for links, which should come in 35. However, I'll let product make the decision there.

Comment 3

[Alexis Metaireau (:alexis)]

The wiki page about the rooms feature [0] says the rooms should expire after a certain amount of time that's defined by the room creator.

The server implementation we have is currently expiring them, as defined in the document. We need product to make a decision here about this, and can update the code accordingly then.

[0] https://wiki.mozilla.org/Loop/Architecture/Rooms#POST_.2Frooms

Comment 4

[Mark Banner (:standard8)]

(In reply to Alexis Metaireau (:alexis) from comment #3)
> The wiki page about the rooms feature [0] says the rooms should expire after
> a certain amount of time that's defined by the room creator.

Lets move this discussion to bug 1074700 as that is specifically about rooms. This bug can then be specific to the existing call urls.

Comment 5

[Alexis Metaireau (:alexis)]

What we can do, on the server side, is that all the call urls which are sent to us will have the action of making them valid for the expiration that was set at the beginning.

Would that work okay for you?

Comment 6

[:Harald Kirschner :digitarald]

For my use case that sounds great and from a user perspective this sounds also expected; having a valid link as long as its being used.

I don't know if rooms and links would need to work differently as I only see links in my Nightly.

Comment 7

[Romain Testard [:RT]]

After discussion with Mark:
* Call URLs are used in Fx34 and FxOS
* In Fx35 only room URLs will be used although we need to carry on supporting call URLs on the server as they get generated on the server side and FxOS will keep using them as we get to Fx35+

The room URL is as described in https://bugzilla.mozilla.org/show_bug.cgi?id=1074700
The call URL expires after 30 days - this is valid for FxOS and Fx34 behaviors

Changing the call URL behavior to "reset to 30 days" each time the call URL gets used seems interesting and will probably be mostly valuable for FxOS given that Fx34 will move to Fx35 after 45 days. Would this require client change or is it only server change?

I hope this clarifies things.

Comment 8

[Alexis Metaireau (:alexis)]

On the server side, we can only take action once the call-url is refreshed or accessed.
This means that we will not be able to do anything if the link is passed by email without being clicked, for instance.

Comment 9

[Romain Testard [:RT]]

Thanks.

The FxOS application lists the active call URLs under the assumption that generated URLs expire after 30 days. Implementing what is suggested here would break this FxOS application feature.

So let's not implement the call URL expiry date extension for now given that it would break a feature of the FxOS mobile app.
This is although added to the backlog for the mobile client app for its next release.

Comment 10

[Rémy Hubscher (:natim)]

This means we should probably add an endpoint to list the user call-urls.

Comment 11

[Alexis Metaireau (:alexis)]

Okay, closing this bug for now, please reopen when needed.

Comment 12

[James Bonacci [:jbonacci]]

OK.