Feature Request: Little Explanations

[OssNass]

Is it possible to add a little explanations below permissions so the user can understand what are the permissions they are granting or revoking of an application

[rusty-snake]

There's a quite comprehend documentation.

[OssNass]

It is still better to show it under the options.

[tchx84]

hey @OssNass , this is a tricky one... e.g, I need to avoid overwhelming people with too much information, because there're so many options (and these will only increase with time).

Could there be other ways? Maybe... e.g. tool tips on each permission (but, would not help much on mobile devices). e.g. re-working the current titles (I tried, but not every permission can be fully explained in a one-liner).

So, the current compromise is to include that offline documentation where I can describe as many details I want, plus examples, etc.

[Doomsdayrs]

I was writing down issues my neurodivergent girlfriend had when using Linux, and thankfully someone already reported this.

Take for example, this below

What does allow=per-app-dev-shm mean to someone who doesn't work with computers, Linux, and/or FLATHUB? These are developer flags, useless for the average user.

To further investigate let us look at FLATHUB documentation for what per-app-dev-shm means:

The per-app-dev-shm feature shares a single instance of /dev/shm between the application, any unrestricted subsandboxes that it creates, and any other instances of the application that are launched while it is running.

To simplify this beefy documentation for an average user

Allows applications to access a shared pool of memory. (More Info)[open up documentation]

This is an explanation, it is not beefy, it is not overwhelming. It is the bare minimum to inform someone what something is. The more info link is because not everything can be explained in one line, but that is okay, you already have offline documentation, more info can just open it up to the specific page.

Further more if you want to have allow=per-app-dev-shm displayed for some reason, it should be a toggle in settings for developers. Users will get overwhelmed by weird looking things that don't make sense to them.

As quoted by my girlfriend "A Wikipedia article is better at explaining things"

There's a quite comprehend documentation.

Further more, I did not even know about this, why would an average user know about it either? There is no indication that such exists.

[trymeouteh]

The documentation is also hidden away a bit and I think having a short description on every setting with a link to the full details to the documentation would be best.

[Danik1601]

I need to avoid overwhelming people with too much information, because there're so many options (and these will only increase with time)

I think I have a solution for that. In Russia we have the company named Keenetic. It is a former subsidiary of Chinese TP-Link. They produce Wi-Fi routers. Their hardware are mostly crappy MIPS processors, but software is pure brilliance. By the way it is based on Linux and OpenWRT and partially open source.

Well, I get back to topic. Their software is deeply integrated with their help center and online documentation (also brilliant, by the way). You can see the example below. I suggest you to implement similar thing (little question marks that lead to the corresponding documentation section).

P.S. please make offline documentation open in a separate window, this would be very handy.

https://user-images.githubusercontent.com/17238959/171259306-9a846c56-f452-42ca-aa15-f67fc6daff6a.mp4