Changing group chat title causes orphan logs

[PabloCastellano]

While individual chat logs are written to:
~/.purple/logs/telegram/"MY_CELL_NUMBER"/"ID"/.txt,
group chat logs are written:
~/.purple/logs/telegram/"MY_CELL_NUMBER"/"GROUP_TITLE"/.txt

Changing the group chat title doesn't rename the folder, so the old title logs remain unlinked to any chat.
The solution is not as easy as renaming the folder when the title changes as two group chats with the same title share the same folder and it would mess it up even more. Maybe using an uuid or using group title + uuid as folder?

[franciscod]

I think the directory name being an UUID makes sense.

Because this name isn't really meaningful to a human looking for its chats, there should be a way for mapping names to UUIDS. Maybe a text file containing current and old names is useful, something along these lines:

### Current group UUIDs
uuid                | current name
------------------- | ------------
ADJIOIJWQEASKD-1231 | School Buddies
IQWOPEIEWQOPDA-6666 | Next meetup: 04-04!

### Old names
uuid                | old name
------------------- | --------
IQWOPEIEWQOPDA-6666 | Next meetup: 03-03, woohoo!

bonus: the same text file rendered as github's markdown:

Current group UUIDs

uuid	current name
ADJIOIJWQEASKD-1231	School Buddies
IQWOPEIEWQOPDA-6666	Next meetup: 04-04!

Old names

uuid	old name
IQWOPEIEWQOPDA-6666	Next meetup: 03-03, woohoo!

[majn]

@franciscod Telegram already assigns unique IDs to all chats, and I use those as a chat id in libpurple and the chat name as subject.

I think its because Libpurple will always use the displayed conversation name to store chat logs. The only fix I can think of at the moment would be to just not update the chat names after adding them for the first time.

[majn]

The only fix I can think of at the moment would be to just not update the chat names after adding them for the first time.

This is how I do it now, btw.