Preserve Thread History when Chat Profile no longer available or is renamed

[DmitriyAlergant]

trafficstars

Is your feature request related to a problem? Please describe.

Current behavior: If a Chat Profile was used to create a thread (with persistence). But later is no longer advertised by the App, or its name has changed (which is basically same thing, since Chat Profiles only have names not IDs), the thread is broken in the history and cannot be shown to the user - blank screen

Describe the solution you'd like

1. Some kind of persistence of previously used chat profiles metadata (at a thread level) that would allow a user to recall and review the thread history, and see what profile it used - with its last known name, icon and description. Perhaps the thread should then become immutable and do not allow further messages submissions or edits, until or unless the chat profile is advertised again by the app.

2. Introduce chat_profile."display name" attribute (optional) in addition to the name. If "display name" is provided, then use Display Name when showing the profile in UI for end-users, and it can be different from the technical "name" (which currently acts as a code/id of a chat profile), and can freely change without breaking the data model. This will make it easier for developers to keep the actual "names" immutable and less changing. If it was a redesign from scratch perhaps it would be better to have a "chat profile id" as a key, but that would be a breaking change so better not to.

3. AT THE VERY LEAST if point 1 is not done, just show a clear and concise error "chat profile (name) is no longer available, the thread cannot be shown" rather then blank screen.