This probably is the issue, when you download a script or binary from the internet it doesn’t have execution permission, you would have to right click on folder to open in terminal (that way don’t have to cd to it), and check permissions with ls -la if it doesn’t have permission, change it with chmod

and then donate to the instance’s admins because there are no VC’s here … yet.

The point of lemmy (as far as I understand) is that there will not be a central corpo entity controlling and enshittifiying it as a whole, if that does happen to the particular instance your account or community is, you have the freedom to jump to another one, and continue your life.

On the other hand if you enjoy lemmy you could show support/donate, either to the devs, a particular instance admins, or even a particular community moderators

In my mind it would be super useful, I could sync my photos when my PC is on and when is off rely on my local photos only since my main goal is having a backup of them.

You could do this perfectly with the docker version, so just curiosity here, why not user docker?

Is it because you don’t want to install docker for only Immich? (you could also install other selfhosted server/apps as bonus),

would you be against snap? As someone already mentioned, there is a snap version.

If the important thing is having backups of your photos, there are alternative apps with different packaging formats.

You could make a request for flatpak, and see if other users also would like it, but you would have to wait for feedback from devs and understand if they don’t have the resources or willingness to maintain it.

Am I crazy or it makes sense?

If I’m interested in a specific app, I see what packaging formats it has and see how to install it and try it out. Only if I’m having issues with it (that can’t be solved), or can’t run it on my specific distro with the available packaging formats, I try to suggest/request a different format.

As far as I know, the options are:

• Use a QR reader app that doesn’t auto open links (or lets you configure it like that), so you see the URL and inspect it before opening the URL in the browser.
• In case of a short URL, use a short URL resolver so you can see what is the real destination without actually opening the URL yourself.
• Using a DNS with block lists (that are updated often) of known phishing sites.

If these 3 checks fail, there is not much more you can do.