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.

  • Pantherina@feddit.deOP
    link
    fedilink
    arrow-up
    3
    ·
    11 months ago

    Flatpaks are generally made way to loosely. Always “not breaking” > “being secure”.

    So this should not really be the case, drag&drop doesnt work yet, maybe copy-pasting files doesnt if the app cannot access that directory statically (you need to add an attachment from within the app, your file picker will open which is a “portal” which links that file into the apps container and thus allows the app to see it.)

    Everything else works normally, screensharing too

    • Daniel Quinn@lemmy.ca
      link
      fedilink
      English
      arrow-up
      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
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        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.ca
          link
          fedilink
          English
          arrow-up
          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.

    • where_am_i@sh.itjust.works
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      11 months ago

      Last time I installed slack through flatpack I couldn’t send any files. Not through drag-and-drop, neither through the filepicker. The latter was just empty.

      Downloading files from slack also had awfully weird side-effects.

      Slack doesn’t have an apt repo, so I download debs and updat manually. Maybe once half-a-year.

      If that’s the experience I’d get on my signal through flatpack, I’d also rather be downloading manually. And I’d even compile from source rather than deal with that flatpack stuff.