Signal on Desktop survey?
community.signalusers.org
On this forum there is open discussion about Taking ownership of Signal Flatpak, but in my humble opinion, we need to have some measurements, before we can be taken more seriously by Signal desktop team. Can you please answer to bellow questions. Thank you. Which Signal on phone are you using: poll Which Signal on desktop are you using: poll Which method of installation are you using on Signal on desktop? poll If you are using Singal on Linux, on which Linux distribution you are using S...

There are big wishes for Signal to adopt the perfectly working Flatpak.

This will make Signal show up in the verified subsection of Flathub, it will improve trust, allow a central place for bug reports and support and ease maintenance.

Flatpak works on pretty much all Distros, including the ones covered by their current “Linux = Ubuntu” .deb repo.

To make a good decision, we need to have some statistics about who uses which package.

  • Daniel Quinn@lemmy.caEnglish
    3·
    11 months ago

    That’s an understandable goal, but as a user, breaking the user experience when I go to send a file to someone only to find that I can’t even see it in some apps is a deal breaker. If the app can’t be trusted to do that, I won’t use it.

    • Pantherina@feddit.deOP
      11·
      11 months ago

      What do you mran by this?

      This makes no sense.

      You cannot trust any app to do anything. Look at their code, or ask people that know people that heard of people that looked at their code (how it is currently done in FOSS, lol).

      Modern apps integrate portals & pipewire permissions. Bad apps dont, and they suck. Please annoy Slack with that, they have to adopt the Flatpak and modernize the code. Its like a few dozen lines to replace a custom own filepicker with the xdg-desktop-portal file picker of the OS.

      • Daniel Quinn@lemmy.caEnglish
        1·
        11 months ago

        I wasn’t talking about Slack. Actually, my worst Flatpak experience was with PyCharm. The fs limitations mean it couldn’t see files like ${HOME}/.config/git/ignore or load up my shell environment inside the IDE. It’s basically a neutered version of the app because someone decided to draw the security/usability line too far in the one direction.

        It’s fine if you think that’s a good idea, but as a user, the choice of packaging means it’s not useful to me, so I won’t use it.