About non-official apps.

[Samueru-sama]

Following @probonopd comments we have to add a way for "mere mortals" to be able to know which third-party provided AppImages are high-quality and trustworthy.

Thankfully, I think over 90% of the appimages in AM are all hosted on github and have a transparent build process behind them.

So I think what needs to be done is:

• We the appimage is not official but has a transparent build process behind, like this example we don't need to issue any warning, just point out that it is not official in the description.
• If the appimage is just a random uploaded binary, like in this example, we need to add a warning before installation.

I think the simple solution is adding a comment like # spooky to the installation script, and AM should check for that word before giving the warning.

[ivan-hc]

I agree.

The first step will be to allow listing AppImages into a separated list using a suboption --appimages in -l/list and -q/query

This is a preview on how AM 7.5 will look alike:

simplescreenrecorder-2024-08-08_22.55.41.mkv.mp4

---

I think that the focus on "spooky" AppImages can be planned for "AM" 7.6, so now we have a roadmap.

[Samueru-sama]

We can also add an option to filter out unofficial appimages from the list by simply doing a grep -vi unofficial in am -l, maybe I don't know if it is worth it lol.

[ivan-hc]

We can also add an option to filter out unofficial appimages from the list by simply doing a grep -vi unofficial in am -l, maybe I don't know if it is worth it lol.

I've another idea instead: to add an option "--safe-install" to ignore all scripts marked as "spooky", if marking the installation scripts was what you are looking for.

[ivan-hc]

or maybe to add "--safe" as a suboption of "-i"

[Samueru-sama]

https://github.com/ecmu/geany.AppImage (official "refurbised" in appimage)

What do you mean by "refurbised"?

Edit: If you meant a portable build wrapped into an appimage, that is still not official. I actually do this with DeaDBeeF and I clearly mark it as non-official.

edit: Also geany isn't in the database, I will add it later.

https://github.com/ValdikSS/windows2usb (spooky)

This one will have the warning.

[Samueru-sama]

In this case, Geany is a super-traditional app (official) in which people might think that there really is an AppImage for it, so in that sense it is "reformed/rehabilitated/refurbished". I dont know, but people can install it unconsciously thinking it is official.

In that case it will be marked as unofficial.

Basically for the app to be official it has to come from the creators of the application (geany) that isn't the case with that appimage.

What I'm not sure is how we should handle clients for popular applications, like for example the discord appimage will be marked as unofficial, but what about 3rd-party clients that modify discord like Vesktop which the appimage is made by the creators of the app, should that one be marked as unofficial as well?

[Samueru-sama]

What I'm not sure is how we should handle clients for popular applications, like for example the discord appimage will be marked as unofficial, but what about 3rd-party clients that modify discord like Vesktop which the appimage is made by the creators of the app, should that one be marked as unofficial as well?

I think we don't have to mark those as unofficial, because after all if you are installing vesktop you know that app isn't made by discord themselves I think.

However if the vesktop appimage wasn't made by themselves then the unofficial has to be added.

[ivan-hc]

Now that descriptions in the lists can be longer and more readable, to add info about official/unofficial and ever more details will be easier.

The "80 characters" rule is no more a rule.

Now to add Official/Unofficial can be done via pull request or bug report.

At this point, I think we have finished for the new release. This issue will be closed soon.

[ivan-hc]

The first part is complete.

Now its time to mark installation scripts. Right @Samueru-sama ?

[ivan-hc]

merged #850

now starts phase 3: the "AM" community