Tiddlers with long names have their filenames truncated when backing up resulting in lost/missing data

[mdeabreu]

Describe the bug

File names are truncated when using the YunoHost backup which can result in hard to find or lost data. When restoring from a back up since the file names are truncated they may not have the .tid extension and so TiddlyWiki will not pick up and display the files. It's possible to go back and change the file names to include the extension however that can be tedious and error prone. Additionally it might be possible to have two tiddlers with long names that only differ near the end (ie ThisIsAReallyLongFileNameThatWouldBeTruncated.tid and ThisIsAReallyLongFileNameThatWouldAlsoBeTruncated.tid) that once truncated will become the same file name and might be overwritten (note I haven't actually seen this, but it seems like it might be possible).

Context

• Hardware: VPS bought online
• YunoHost version: 11.1.6.2
• I have access to my server: Through SSH | through the webadmin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using package version/branch: 5.2.3~ynh1

Steps to reproduce

• Install and open TiddlyWiki, nothing interesting here.
• Create and save a new tiddler with a very long name (~64 characters? Haven't counted)
• Create and save a new tiddler with a short name (ie test)
• Using the YunoHost backup system, create a backup. Can be done through the webadmin
• Download the backup and navigate to the folder containing your tiddlers (apps/tiddlywiki/backup/home/yunohost.app/tiddlywiki/tiddlers)
• Notice that the short name tiddler has a filename with extension .tid, notice that your long name tiddler has been truncated and is missing the extension.

Expected behavior

Backup system should back up the files exactly as they are named and should restore them exactly as they are named, this will ensure that no data is lost/missing

Logs

No logs seem relevant, the backup occurs without any indication that something has gone wrong

[mdeabreu]

Dug into this a bit more and I believe it to be an issue on my side and not applicable to many others. While attempting to use the backups I had, I had been opening the archives created by YunoHost using 7-zip 19.00, upgrading to 7-zip 22.01 everything appears to be correct.