mdPlusPlus

@michaelkrieger I actually had to run the script multiple times for it to not show any missing files anymore.

You can achieve this with `firejail`. A simple firejail profile for Session derived from their Signal one (can certainly be improved): ``` $ cat ~/.config/firejail/session-desktop.profile # Firejail profile for session-desktop...

Just a little note that I personally really like the idea of recently closed #2519.

For the time being you can use the .AppImage and this[0] to run multiple different instances at once: [0] https://docs.appimage.org/user-guide/portable-mode.html It works a lot better than firejail isolation.

Just adding these here for completeness' sake. Some Session users mentioned (in addition to the AppImage portable mode and firejail) you can try to use `--profile=...` and `--user-data-dir=...` to separate...

This unfortunately doesn't work: ``` $ tree -L 2 . ├── GenericSessionNameWithVersionNumber.AppImage ├── profile1 │   ├── session1.AppImage -> ../GenericSessionNameWithVersionNumber.AppImage │   ├── session1.AppImage.config │   └── session1.AppImage.home └── profile2 ├── session2.AppImage ->...

If anyone is interested in implementing this, I think it would be beneficial if we had the option to have Session (especially the AppImage in my case) to start minimized...

Yes, like all other information available via the API, I imagine this information to be added using the `sogs` command at creation and being able to be modified later if...

This is somewhat related to #185.

My understanding is that there is "deep linking" feature planned, which is supposed to automatically open the client and ask whether to join. Judging from my observations of the development...