Delay before client obsolescence

When a new Discord client update is published, the client forbid access to the app while the update is not applied, and ask the user to install it manually.

On Linux, the standard way is to install application through packet manager. And it may takes some time that the Discord update comes to the distribution repositories.

And it makes sense, since there is an integration test before the update is published to those repositories. Even in rolling release based distribution, it may takes several weeks. And meanwhile, Discord is not anymore accessible. Quite annoying.

It would be nice if there is some tolerance before a client become obsolete.

Comments