TheAssassin

> If we are to "reverse" the action/checkbox, I'd need to find a good label text for the checkbox ("Also make available to the system"? "Also install into the system"?)....

> the user may copy the application if they so desire Well, we just provide that option in a dialog, since there is no "Applications dir" that would pop up...

> How come that on the Mac there is /Applications (let's call this the "integration directory") but there is absolutely no way nor need to change that directory? I think...

> in which situation can a user end up with an AppImage that is integrated into the system but resides in a different location? If the integration directory is changed?...

... will be looked into if I find 5 minutes. The issue is still open, but you might have noticed there's tons of older issues that I want to look...

The "do not ask again" part is planned for the new UI. We have not thought of a usable mechanism so far, but I guess that'll be another nice use...

Filenames that depend on the content. `kdenlive-18.04.1-x86_64_db228740f982bb2cace6b70a4dd494ca.AppImage` would be such a name. The idea is that even if two AppImages had the same filename, but differed content-wise, adding such a...

That's automatically performed by AppImageLauncher on integration.

Why should that be a joke? What the heck? This is actually an important _feature_. The files can still be recognized by their original filename in `~/Applications`.

That sentence doesn't make _any_ sense. This is the only way to allow multiple apps which don't put a version in their AppImage filename in parallel. Users don't have _any_...