In my opinion, it's a bit confusing for the user to save a file and to not be able to load it.
Couldn't it be better to force the extension. .jami for example ?
Even if it's a gz archive, why not to use our own extension (like .jami), making it easier for user to understand it is relative to Jami application and make it easier to filter when displaying the files available to load ?
enable all Jami account and extension files to be saved in one directory/folder should the user wish so.
have unique Jami file extensions.
be scalable and have distinct file extensions from those currently in use with other programs.
Having the file extension differ for the Desktop (*.jxd) and Android (*.jxa) versions would enable saving the extensions in one location on a user's computer. Additionally the files could be saved in the same directory/folder as Jami accounts (*.jac).
Unique file extensions for the same extension (eg. GreenScreen) for different platforms (eg. Desktop, Android, iOS)
If extensions are extended to iOS (which at the time of writing seems very unlikely due to Apple's restriction), the file extension could be *.jxi (Jami eXtension for iOS).
File extension summaries for *.jac, *.jxd, *.jxa and *.jxi indicate that these file extensions are categorized under zero distinct file types and/or mainly identified as a Binary Data format.
Android and Desktop extensions for Jami could be in one file; however, it is often chosen to distribute the plugins separately for Desktop and Android clients to have smaller file sizes.
Desktop extensions include multiple architectures (Linux/Windows/macOS) and the extension preferences system is designed around a declarative mechanism to allow a native presentation of extension preferences across various Jami clients/user interfaces.
So *.jxd and *.jxa could be one file *.jxu (Jami eXtension Unified).
The extension system is a unified format.
Unfortunately the "marketing" name for plugins was changed to extensions after years of developing them, and it would be too much work to change everything to extensions.
The consensus at the moment is to keep the jpl file extension for now, even if it's not consistent with the UI, most users would manage extensions through the Jami UI.
For now, the extension should be *.jpl and the description should be Jami extension as shown below: