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.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    Personally I install it with pacman and generally avoid Flatpaks due to annoying problems I’ve had with it limiting filesystem access in the past. My biggest problem is that it seems to “forget” that I’m logged in if I don’t use it regularly, meaning I have to regularly re-auth it on my desktop since I use it infrequently there.

    • Pantherina@feddit.deOP
      link
      fedilink
      arrow-up
      0
      ·
      5 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

      • where_am_i@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        5 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.

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

      This is just so bad. I can’t use anything snap/flatpack cuz it simply won’t let me send a file. As it runs on it’s on file subsystem and doesn’t have access to anything else.

      On the other hand, an app that has access to my entire hard-drive is awfully insecure, right? So, what’s the solution?

      in the meantime they could include an option “I allow this app to acess my whole $HOME, thanks, I need it cuz I am a user not a security researcher”. Until then I’m not touching flatpack

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

    Luckily for me, I’m on an Ubuntu derivative. So apt upgrade just does it. Sorry, OP, works for me in my preferred way, I don’t need any flatpacks. Let’s hope once they do one they keep building .debs nonetheless.

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

    The heck are you all talking about? The post says Linux and Flatpack, while everyone somehow is discussing why signal is not on f-driod.

    How the heck is this related?